Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Recover for Db2 13.1.

SCOPE specification for REBUILD INDEX

Use the SCOPE options to enable 

BMC AMI Recover

 to bypass objects based on specified criteria, thereby defining the scope of the rebuild processing.

To use SCOPE to reduce the scope of an object list, you must first supply the object list. Therefore, REBUILD INDEX SCOPE STATUS (RECP) is not supported.

The SCOPE option is not allowed when BMC AMI Recover is processing clones or RICHK YES is in use.

For the SCOPE specification syntax diagram, see REBUILD-INDEX-syntax.

Option

Description

SCOPE ALL

If you specify SCOPE ALL, BMC AMI Recover rebuilds all of the specified spaces.

SCOPE STATUS(status1,status2,…)

BMC AMI Recover bypasses spaces that are not in at least one of the specified statuses.

The following statuses are valid:

ACHKP, AREO*, AREOR, AUXW, CHKP, COPY, ERROR_RA, GRECP, ICOPY, LPL, NGE, PSRBD, PSRCP, RBDP, RBDP*, RECP, RECP*, REFP, REORP, REST, RESTP, RO, RW, STOP, STOPE, STOPP, UT, UTRO, UTRW, UTUT

Example
REBUILD INDEX OBJECTSET oscreator.osname
  SCOPE STATUS(GRECP,LPL)

SCOPE PENDING

BMC AMI Recover bypasses spaces that are not in RBDP, RBDP*, PSRBD, or RECP status.

To process spaces with other statuses, use SCOPE STATUS(...).

Example
REBUILD INDEX OBJECTSET oscreator.osname
  SCOPE PENDING


Related topics

REBUILD-INDEX-option-descriptions

REBUILDSCOPE


 

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