Under certain circumstances, you might want to reset the
entire Db2 subsystem
to a point of consistency.
Procedure
To prepare a point of consistency:
- Display and resolve any indoubt units of recovery.
- Use the COPY utility to make image copies of all the following types of
data:
- User data
- Db2 catalog and directory table spaces,
and optionally indexes
- If you are using Db2 query acceleration with IBM Db2 Analytics Accelerator for z/OS, the table spaces and index spaces for the
Db2 SYSACCEL tables and indexes
Copy SYSLGRNX and SYSCOPY last. Installation job DSNTIJIC creates image copies of the Db2 catalog and directory table spaces. If you
decide to copy your directory and catalog indexes, modify job DSNTIJIC to include those indexes.
Alternate method: Alternatively, you can use an off-line method to
copy the data. In that case, stop Db2
first; that is, do the next step before doing this step. If you do not stop Db2 before copying, you might have trouble
restarting after restoring the system. If you do a volume restore, verify that the restored data is
cataloged in the integrated catalog facility catalog. Use the access method services LISTCAT command
to get a listing of the integrated catalog.
- Stop Db2 with
the command STOP DB2 MODE (QUIESCE).
Important: Be sure to use MODE (QUIESCE); otherwise,
I/O errors can occur when you fall back before a Db2 restart.
Db2 does
not actually stop until all currently executing programs have completed
processing.
- When Db2 has stopped,
use access method services EXPORT to copy all BSDS and active log
data sets. If you have dual BSDSs or dual active log data sets, export
both copies of the BSDS and the logs.
- Save all the data that has been copied or dumped, and protect
it and the archive log data sets from damage.