Creating a full-recovery baseline
Use the following procedure to create a full-recovery baseline, which establishes a point-in-time snapshot of an application’s data structure and data.
This type of baseline can be used as a recover point in cases in which structure changes are implemented or data is lost. Baselines that are taken at two different points in time can be compared to determine what changes have been applied to the data structure definitions for that specific time frame.
Before you begin
To exclude XML or LOB data from the full-recovery baseline, modify one of the following profiles and create scope rules to exclude the tables that contain the XML or LOB columns:
- Baseline profile that you used to build the full-recovery baseline
- Outbound migrate profile that the baseline profile references
To create a full-recovery baseline
- On the BMC AMI Change Manager for Db2 Main Menu, select WORKID, and press Enter.
On the WORKID Action Menu, specify an existing alter-type WORKID and select Analyze WORKID and create a worklist. Then, press Enter.
- On the Analysis Alter Worklist Interface panel, select Generate a worklist which will convert and reload current data and establish a full recovery baseline. Then, select the Run Type and press Enter.
- On the Analysis Baseline Interface panel, provide the information that is needed to build the full-recovery baseline.
- Specify the name of the Baseline Profile.
- Specify the Baseline Name, or leave the field blank and use the profile’s baseline name template to name the baseline automatically.
- To protect the baseline, type Y for Protect.
- Press Enter.
- On the Analysis JCL Processing Interface panel, specify the data set names to be used in the baseline.
- (Batch run type) Type the data set name for the JCL that is generated by this process.
- Type the data set name for the Worklist that is generated by this process.
- Type one of the following options for Diagnostics:
- (Foreground run type) To display the diagnostics on the terminal, type TERM.
- To write the diagnostics to a sequential file, type the name of the data set.
- To write the diagnostics to a print data set, type SYSOUT.
- (Foreground run type) If you specified SYSOUT in step Step 5.c, specify the SysoutClass.
- Select your processing options.
- To override the options for analyzing the work ID, type S to select Override. The Analysis Options panels are displayed. For more information about overriding options for analysis, see Overrides-of-default-processing-options.
- To create the input for Analysis, select one of the following options:
- (Foreground run type) Type S to select Create analysis input.
- (Batch run type) Type S to select Create JCL.
- To review or modify the input to the process, select one of the following options:
- (Foreground run type) Type S to select Edit analysis input.
- (Batch run type) Type S to select Edit JCL.
- To create a worklist, select one of the following options:
- (Foreground run type) Type S to select Run analysis.
- (Batch run type) Type S to select Submit JCL.
- To modify the worklist, type S to select Edit Worklist.
- Press Enter.Analysis generates the steps in a worklist for creating a full-recovery baseline.
- Press END.
- On the WORKID Action Menu, select Execute WORKID worklist created by Analysis.The Execution JCL Build Interface panel is displayed.
- Specify the information to build and run the JCL.
- Select Build Initial JCL.
- Specify a Run Type.
Press Enter.The Execution Pre- and Post-Processing Interface panel is displayed.
ACMFEXC1 ---------- Execution Pre- and Post-Processing Interface --------------
Command ===>
WORKID . . . . . : RDACRJ.ALT03
Specify additional steps to be included in this job. Then press Enter.
Pre-Execution Compare
1 1. Do not do a compare before execution
2. Compare two previous baselines
3. Compare a previous baseline to the current catalog
Full Recovery Baseline has been specified.
Post-Execution Compare
1 1. Do not do a compare after execution
2. Compare a previous baseline to the new catalog structures
3. Compare the baseline built during a previous job step to the new
catalog structures
4. Create CDL to fall back to a previous baseline
Post-Execution Baseline
1 1. Do not build a baseline after execution
2. Build a baseline after execution
Commands: HELP PREVIOUS END
- Press Enter.
- On the Execution JCL Processing Interface panel, specify the data set names to be used by Execution.
- Type the data set name for the Execution JCL that is generated by this process.
- Type the data set name for the Worklist that is used by this process.
- Type one of the following options for Diagnostics:
- To write the diagnostics to a sequential file, type the name of the data set.
- To write the diagnostics to a print data set, type SYSOUT.
- (Batch run type) Type the name of the data set to contain the Batch JCL Job. The batch job is used to generate the Execution JCL.
- Select the processing options. When Execution processes the worklist, the full-recovery baseline is established.
- To override the options for executing the worklist, type S to select Override Defaults. The Execution Options panels are displayed. For more information about overriding options for execution, see Overrides-of-default-processing-options.
- To edit the worklist that was generated by Analysis, type S to select Edit Worklist.
- To create the input to Execution, select one of the following options:
- (Foreground run type) Type S to select Build Execution JCL.
- (Batch run type) Type S to select Build Batch JCL.
- To review or modify the input to the process, select one of the following options:
- (Foreground run type) Type S to select Edit Execution JCL.
- (Batch run type) Type S to select Edit Batch JCL.
- Select one of the following options:
- (Foreground run type) To execute the worklist, type S to select Submit Execution JCL.
- (Batch run type) To submit the batch JCL, type S to select Submit Batch JCL.
- Press Enter.