You Are With Mahesh Blog: Migrate_V7(32)_to

Migrate DB2 UDB from V7 to V8 64 bits

INDEX

Purpose
Scope
Process

DB2 V8 32 bit instance creation
Offline back of V7 and use of DB2CKBKP utility
Preparation of ‘set tablespace container’ script
Re-direct restore of V7 database backup into DB2 V8 32 bit instance
Verification of restore re-direct
Migrate instance from V8 32 bits to V8 64 bits (db2iupdb)
Post migration activities

Rebinding DB2 Packages
Verify packages are migrated into V8 sqllib directory
Updating your System Catalog Statistics
Converting all Indexes from TYPE-1 to TYPE-2

Perform offline backup of database (V8 64 bit)

Purpose: This document provides standard way of migrating database DB2 UDB from V7 to V8 64 bits.

Scope: DBA and System admin

It is not possible to restore database backup image from V7 32 bit to V8 64 Bit directly, but it is possible to migrate by restoring a V7 32-bit backup, restore it to v8 32-bit before updating the instance to 64-bit.

Process:

DB2 V8 32 bit instance creation:

Create db2 32 bits instance sandbox (test server).

Below document describe brief way to create V8 32 bit instance.

Offline back of V7 and use of DB2CKBKP utility:

Take full offline back up of DB2 V7

Check whether backup is restorable or not and also extract tablespace information and other object information from backup image.

FTP backup image to the sandbox (test server where you have created 32 bit instance)

Below document provides way to perform the same task.

Preparation of ‘set tablespace container’ script:

Base on tablespace information extracted from db2ckbkp command; prepare script to set tablespace containers which will be use in redirect restore process.

Below document has ‘set tablespace container’ script

Don’t execute the script

Re-direct restore of V7 database backup into DB2 V8 32 bit instance:

Now be ready for redirect restore.

Find out the file system where you can have space double or more then size of the backup image as restore command will dump data there in that file system.

db2inst2@mcdb-ha17:~> db2 RESTORE DATABASE AC202 FROM /home/db2inst1/nfsbackup/db200/ac202/db2backupfiles TAKEN AT 20070510091206 NEWLOGPATH /db2data1/db2inst2/data/ac202/logs REDIRECT

SQL1032N No start database manager command was issued.

Make sure instance is up and running. If not start db2 instance.

db2inst2@mcdb-ha17:~> db2start

SQL1063N DB2START processing was successful.

db2inst2@mcdb-ha17:~> db2 RESTORE DATABASE AC202 FROM /home/db2inst1/nfsbackup/db200/ac202/db2backupfiles TAKEN AT 20070510091206 NEWLOGPATH /db2data1/db2inst2/data/ac202/logs REDIRECT

SQL1277N Restore has detected that one or more table space containers are

inaccessible, or has set their state to 'storage must be defined'.

DB20000I The RESTORE DATABASE command completed successfully.

As shown in “SQL1277N” you need to set tablespace container for each tablespace as restore is not able to identify path for the tablespace containers in new server (test server).

So need to define storage path of each tablespace container.

Now run script for set tablespace container.

db2inst2@mcdb-ha17:~> db2 -td~ -vf set_tab_cont.sh

set tablespace containers for 0 using (path '/db2data1/db2inst2/data/ac202/SYSCATSPACE')