Table space and index space status
If the output from a table space or index space recovery is to a Db2 data set, the initial status of the target space must be acceptable to
BMC AMI Recover
before a recovery can start.
However, if SIMULATE YES is specified or INDEPENDENT OUTSPACE is specified to direct the recovery output of a table space to a non Db2 data set, the initial status of the space is not a factor in the recovery and is ignored by BMC AMI Recover. Also, no status changes are made to the space. But if you do not specify INDEPENDENT INTABLESPACE when you use the INDEPENDENT OUTSPACE option with REBUILD INDEX, the table space is stopped and started as READ ONLY (RO). In this case, the initial table space status is a factor.
If the recovery is to a Db2 data set and the initial status of the target table space or index space is not acceptable, BMC AMI Recover terminates. If the status is acceptable, BMC AMI Recover stops all of the spaces during the ANALYZE phase to ensure exclusive use of the spaces during the recovery.
BMC AMI Recover sets the appropriate pending status (RECP or RBPD) for each space in anticipation of processing the space. When the recovery of the space is completed successfully, the pending status is turned off. If the job fails, a space may be left in a pending status even though it was never processed
If you set the RDB2STAT parameter to NO, BMC AMI Recover will leave the spaces stopped to ensure that you take some action before allowing the spaces to be used. For example, you may want to ensure that all related spaces have been recovered to the same point, or you may want to take image copies for future recovery if copies were not taken during processing.
If BMC AMI Recover determines that the spaces can be used when a recovery is complete, the initial status is restored if the RDB2STAT parameter is set to YES. (You can also use RDB2STAT(RW) or RDB2STAT(RO) on the EXEC statement as described on RDB2STAT override parameter (rdb2Stat) to set the space in RW or RO status at the end of the run.)
If a table space status is copy pending before a recovery and an output image copy is successfully registered, BMC AMI Recover removes the COPY status. BMC AMI Recover does not remove the COPY status for an image copy that was created with the OUTCOPY ONLY option.
If REBUILD INDEX or RECOVER BUILDINDEX of a nonpartitioned index space on a partitioned space fails during the BUILD phase, BMC AMI Recover sets page set recover pending (PSRCP) or page set rebuild pending (PSRBD) status on the index space.
Initial table space and index space status
The following table shows the action taken by BMC AMI Recover for acceptable and unacceptable initial Db2 table space status.
BMC AMI Recover command | BMC AMI Recover action for table spaces with acceptable initial status 1 | BMC AMI Recover action for table spaces with unacceptable initial status 1 | Unacceptable initial table space status |
|---|---|---|---|
RECOVER TABLESPACE (with or without index recovery or unload keys) without BACKOUT option | Issues the Db2 command STOP AT (COMMIT) for the table space | BMC AMI Recover terminates | |
RECOVER TABLESPACE (with or without index recovery or unload keys) with BACKOUT option | Issues the Db2 command STOP AT (COMMIT) for the table space | BMC AMI Recover terminates | RECP LPL GRECP DEFER WEPR REFP UTUT UTRW UTRO |
REBUILD INDEX SHRLEVEL REFERENCE (but not REBUILD INDEX SHRLEVEL CHANGE) | Issues the Db2 command STOP AT (COMMIT) for the table space and restarts in ACCESS(RO) | BMC AMI Recover terminates | RESTART UTUT UTRW RECP DEFER LPL GRECP AREST RESTP WEPR REFP |
1 When the recovery is to a non Db2 data set, the initial status of a table space is ignored and no status changes are made.
2 Acceptable if the recovery is to a point in time.
This next table shows the action taken by BMC AMI Recover for acceptable and unacceptable initial Db2 index space status.
BMC AMI Recover command | BMC AMI Recover action for index spaces with acceptable initial status 1 | BMC AMI Recover action for index spaces with unacceptable initial status 1 | Unacceptable initial index space status |
|---|---|---|---|
RECOVER INDEX or RECOVER INDEXSPACE without BACKOUT option | Issues the Db2 command STOP AT (COMMIT) for the index space | BMC AMI Recover terminates | |
RECOVER INDEX or RECOVER INDEXSPACE with BACKOUT option | Issues the Db2 command STOP AT (COMMIT) for the index space | BMC AMI Recover terminates | RECP RESTART UTUT UTRW UTRO RBDP PSRCP PSRBD WEPR REFP |
REBUILD INDEX SHRLEVEL REFERENCE or RECOVER BUILDINDEX | Issues the Db2 command STOP AT (COMMIT) for the index space | BMC AMI Recover terminates | RESTART UTUT UTRW UTRO AREST RESTP |
RECOVER UNLOADKEYS | No action is required, any status is acceptable | No action is required, any status is acceptable | N/A |
1 When the recovery is to a non Db2 data set, the initial status of a table space is ignored and no status changes are made.
2 Acceptable if the recovery is to a point in time.
When the initial status is acceptable, BMC AMI Recover issues Db2 commands that give control of the space to BMC AMI Recover and allow the recovery to start. When the initial status is not acceptable, BMC AMI Recover terminates. However, if the output from an index or table space recovery is to be directed to a non Db2 data set, BMC AMI Recover does not issue any Db2 commands.
Restoring initial status
BMC AMI Recover provides the RDB2STAT utility parameter, which determines whether Db2 objects should be returned to their original status when a recovery job is complete. If you specify RDB2STAT(YES) (or default to the RDB2STAT installation option when it is set to YES), BMC AMI Recover handles the space as follows:
- Starts the space with ACCESS(RW) status if the space was in RW status initially
- Starts the space with ACCESS(RO) if the space was in RO status
- Will not start the space if the space was in STOP, STOPE, LSTOP, or STOPP status
- Starts the space with START ACCESS (FORCE) if the space was in DEFER, LPL status, GRECP status, or internal ERROR RANGE status
You may also use RDB2STAT(RW) and RDB2STAT(RO) on the EXEC statement to request that Db2 objects be restored to a status of RW or RO, regardless of their initial status. For a description of the RDB2STAT parameter, see RDB2STAT override parameter (rdb2Stat).
If you do not specify RDB2STAT, BMC AMI Recover defaults to the value that is specified for the RDB2STAT installation option.
Related topic