TORBA or TOLOGPOINT specification for LOGSCAN
The following section describes the TORBA or TOLOGPOINT specification shown in LOGSCAN syntax.
| TORBA or TOLOGPOINT | Use TORBA or TOLOGPOINT to scan a table space or index to a prior point in time identified by a log point. (For more information about using TORBA or TOLOGPOINT with table spaces and indexes, see LOGSCAN command dependencies and prohibitions.) You can use TORBA or TOLOGPOINT interchangeably, regardless of the version of Db2 that you are using. |
|---|---|
| TORBA LASTQUIESCE (relativeGenerationNumber) or TOLOGPOINT LASTQUIESCE (relativeGenerationNumber) | Use TORBA LASTQUIESCE or TOLOGPOINT LASTQUIESCE to scan to the most recent quiesce point registered in SYSIBM.SYSCOPY for the table space being scanned. For indexes, the most recent quiesce of the table space is used. BMC AMI Recover scans log records with starting log points less than or equal to the most recent quiesce point, unless BACKOUT is used. For BACKOUT requests, BMC AMI Recover scans log records with starting log points greater than the most recent quiesce point. 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 scanning multiple table spaces in a single LOGSCAN TABLESPACE command statement, all of the table spaces must have a common last quiesce point. However, if you are using multiple LOGSCAN TABLESPACE command statements to scan multiple table spaces, each table space can have a different last quiesce point. The same is true for indexes if you are using LOGSCAN INDEX or LOGSCAN INDEXSPACE. LASTQUIESCE can be abbreviated as LASTQ. Important If you use LASTQUIESCE and the quiesce is prior to the 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 scan a set of table spaces and indexes to the most recent common quiesce point registered in SYSIBM.SYSCOPY. The scanning of indexes is based on the common quiesce point of the owning table space. BMC AMI Recover scans log records with starting log points less than or equal to the most recent quiesce point common to all table spaces and indexes listed, unless BACKOUT is used. For BACKOUT requests, BMC AMI Recover scans log records with starting log points greater than the most recent common quiesce point. If no common quiesce point exists for all table spaces and indexes specified, an error message is issued. If you specify this option when only one table space or index is scanned, the effect is exactly the same as using TORBA LASTQUIESCE. You can use TORBA LASTCOMMONQ or TOLOGPOINT LASTCOMMONQ with LOGSCAN 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 scan to the log point of the last ARCHIVE LOG MODE(QUIESCE) command issued for the Db2 subsystem. BMC AMI Recover scans only log records with starting log points less than or equal to the most recent ARCHIVE LOG MODE(QUIESCE) command, unless BACKOUT is used. For BACKOUT requests, BMC AMI Recover scans log records with starting log points greater than the most recent ARCHIVE LOG MODE(QUIESCE) command. 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 scan to the log point of the last normal system shutdown. BMC AMI Recover scans only log records with starting log points less than or equal to the most recent successful subsystem shutdown, unless BACKOUT is used. For BACKOUT requests, BMC AMI Recover scans log records with starting log points greater than the most recent successful subsystem 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 scan 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 scan 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:
|
| TORBA X'logPoint' or TOLOGPOINT X'logPoint' | Use TORBA X'logPoint' or TOLOGPOINT X'logPoint' to scan to a prior point in time identified by the log point, 'logPoint'. BMC AMI Recovery Manager scans only log records with starting log points less than or equal to 'logPoint', unless BACKOUT is used. For BACKOUT requests, BMC AMI Recover scans log records with starting log points greater than 'logPoint.' '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 may enhance the performance of a point-in-time LOGSCAN request significantly. The following restrictions apply:
|
Comments
Log in or register to comment.