RECOVER TABLESPACE, RECOVER INDEX, and RECOVER INDEXSPACE commands

The RECOVER TABLESPACE, RECOVER INDEX, and RECOVER INDEXSPACE commands specify one or more table spaces or indexes, or table space or index data set, for recovery. You can recover a single table space, index, or data set to a specific image copy, to a specific log point, or to the current state (by using all of the log records that apply).

Multiple table spaces, indexes, or data sets can be recovered to a specific log point or to the current state. You can have as many RECOVER TABLESPACE, RECOVER INDEX, or RECOVER INDEXSPACE command statements in a job step as necessary. However, unlike the IBM Db2 RECOVER utility, BMC AMI Recover examines all of the command statements in the job step before processing starts so that all log processing can be combined and activities can be optimally scheduled.

Important

If you request simulation mode with the SIMULATE YES option, which requires a valid Recovery Management for Db2 solution password, you must use SIMRCVR TABLESPACE, SIMRCVR INDEX, and SIMRCVR INDEXSPACE instead of RECOVER TABLESPACE, RECOVER INDEX, and RECOVER INDEXSPACE.

For more information, see RECOVER-TABLESPACE-RECOVER-INDEX-and-RECOVER-INDEXSPACE-option-descriptions.

Important

This space assumes that RECOVER INDEX uses copies, logs, or both. However, BMC AMI Recover can interpret the RECOVER INDEX syntax as REBUILD INDEX if the option INDEXLOG is set to NO (the default). INDEXLOG AUTO could have the same effect in some circumstances. INDEXLOG is set by using the INDEXLOG installation option or the INDEXLOG option on the OPTIONS command (see INDEXLOG-NO and INDEXLOG).

This section describes the syntax of the RECOVER TABLESPACE, RECOVER INDEX, and RECOVER INDEXSPACE commands and their options.



 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*