TOCOPY specification
For TOCOPY syntax, see RECOVER TABLESPACE, RECOVER INDEX, and RECOVER INDEXSPACE syntax.
TOCOPY
The TOCOPY option specifies the last image copy to be processed by BMC AMI Recover to recover the specified table space (full or incremental copies) or index (full copies only). The recovery process ends after this image copy has been applied. If you specify an incremental copy for table space recovery, the prior full copy and any intervening incremental copies are also used in the restore process. Except when used with the INCOPY option, the image copy specified must be registered in SYSIBM.SYSCOPY (or in BMCXCOPY for indexes) as an image copy or as a 'kept' incremental copy (as specified by the BMC AMI Copy for Db2 product) for the specified object or object data set. When you specify TOCOPY, the log is not used to apply updates that are made after the copy.
After a TOCOPY recovery, the data in the space reflects the data as of the time of the specified image copy. Any log record or activity after the TOCOPY recovery is no longer reflected in the space but may be reinstated by a subsequent TOLOGPOINT recovery.
You can specify the image copy by its data set name or by the keyword LASTCOPY.
If the copy named was created by using SHRLEVEL CHANGE, BMC AMI Recover issues a warning (message BMC40971), but continues processing. (With a SHRLEVEL CHANGE copy, the pages may not be logically consistent.)
Important
When you use TOCOPY, you may specify only one table space. To recover more than one table space by using TOCOPY, you can use multiple RECOVER TABLESPACE command statements. The same is true for index recovery with RECOVER INDEX or RECOVER INDEXSPACE.
If you are recovering directly to the real Db2 data sets (not using INDEPENDENT OUTSPACE and not using OUTCOPY ONLY), a point-in-time recovery event is recorded in SYSIBM.SYSCOPY or BMCXCOPY. However, if you are not changing the actual objects and specify TOCOPY, the event is not recorded in SYSIBM.SYSCOPY (or BMCXCOPY) because the actual Db2 data sets are not changed.
| Option | Description | ||||||
|---|---|---|---|---|---|---|---|
| TOCOPY LASTCOPY (relativeGenerationNumber) | TOCOPY LASTCOPY specifies that the most recent image copy (full or incremental for table spaces, full for indexes) registered in SYSIBM.SYSCOPY (or BMCXCOPY for indexes) is the last one to be processed by BMC AMI Recover to recover the specified object. Optionally, you can add a relative generation number in parentheses to indicate the copy to use. A relative generation number of (0) uses the most recent image copy. For example, TOCOPY LASTCOPY (-1) indicates the use of the copy before the most recent copy. When used with the INCOPY option, LASTCOPY means the last copy specified in your INCOPY list. | ||||||
| TOCOPY dataSetName | TOCOPY dataSetName specifies that the image copy data set named (full or incremental for table spaces, full for indexes) is the last one to be processed by BMC AMI Recover to recover the object. The named copy must be registered in SYSIBM.SYSCOPY (or BMCXCOPY for indexes or Instant Snapshot copies) unless you are choosing the INCOPY option. In that case the named copy must be the last copy specified in your INCOPY list. When the data set is part of a generation data group (GDG), you can specify either the full name or the relative GDG name. If you specify a relative GDG name for an existing data set, use either (0) or (-n) for the relative generation. Do not refer to it as the (+1) generation. The most recent data set is the (0) generation, even if it was created in a previous step in the same job. The following restrictions apply to the TOCOPY dataSetName option:
Important TOCOPY dataSetName is not allowed with OBJECTSET.
|
Comments
Log in or register to comment.