SEO

Hi,

we have a little problem with the dependencies of an application (MKS)
that we want to upgrade to a new version.

The application now runs on a Suse Linux 7.3 system with 2.4 kernel and
DB2 7.2. We want to upgrade this application to the recent version and
move it to new host. This system will be RedHat EL 4 with kernel 2.6 and
DB2 8.2.

The problem is that the old version doesn't support DB2 8.x. I thought a
backup on the old host and a restore on the new host should be sufficient,
but the support people told us, that this is not possible. They recommend
us to first install 7.2 on the new system (RHEL 4, 2.6 kernel), import the
data from the old system and then update 7.2 to 8.2. I hate this solution.

I can't find any information which distribution/kernel DB2 7.2 supports,
because 7.2 is outdated and not listet on the DB2 validation page.

Any pitfalls with 7.2 on RHEL 4 and kernel 2.6? Any ideas how to avoid
this messy upgrade path?

Thanks, Ralf

Ralf Gross wrote:
> Hi,
>
> we have a little problem with the dependencies of an application (MKS)
> that we want to upgrade to a new version.
>
> The application now runs on a Suse Linux 7.3 system with 2.4 kernel and
> DB2 7.2. We want to upgrade this application to the recent version and
> move it to new host. This system will be RedHat EL 4 with kernel 2.6 and
> DB2 8.2.
>
> The problem is that the old version doesn't support DB2 8.x. I thought a
> backup on the old host and a restore on the new host should be sufficient,
> but the support people told us, that this is not possible. They recommend
> us to first install 7.2 on the new system (RHEL 4, 2.6 kernel), import the
> data from the old system and then update 7.2 to 8.2. I hate this solution.
>
> I can't find any information which distribution/kernel DB2 7.2 supports,
> because 7.2 is outdated and not listet on the DB2 validation page.
>
> Any pitfalls with 7.2 on RHEL 4 and kernel 2.6? Any ideas how to avoid
> this messy upgrade path?
>
> Thanks, Ralf

Place to start looking is:

http://www-306.ibm.com/software/data...inux/validate/


Unfortunately V7.1 was pulled out of service in Dec 2002 (3 years ago) and V7.2
was pulled out of service in Sep, 2004 (2 years ago) - so you will find
difficult to locate historical information.

I would not give up on backup/restore path - just take a backup on existing V7.2
system - ftp backup image to new system and try to restore.

It would help if containers were all SMS containers.


Hope it helps,

Jan M. Nelken

Jan M. Nelken wrote:
>>
>> we have a little problem with the dependencies of an application (MKS)
>> that we want to upgrade to a new version.
>>
>> The application now runs on a Suse Linux 7.3 system with 2.4 kernel and
>> DB2 7.2. We want to upgrade this application to the recent version and
>> move it to new host. This system will be RedHat EL 4 with kernel 2.6
>> and DB2 8.2.
>>
>> The problem is that the old version doesn't support DB2 8.x. I thought
>> a backup on the old host and a restore on the new host should be
>> sufficient, but the support people told us, that this is not possible.
>> They recommend us to first install 7.2 on the new system (RHEL 4, 2.6
>> kernel), import the data from the old system and then update 7.2 to
>> 8.2. I hate this solution.
>>
>> I can't find any information which distribution/kernel DB2 7.2
>> supports, because 7.2 is outdated and not listet on the DB2 validation
>> page.
>>
>> Any pitfalls with 7.2 on RHEL 4 and kernel 2.6? Any ideas how to avoid
>> this messy upgrade path?
>>
>> Thanks, Ralf
>
> Place to start looking is:
>
> http://www-306.ibm.com/software/data...inux/validate/

That was the first thing I checked

> Unfortunately V7.1 was pulled out of service in Dec 2002 (3 years ago)
> and V7.2 was pulled out of service in Sep, 2004 (2 years ago) - so you
> will find difficult to locate historical information.

That's one of my problems.

> I would not give up on backup/restore path - just take a backup on
> existing V7.2 system - ftp backup image to new system and try to
> restore.

I tried the backup/restore and it worked well. The problem is the
application that uses the DB2 database. To upgrade this application,we
have to install an old version of this app (which doesn't support DB2 8.x)
on the new host and then migrate to the recent release.

> It would help if containers were all SMS containers.

I have no idea about the database structure, how can I check this?

Ralf

Ralf Gross wrote:

> I have no idea about the database structure, how can I check this?
>
> Ralf

db2 connect to sample

Database Connection Information

Database server = DB2/NT 8.2.3
SQL authorization ID = DB2ADMIN
Local database alias = SAMPLE


db2 list tablespaces

Tablespaces for Current Database

Tablespace ID = 0
Name = SYSCATSPACE
Type = System managed space
Contents = Any data
State = 0x0000
Detailed explanation:
Normal

Tablespace ID = 1
Name = TEMPSPACE1
Type = System managed space
Contents = System Temporary data
State = 0x0000
Detailed explanation:
Normal

Tablespace ID = 2
Name = USERSPACE1
Type = System managed space
Contents = Any data
State = 0x0000
Detailed explanation:
Normal

Tablespace ID = 3
Name = SYSTOOLSPACE
Type = System managed space
Contents = Any data
State = 0x0000
Detailed explanation:
Normal


db2 list tablespace containers for 0

Tablespace Containers for Tablespace 0

Container ID = 0
Name = D:\DB2\NODE0000\SQL00002\SQLT0000.0
Type = Path



db2 list tablespace containers for 1

Tablespace Containers for Tablespace 1

Container ID = 0
Name = D:\DB2\NODE0000\SQL00002\SQLT0001.0
Type = Path



db2 list tablespace containers for 2

Tablespace Containers for Tablespace 2

Container ID = 0
Name = D:\DB2\NODE0000\SQL00002\SQLT0002.0
Type = Path



db2 list tablespace containers for 3

Tablespace Containers for Tablespace 3

Container ID = 0
Name = D:\DB2\NODE0000\SQL00002\SYSTOOLSPACE
Type = Path


Rest is documented in online documentation available at:

http://publib.boulder.ibm.com/infoce...help/index.jsp

Jan M. Nelken wrote:

> Ralf Gross wrote:
>
>> I have no idea about the database structure, how can I check this?
>
> db2 connect to sample
> [...]

This basically looks the same here.

Tablespace ID 0...3
Type = System managed space

> Rest is documented in online documentation available at:
>
> http://publib.boulder.ibm.com/infoce...help/index.jsp

I'm not quite sure how importent for the upgrade this will be.

| It would help if containers were all SMS containers.

Maybe I should contact the support of the application again. But they are
not very experienced with DB2 either...

Ralf

Ralf Gross wrote:

>
> Maybe I should contact the support of the application again. But they are
> not very experienced with DB2 either...
>
> Ralf

Another idea you may want to consider is to use VMWARE under RHEL 4. Just create
a VM running Suse 7.3 - install DB2 V7.2 in VM and DB2 V8.2 in RHEL 4....With a
private networking both DB2 can "see" each other ...

Jan M. Nelken