SHRLEVEL CHANGE method
In this method, you define an ongoing log scan to collect the log generated by the source table space and apply it to the target table once it has been transformed.
An ongoing log scan can run repeatedly, with each start point dependent on the end of the previous log scan. You can scan the logs multiple times, changing the range of the log scan for each run, but not changing the SYSIN DD syntax of your job step. The product keeps track of any transactions (units of recovery) that start within the current log scan, but are still open at the end point. At the start of each run, the product automatically changes the start point so that it begins at the lowest RBA/LRSN address in the set of recorded open transactions from the previous run of the log scan.
(For more information, see Using-Online-Consistent-Copy-for-transforms-or-data-migration.)
The procedure for converting a table space with SHRLEVEL CHANGE method is similar to the procedure for using the SHRLEVEL REFERENCE method, with the following exceptions:
- You do not issue a Db2 command to start the database in read-only status before you create a consistent copy. Instead, you issue the command later in the process.
- You use logical log files to migrate data changes on an ongoing basis.
To convert objects by using the SHRLEVEL CHANGE method, follow the steps in the order shown in the following table:
To perform this step | Use this BMC solution component | Reference |
|---|---|---|
Create a target set of objects, using the source objects as a template. | BMC Database Administration for DB2 (BMC AMI Change Manager for Db2 component) | |
Create an Online Consistent Copy of the Db2 table spaces and indexes and specify a WORKID. | BMC Recovery Management for Db2 (Online Consistent Copy technology) | |
Create and run a job that converts the table spaces and indexes. | BMC Recovery Management for Db2 ( component) | |
Create the logical log files. | BMC Recovery Management for Db2 (BMC AMI Log Master for Db2 and High-speed Apply Engine components) | |
Apply the logical log files to the target table space and indexes. Create and apply the logical files as needed until the desired batch window is available to stop and rename the table. | BMC Recovery Management for Db2 (BMC AMI Log Master for Db2 and High-speed Apply Engine components) | |
Issue a Db2 command to start the source table space with read-only status. | None | |
Run RUNSTATS. | None | |
Create the final logical log file, and apply the file to the target objects. | BMC Recovery Management for Db2 (BMC AMI Log Master for Db2 and High-speed Apply Engine components) | |
Issue a Db2 command to stop the target table space. | None | |
Rename the source and target objects. Re-create alias and view triggers. | BMC Database Administration for DB2(BMC AMI Change Manager for Db2 component) | |
Start the database in read-write status. | None | |
Run binds. | None | |
Modify the batch jobs that reference the source table spaces. | None |
The following figure provides a hypothetical timeline that corresponds to the steps shown in above table for performing conversion using the SHRLEVEL CHANGE method.
This section contains the following topics: