TORBA or TOLOGPOINT specification

Use TORBA or TOLOGPOINT to recover a table space or index to a prior point in time identified by a log point.

The syntax diagram for the TORBA or TOLOGPOINT specification is in RECOVER-TABLESPACE-RECOVER-INDEX-and-RECOVER-INDEXSPACE-syntax.

Important

Place syntax for the TORBA or TOLOGPOINT specification after the syntax for Table space specification, Single index specification, or Multiple index specification.

Related topics

RECOVER-TABLESPACE-RECOVER-INDEX-and-RECOVER-INDEXSPACE-option-descriptions

Example-5-Recovering-to-a-specific-log-point

RECOVERYPOINT

For more information about using TORBA or TOLOGPOINT with table spaces and indexes, see Additional-RECOVER-INDEX-and-RECOVER-INDEXSPACE-limitations.

TORBA or TOLOGPOINT

You can use TORBA or TOLOGPOINT interchangeably, regardless of the version of Db2 that you are using. For a non-data-sharing system, the recovery point must be specified as an RBA. For a data sharing system, the recovery point must be specified as an LRSN.

A TOLOGPOINT recovery returns a space to a point that reflects all activity on the space up to and includes a log record at the log point specified. Any log record or activity higher than TOLOGPOINT is no longer reflected in the space but might be reinstated by a subsequent TOLOGPOINT recovery.

Important

If you are recovering directly to the real Db2 data sets and are not using INDEPENDENT OUTSPACE, a point-in-time recovery event is recorded in SYSIBM.SYSCOPY for table spaces and COPY YES indexes or BMCXCOPY for COPY NO indexes.

In contrast, if you are using the INDEPENDENT OUTSPACE option to recover to non-Db2 data sets and specify TORBA or TOLOGPOINT, the event is not recorded in SYSIBM.SYSCOPY or BMCXCOPY because the actual Db2 data sets are not changed. Using OUTCOPY ONLY with TORBA or TOLOGPOINT is not a point-in-time recovery; instead, you are simply creating a copy as of an earlier point in time. You can register the copy in SYSCOPY or BMCXCOPY, but no other event is recorded.

Option

Description

TORBA LASTQUIESCE (relativeGenerationNumber) or TOLOGPOINT LASTQUIESCE (relativeGenerationNumber)

Use TORBA LASTQUIESCE or TOLOGPOINT LASTQUIESCE to recover to the most recent quiesce point registered in SYSIBM.SYSCOPY for the table space being recovered. For index recovery, the most recent quiesce of the table space is used.

Optionally, you can add a relative generation number in parentheses to indicate the quiesce to use. A relative generation number of (0) uses the most recent image copy. For example, TOLOGPOINT LASTQUIESCE (-1) indicates the use of the quiesce before the most recent quiesce.

If you are recovering multiple table spaces in a single RECOVER TABLESPACE command statement, all of the table spaces must have a common last quiesce point. However, if you are using multiple RECOVER TABLESPACE command statements to recover multiple table spaces, each table space can have a different last quiesce point. The same is true for index recovery with RECOVER INDEX or RECOVER INDEXSPACE.

LASTQUIESCE can be abbreviated as LASTQ.

Important

If you use LASTQUIESCE and the quiesce is prior to an ALTER ADD PART, the recovery will fail. You must specify a hard-coded RBA. If the partition was added for a partition-by-growth universal table space, you can use the LASTQUIESCE option.

TORBA LASTCOMMONQ or TOLOGPOINT LASTCOMMONQ

Use TORBA LASTCOMMONQ or TOLOGPOINT LASTCOMMONQ to recover a set of table spaces and indexes to the most recent common quiesce point registered in SYSIBM.SYSCOPY. Index recoveries are based on the common quiesce point of the owning table space. If no common quiesce point exists for all table spaces and indexes specified, an error message is issued.

If you use this option when only one table space or index is recovered, the effect is exactly the same as using TORBA LASTQUIESCE.

You can use TORBA LASTCOMMONQ or TOLOGPOINT LASTCOMMONQ with RECOVER INDEX (ALL) or when multiple index space specifications exist in one command statement.

TORBA LASTARCHQ or TOLOGPOINT LASTARCHQ

Use TORBA LASTARCHQ or TOLOGPOINT LASTARCHQ to recover to the log point of the last ARCHIVE LOG MODE(QUIESCE) command issued for the Db2 subsystem.

When you use this option, BMC AMI Recover issues a message indicating the date and time of the ARCHIVE LOG MODE(QUIESCE) command used.

TORBA LASTSHUTDOWN or TOLOGPOINT LASTSHUTDOWN

Use TORBA LASTSHUTDOWN or TOLOGPOINT LASTSHUTDOWN to recover to the log point of the last normal system shutdown. When you use this option, BMC AMI Recover issues a message indicating the date and time of the last successful system shutdown. You cannot use the LASTSHUTDOWN keyword to recover to the log point of an abnormal Db2 termination. When you use this keyword, ensure that the table spaces and indexes were not in an exception status at the shutdown.

Important

In a data sharing environment, this keyword is used to recover to the last successful shutdown of the member subsystem on which the job is running, without regard to other member subsystems. For this reason, use extreme caution when you use TORBA LASTSHUTDOWN or TOLOGPOINT LASTSHUTDOWN in a data sharing environment to ensure that the shutdown used is really a point of data consistency.

To ensure that the last successful shutdown is really a point of data consistency, one of the following conditions must be true:

  • The subsystem on which the BMC AMI Recover job is running was the last member of a data sharing group to be stopped.
  • All updates to the table spaces and indexes to be recovered occurred on the subsystem on which the BMC AMI Recover job is running.

TORBA LOGMARK logMarkName (logMarkGeneration) or TOLOGPOINT LOGMARK logMarkName (logMarkGeneration)

Use TORBA LOGMARK logMarkName or TOLOGPOINT LOGMARK logMarkName to recover to a prior point in time identified by a log mark that was created in BMC AMI Log Master.

Optionally, you can add a log mark generation number in parentheses, (logMarkGeneration). If you do not specify a log mark generation, BMC AMI Recover uses the most recent version of the log mark. You can use one of the following ways to specify the log mark generation:

  • If you specify a log mark generation as less than or equal to zero (< = 0), BMC AMI Recover treats the generation as a relative generation. BMC AMI Recover refers to the most recent log mark with the generation of zero (0). The previous generation of the log mark is referred to with (-1), and so on.
  • If you specify a log mark generation as greater than zero (> 0), BMC AMI Recover treats the generation as an absolute generation number and use the specified version of the log mark.

Important

The way that you specify an absolute generation number for a log mark in BMC AMI Recover is different than the way you specify the absolute generation number in BMC AMI Log Master.

When you create the log mark, you can specify if BMC AMI Log Master should create a quiesce point. You can also specify that BMC AMI Log Master set a log mark at a quiet point or a non-quiet point. If you know that the log mark is at a quiesce or a quiet point for the space or spaces that you are recovering, use this option to perform a point-in-time recovery. If the log mark is not at a quiet point, you should use a timestamp recovery using the option RECOVERYPOINT LOGMARK logMarkName.

Important

You must determine if the log mark is at a quiesce or quiet point or not. If you are not sure that there is a quiesce or quiet point, a timestamp recovery might be best although it will take longer to look for inflight transactions.

TORBA X'logPoint' or TOLOGPOINT X'logPoint'

Use TORBA X'logPoint' or TOLOGPOINT X'logPoint' to recover to a prior point in time identified by the log point, 'logPoint'. Except with BACKOUT, only log records with starting log points less than or equal to 'logPoint' are used by BMC AMI Recover.

'logPoint' is a string of up to twelve hexadecimal digits.

BACKOUT

BACKOUT invokes the backout strategy for point-in-time recovery by using log points (TORBA, TOLOGPOINT). This strategy assumes that spaces are undamaged and that you require a reset to a specific point in time. The spaces are used with the log records between the point in time and the current point to back out to the required state. Using BACKOUT might enhance the performance of a point-in-time recovery significantly.

The following restrictions apply:

  • All recovery requests in SYSIN must use BACKOUT. You cannot mix backward and forward recovery in SYSIN.
  • The space must be current as of the last logged activity and not damaged in any way. Multi-data-set, nonpartitioned spaces must have all data sets recovered (DSNUM ALL).
  • The space must not be in RECP, RECP*, RBDP, RBDP*, RBDPM, PSRCP, PSRBD, GRECP, WEPR, REFP, or STOPE status or have an LPL range.
  • No LOAD or REORG events can exist between the log point specified and the current point in time. For indexes, no REBUILD INDEX events can exist in this range.
  • No prior point-in-time recovery with a START_RBA greater than the log point requested and a PIT_RBA less than the log point requested can exist.
  • BACKOUT might not be requested with the following BMC AMI Recover options:
    • INDEP OUTSPACE
    • OUTCOPY ONLY
    • OBIDXLAT
    • DROPRECOVERY

    • LOGONLY or LOGAPPLY ONLY

      Important

      BACKOUT uses only logs and spaces but requires that the spaces be current. The LOGONLY and LOGAPPLY ONLY options imply applying log records going forward by using a space restored to a previous state.

  • Change accumulation files are not allowed with BACKOUT because they are not properly ordered. Output accumulation files are also not supported because they are defined from the point of the last image copy to the current point in time.

 

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