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.

Using SHRLEVEL CHANGE full copies for recovery

You can make a SHRLEVEL CHANGE image copy ('fuzzy' copy) of a table space while updates to the table space are in progress.

Using this type of image copy is not a problem during recovery because IBM Db2 RECOVER and BMC AMI Recover use the log point recorded for the SHRLEVEL CHANGE copy, which is the log point before the start of the copy.

This log point is the point at which the recover utilities begin examining log records. All log records that might need to be applied to the table space are examined. Because each Db2 page contains the log point of the last update to the page, both utilities can determine whether a log update really needs to be applied to the page or if that update is already reflected in the current page image.

Attempting to recover to a SHRLEVEL CHANGE copy

With BMC AMI Recover, you can specify RECOVER TABLESPACE TOCOPY that uses a SHRLEVEL CHANGE copy.

However, the data on such a copy may not be consistent. This procedure is not recommended and BMC AMI Recover issues a warning to this effect.

For more information, see TOCOPY-specification.

 

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