RECOVERYPOINT

The RECOVERYPOINT option supports the Recovery Management for Db2 timestamp recovery feature.

Important

To use a timestamp recovery, you must have the Recovery Management for Db2 solution, with its valid solution password, installed. Without the solution password, jobs that use RECOVERYPOINT fail.

Related topics

OPTIONS-option-descriptions

Example-17-Using-timestamp-recovery

Recovery Management for Db2 can perform a consistent, point-in-time recovery to a user-specified timestamp by using Inflight Resolution technology. BMC AMI Recover translates the timestamp to an RBA or LRSN, recovers the objects, then resolves all inflight units of work for both data sharing and non-data-sharing systems. You can perform timestamp recovery either by using the online interface of BMC AMI Recovery Manager or by submitting a batch BMC AMI Recover job with the RECOVERYPOINT option. (The online interface of BMC AMI Recovery Manager for Db2 supports this feature on data sharing systems.)

The Inflight Resolution feature of the Recovery Management for Db2 solution enables you to perform a consistent recovery to any LRSN, RBA, or timestamp. The ability to resolve inflight units of work at any point in time completely eliminates the need to perform quiesces to establish consistent recovery points during application execution. The ability to avoid quiesces can dramatically improve the availability of your Db2 data.

For more information, see the Recovery Management for Db2 documentation and the BMC AMI Recovery Manager for Db2 documentation .

The RECOVERYPOINT option specifies the recovery point and directs the utility to resolve inflight units of recovery. You specify the RECOVER statements as if recovery to the current point in time is specified. You can have multiple RECOVER statements in the input. The RECOVERYPOINT option effectively determines what the current recovery point is. You can specify the TIMESTAMP option or the LOGPOINT option (but not both) with RECOVERYPOINT.

In the following examples, the first example shows the syntax with the TIMESTAMP option and the second example shows the syntax with the LOGPOINT option:

OPTION RECOVERYPOINT URIDDDN(output) TIMESTAMP yyyy-mm-dd-h.mm.ss.tttttt
OUTPUT(output) UNIT SYSDA
               DSNAME dataSetName
RECOVER TABLESPACE databaseName.tableSpaceName
        TABLESPACE databaseName2.tableSpaceName2
OPTION RECOVERYPOINT URIDDDN(output) LOGPOINT X'logPoint'
OUTPUT(output) UNIT SYSDA
               DSNAME dataSetName
RECOVER TABLESPACE databaseName.tableSpaceName
        TABLESPACE databaseName2.tableSpaceName2

You should consider the following items when you use the RECOVERYPOINT option:

  • RECOVERYPOINT is not valid with the use of the ACCUM or IMPORT commands in the same SYSIN.
  • RECOVERYPOINT interacts with the SIMULATION option in the following ways:
    • If OPTION SIMULATE specifies no LOGPOINT, OPTION RECOVERYPOINT determines the ending point of the simulation.
    • If OPTION RECOVERYPOINT specifies a TIMESTAMP, OPTION SIMULATE must not specify a LOGPOINT.
    • If both OPTION RECOVERYPOINT and OPTION SIMULATE specify LOGPOINT, they must both specify the same value.
  • To use OUTCOPY ONLY and OBIDXLAT with OPTION RECOVERYPOINT, you will need to rebuild any indexes on the target table spaces.
  • If the RECOVERYPOINT specifies a point on the log during a SHRLEVEL CHANGE image copy, forward recovery from that copy fails if the copy includes any changes that were inflight at the recovery point. If that happens, BMC AMI Recover attempts to fall back to a previous copy.
  • If OPTION RECOVERYPOINT is specified, no other point-in-time specification (TORBA, TOLOGPOINT) is allowed.

The following table describes options that you can use for RECOVERYPOINT:

Option

Description

LOGPOINT LOGMARKlogMarkName ( logMarkGeneration)

The LOGPOINT LOGMARKlogMarkName option specifies the recovery point as 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 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 not at a quiesce point or a quiet point for the spaces or spaces that you are recovering, you should use a timestamp recovery by using OPTION RECOVERYPOINT LOGMARK syntax. If you know that the log mark is at a quiesce point or a quiet point, consider using RECOVER TOLOGPOINT LOGMARK syntax (TORBA or TOLOGPOINT) to perform a point-in-time recovery.

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.

LOGPOINT X'logPoint'

The LOGPOINT X'logPoint' option specifies the recovery point for the recovery.

TIMESTAMP yyyy-mm-dd-h.mm.ss.tttttt

The TIMESTAMP option specifies the recovery point. If you use TIMESTAMP, you cannot use LOGPOINT. TIMESTAMP requires a value to at least the second. You need to specify unspecified levels of detail with zeros. For example, a TIMESTAMP specification that only goes to the minute level needs to specify zeros for the seconds level.

OPTION RECOVERYPOINT TIMESTAMP 2013-01-15-09.15.00

The TIMESTAMP value is converted to a log point and adjusted for Daylight Savings Time. The Daylight Savings Time adjustment uses the TZRULE installation option. For information about this installation option, see TZRULE-NONE.

URIDDDN (output)

You use the URIDDDN parameter to identify an OUTPUT statement that is used to allocate a data set where inflight units of recovery are reported.

The URIDDN parameter refers to an OUTPUT statement to capture a UNIT name and data set name (DSNAME). If you specify the SPACE parameters, BMC AMI Recover also uses them. If the OUTPUT statement specifies a tape unit, BMC AMI Recover ignores it. BMC AMI Recover honors any SMS class specifications (DATACLAS, MGMTCLAS, STORECLAS) on the OUTPUT statement. BMC AMI Recover ignores any other OUTPUT statement parameters.

If the RECOVERYPOINT request does not include a URIDDDN specification, BMC AMI Recover defaults the data set name to:

&SYSUID..D&DATE..T&TIME.URIDS

An example data set name that uses this default is RDAMSM.D120206.T171005.URIDS.

If the DSNAME parameter on the OUTPUT statement is a relative GDG name, BMC AMI Recover resolves it to an absolute name before allocation.

If the request does not include a URIDDDN specification or if the URIDDDN does not include UNIT, BMC AMI Recover uses the WKUNIT value defined in the installation options.

If the request does not include a URIDDDN specification or if the URIDDDN does not include SPACE parameters, BMC AMI Recover defaults the space to TRK(1,1).

Important

BMC AMI Recover deletes this data set at the end of a successful job.

 

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