Filter
Top Products
Recover to prior point in time
- A recovery of all tablespaces, indexspaces, DB2 catalog, and DB2 Directory to a
previous log RBA (three ways to acomplish this)
- Conditional Restart to recover to any previous point in time using DB2 Image Copies
- Identify LOG RBA of prior point in time time: With DB2 V7 and the CHKFREQ
parameter for controlling DB2 checkpoint time the recommendation is to set CHKFREQ
at 15 minutes. That will ensure a days worth of checkpoints on the checkpoint queue in
the BSDS, and will provide four RBAs / LRSNs every hour that can be used in the
conditional restart.
- Identify Tablespaces modified after the RBA to reduce the number of recovery jobs.
Perform an analysis of the DB2 logs from the recovery RBA to the
current end of the log in order to minimize the number of objects to
be recovered. In this case recover the DB2 Catalog/Directory and
only those objects that are identified as a result of the analysis. Use REPORT
RECOVERY utility against all tablespaces or run DSN1LOGP SUMMARY
The best approach to identifying only the objects that need recovering is to analyze the
archive logs that have been created between the two points-in-time. The
recommendation is to put an automated process in place to analyze the archive logs as
they are created, rather than waiting until a recovery situation arises.
The archive logs should be analyzed for all objects that have at least one of the
following four message numbers, indicating a change to the object.
--DSN1151I,
--DSN1152I,
--DSN1160I,
--DSN1162I.
- STOP DB2
- Save the BSDS and log datasets after the target RBA
- Build DB2 Conditional Restart Rceord using DSNJU003 with ENDRBA=target RBA
- Update ZPARMS to set DEFER=ALL, Restart DB2
- Recover DB2 Catalog and Directory to current point in time. Refer to the Utility
Guide, Chapter on RECOVER; Instructions for Specific Tasks; Recovering catalog
and directory objects.
- all user indexes on the catalog and directory
- Recover R/3 Tablespaces and Indexspaces identified above to current point in time
- Stop DB2
- Update ZPARMS to reset DEFER parameter
- Perform Full Offline Backup
- Restart DB2
- Use transaction SM13 to resolve R/3 units of work (business transactions)
Copyright 2006
IBM Solutions Technical Sales (STS) 12/18/2007Page 44 of 51
12/18/2007
Planning and Preparation Guide for SAP NetWeaver Version 6.40: z/OS Implementation