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.

NOSYSLGRNG

NOSYSLGRNG causes the SYSIBM.SYSLGRNX table to be bypassed when determining what logs are used during recovery.

NOSYSLGRNG is used automatically when the object to be recovered has been dropped and is being recovered with the DROPRECOVERY option (see Table-space-specification). If you have a damaged SYSIBM.SYSLGRNX table, you can use the NOSYSLGRNG option to avoid accessing those tables. This option causes all log records to be scanned without regard to log ranges, using SYSCOPY entries and end points to determine what log is needed.

Indexes that are defined as COPY NO do not register SYSIBM.SYSLGRNX entries. Recoveries of COPY NO indexes are effectively NOSYSLGRNG recoveries.

Related topic

OPTIONS-option-descriptions

 

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