This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
Next Generation Technology Recover for DB2 for z/OS
RECOVER with ANALYZE ONLY fails with BMC40126E TABLESPACE db.ts, PART n IS IN A STATUS WHICH WILL NOT ALLOW RECOVERY
This message indicates that the object is in a state that is not suitable for RECOVER:
BMC40126E object IS IN A STATUS WHICH WILL NOT ALLOW RECOVERY
Explanation: The object (a table space or an index space) shown in this message is in a status that does not allow the utility to execute (for example, the status UTRW, which indicates a DB2 utility is executing on the space). NGT Recover will not run if the status is unacceptable.
User response: Terminate any IBM utilities or allow utilities to complete. Be sure the space has a status appropriate for running NGT Recover.
When running RECOVER ANALYZE ONLY, it is important to note that RECOVER is intended to give the same result as the analysis that runs for an actual recovery using the same syntax.
The options for running with ANALYZE ONLY against objects which are not in a status compatible with an actual recovery are:
1. Run a simulation (OPTIONS SIMULATE YES with the SIMRCVR command). Since SIMULATE can run without the need for exclusive access to the objects, ANALYZE ONLY correctly does not complain about the object status.
2. Run RECOVER ANALYZE ONLY with INDEP OUTSPACE. The INDEPENDENT (or INDEP) OUTSPACE option redirects the output of the recovery to a data set that is not used by DB2. INDEP OUTSPACE can be run without the need for exclusive access to the objects. Refer to https://docs.bmc.com/docs/display/AFR12100/INDEPENDENT+OUTSPACE+specification for more information.