Recovering catalog and directory objects
If you need to recover the catalog and directory, you must recover them before you recover user table spaces. Also, you must recover catalog and directory objects in a specific order.
Before you begin
- Ensure that you have applied APAR PI11316 and completed the ++HOLD actions.
- Recovering and rebuilding catalog and directory objects requires installation SYSADM or installation SYSOPR authority.
- If you are performing a recovery at a remote site, start the remote DB2® for z/OS® subsystem with ACCESS(MAINT) specified on the START DB2 command and with DEFER ALL specified in the DSNZPARM load module. (See installation panels DSNTIPS and DSNTIPO3.) If DB2 is not started with ACCESS(MAINT), resource unavailable conditions on the real-time statistics (RTS) catalog indexes might occur during REBUILD INDEX(ALL) for the catalog and directory indexes.
- If the logging environment requires adding or restoring active logs, restoring archive logs, or performing any action that affects the log inventory in the BSDS, you need to recover the BSDS before catalog and directory objects. To copy active log data sets, use the Access Method Services REPRO function.
A full recovery of the catalog and directory is recommended. However, if you need to do a point-time-recovery, be aware of the implications associated with doing point-in-time recovery of the catalog, directory, and user objects. See Point-in-time recovery of the catalog, directory, and all user objects.
About this task
The following table spaces do not have entries in SYSIBM.SYSLGRNX. The indexes that are associated with these table spaces also do not have entries in SYSIBM.SYSLGRNX, even if they were defined with COPY YES. These objects are assumed to be open from the point of their last image copy, so the RECOVER utility processes the log from that point forward.
- DSNDB01.SYSUTILX
- DSNDB01.DBD01
- DSNDB01.SYSLGRNX
- DSNDB06.SYSCOPY
- DSNDB06.SYSGROUP (SYSGROUP does not have entries in SYSLGRNX during conversion mode and some of the enabling-new-function mode processing. After enabling-new-function mode processing, the SYSGROUP catalog table space is replaced by two new table spaces, DSNDB06.SYSTSSTG and DSNDB06.SYSTSVOL, and these new table spaces do have SYSLGRNX entries.)
- DSNDB01.SYSDBDXA
- If you copy your catalog or directory indexes, use the RECOVER utility to recover your indexes. Otherwise, use the REBUILD INDEX utility to rebuild those indexes.
- For all catalog and directory table spaces, you can list the IBM®-defined indexes that have the COPY YES attribute in the same RECOVER utility statement.
- Recovery of the items in the list can be done concurrently or included in the same job step.
However, the following restrictions apply:
- When you recover the following table spaces or indexes, the job step in which the RECOVER
statement appears must not contain any other utility statements. No other utilities can run while
the RECOVER utility is running.
- DSNDB01.SYSUTILX
- All indexes on SYSUTILX
- DSNDB01.DBD01
- When you recover the following table spaces, no other utilities can run while the RECOVER
utility is running. Other utility statements can exist in the same job step.
- DSNDB06.SYSCOPY
- DSNDB01.SYSLGRNX
- When you recover the following table spaces or indexes, the job step in which the RECOVER
statement appears must not contain any other utility statements. No other utilities can run while
the RECOVER utility is running.
- Add the following steps
between step 12 and step 13:
- Recover DSNDB06.SYSRTSTS.
- Recover or rebuild all indexes on DSNDB06.SYSRTSTS. If no user-defined indexes that are STOGROUP-managed are defined on SYSRTSTS, execute the following utility statement to rebuild IBM-defined and any user-defined indexes on SYSRTSTS:
If user-defined indexes that are STROGROUP-managed are defined on SYSRTSTS, rebuild the IBM-defined indexes individually and then rebuild the user-defined indexes in step 16.REBUILD INDEX (ALL) TABLESPACE DSNDB06.SYSRTSTS
- In step 15 ("Other catalog and directory table spaces and their IBM-defined indexes."), add the following objects.
Table 1. Additional table spaces to recover in conversion mode from Version 8 (CM8) Additional table spaces to recover in conversion mode from Version 8 (CM8) SYSROLES
SYSPLUXA
SYSCONTX
SYSXMLSYSTARG
SYSTSUNI
SYSTSASC
Additional table spaces to recover in conversion mode from Version 9 (CM9) | |||
---|---|---|---|
SYSTSUNI
SYSTSASC |
Procedure
To recover catalog and directory objects:
Results
Messages that you might receive:
- DSNU1530I
- If you are recovering the catalog and directory during migration to a new version, you might receive message DSNU1530I with RC0. This message is issued if your RECOVER statement or REBUILD INDEX statement specifies a catalog or directory object that no longer exists in the new version or has not yet been created in the new version. In this case, DB2 skips the object. No action is required.
- DSNT500I
- An ID with a granted authority
receives message DSNT500I RESOURCE UNAVAILABLE while trying to recover a table space in the catalog
or directory if certain table spaces in the following list are unavailable:
- DSNDB06.SYSTSFAU
- DSNDB06.SYSTSCOL
- DSNDB06.SYSTSTSP
- DSNDB06.SYSTSTPT
- DSNDB06.SYSTSTAB
- DSNDB06.SYSTSIXS
- DSNDB06.SYSTSIXT
- DSNDB06.SYSTSIXR
- DSNDB06.SYSTSIPT
- DSNDB06.SYSTSREL
- DSNDB06.SYSTSFOR
- DSNDB06.SYSTSSYN
- DSNDB06.SYSTSFLD
- DSNDB06.SYSTSTAU
- DSNDB06.SYSTSKEY
- DSNDB06.SYSUSER
If you receive message DSNT500I, you must take one of the following actions:
- Make these table spaces available.
- Run the RECOVER utility on the catalog or directory by using an authorization ID that has the installation SYSADM or installation SYSOPR authority.
- DSNT501I
- If certain table spaces in DSNDB06 are unavailable when an ID with a granted authority tries to rebuild indexes in the catalog or directory, DB2 issues message DSNT501I.
What to do next
After you recover the DB2 catalog and directory, perform the following actions:
- After a point-in-time recovery on the catalog and directory, run the CHECK DATA utility on the objects to ensure consistency.
- Recover XML scheme repository objects. Although the XML schema repository database, DSNXSR, is not part of the DB2 catalog, you need to recover all table spaces in the DSNXSR database and rebuild all indexes on those table spaces immediately after you recover the DB2 catalog. If you perform a point-in-time recovery of the catalog, you need to recover objects in the DSNXSR database to the same point in time.