Copying NOT LOGGED objects

Note the following recommendations:

• If you are copying an index space of a NOT LOGGED table space, we recommend that you copy the index space and table space together in a group. Copying the index space and the table space together allows you to recover them to the same recoverable point.
• If you are copying a LOB space with a NOT LOGGED base table space, we recommend that you copy the LOB and the base table space together in a group so that you can recover the LOB and the base table space to the same recoverable point.

Consider the following restrictions when using BMC AMI Copy with a NOT LOGGED object:

• BMC AMI Copy does not allow a SHRLEVEL CHANGE copy of a NOT LOGGED index or table space. Nor does BMC AMI Copy allow a SHRLEVEL CONCURRENT PREFERRED request to change to a SHRLEVEL CHANGE request for a NOT LOGGED object. When BMC AMI Copy encounters such requests, BMC AMI Copy issues the following message and ends with a return code of 8:

  BMC30583E SHRLEVEL CHANGE COPY IS NOT ALLOWED FOR objectName BECAUSE OF ITS NOT LOGGED ATTRIBUTE

• BMC AMI Copy does not allow an image copy of a NOT LOGGED index space in ICOPY status if its table space is not also copied in the same group. If you attempt to copy a NOT LOGGED index space without its table space, BMC AMI Copy issues the following message and ends with return code 12:

   BMC30585E INDEX SPACE creator.ixName IS NOT LOGGED AND IN ICOPY STATUS AND MUST BE COPIED IN A GROUP WITH ITS TABLESPACE
• An ALTER to NOT LOGGED from LOGGED invalidates a quiesce point for a SHRLEVEL CHANGE request. For a SHRLEVEL CHANGE QUIESCE AFTER copy, an ALTER to NOT LOGGED after the copy is registered and before the space is quiesced yields a quiesce point that is unrecoverable. The space is recoverable, however, to the point where the ALTER occurred.