When you migrate a DB2® 10
production subsystem or data sharing group that has a tracker site to Db2 11 conversion mode or convert a Db2 11 production site to new-function mode, you
need to follow a special procedure to migrate or convert the tracker site.
Before you begin
You need to migrate or convert the tracker site after you perform any of the following operations
on the production site:
- Migrate from DB2 10 new-function mode
to Db2 11 conversion mode
- Convert from Db2 11 conversion mode to
Db2 11 enabling-new-function mode
- Convert from Db2 11
enabling-new-function mode to Db2 11
new-function mode
- Revert from Db2 11 new-function mode
to Db2 11 conversion mode*
You do not need to perform fallback of the tracker site after you perform fallback of a
production site from Db2 11 conversion
mode to DB2 10 new-function mode, unless
the fallback process restores the catalog and directory to a point in time prior to the migration to
Db2 11.
Procedure
To migrate or convert the tracker site to Db2 11, follow one of the following
procedures:
- If you use RESTORE SYSTEM for recovery cycles, follow the procedure in Establishing a recovery cycle by using RESTORE SYSTEM LOGONLY.
- If you use the RECOVER utility for recovery cycles, follow these steps.
- If the tracker site is a data sharing group, issue the z/OS SETXCF
FORCE command to delete the shared communications area (SCA) structure.
- Restore the BSDS and active logs using copies of the production site's BSDS and active logs.
- Create a conditional restart control record (CRCR) in the BSDS by
using the change log inventory utility.
- Start Db2 on the tracker
site. The subsystem parameter module for starting Db2 needs to include TRKRSITE=YES.
- Restore the DSNDB01.SYSUTILX table space, and recover the DSNDB01.DBD01, and DSNDB01.SYSDBDXA table spaces. Rebuild the associated indexes after recovering each table space.
For DSNDB01.DBD01 or DSNDB01.SYSDBDXA, if you took full image copies of the table spaces after you migrated or converted the production system to Db2 11, run RECOVER without the LOGONLY option. If you did not take full image copies, run RECOVER with the LOGONLY option.
- Stop Db2.
- Perform steps 1, 2, and 3 again.
- Start Db2 on the tracker site
with the TRKRSITE=YES option again, to cause Db2 to read the new database descriptor information
from the DSNDB01.DBD01 table space.
- Recover all remaining catalog and directory table spaces, and rebuild their
indexes.