Task 1: Initializing Db2 resources for recovery (Phase 1)
Before you begin
Before you initialize the Db2 resources, perform the following tasks:
- Restore operating system catalogs and aliases and the tape management catalog. (This responsibility usually belongs to the operating system programmers.)
- Restore Db2, BMC, and other application load libraries and data sets.
- Unload the system resource recovery jobs that were created by ARMBSRR.
- If you are recovering a data-sharing object set, clean out old information from the coupling facility structures. See the IBM DB2 Administration documentation for additional information on this procedure.
- Bring up BMC Db2 Component Services (DBC).
To initialize Db2 resources
- Verify and, if necessary, edit the JCL that was created by ARMBSRR. For each Db2 subsystem, you may need to perform the following tasks:
- Edit the JCL and search for ACTION(ABORT) to locate any INDOUBT transactions. Determine whether to modify the JCL from ACTION(ABORT) to ACTION(COMMIT) in order to allow those transactions to be committed. Otherwise INDOUBT transactions are aborted.
- If you do not use the same volume names at the recovery site as you do at the local site, you must modify the JCL to reflect the recovery site volume names.
- If your data sharing members are not on the same operating systems as the local site, you must change the ROUTE cards.
Submit the JCL that was created by ARMBSRR. Db2 must not be started at this time.The Phase 1 job or jobs begin executing immediately, whereas the Phase 2 job or jobs are held for execution. If you used MAXLOGJOBS > 1, the Phase 1 jobs will submit additional log copy jobs. For more information about ARMBSRR and the number of jobs in each phase, see ARMBSRR—System resource recovery.
If multiple jobs were created for Phase 1, they will be submitted by this JCL when it executes. See About Phase 2 for a diagram illustrating Phase 1 multiple jobs.
Upon completion of the Phase 1 job or jobs, check the job output for warning or error messages. Correct any error situations to complete Phase 1 successfully.If you are using the Recovery Management for Db2 solution, check the job output from the ARMD* jobs to verify that data collection from the recovery processed correctly. For actual recoveries, data collection errors do not affect the job return code. This feature ensures that problems with data collection do not impact the disaster recovery.