STARTLOGPOINT—Define the Starting Log Point
The STARTLOGPOINT keyword defines the log point in a data sharing environment from which to recover the tablespace.
The STARTLOGPOINT keyword defines the log point in a data sharing environment from which to recover the tablespace. Use this keyword when performing OBID translation processing.
In a STARTLOGPOINT recovery, the recovery job compares each log record RBA or LRSN with the log point in the data pages. If the RBA or LRSN is less than the log point, the recovery job assumes it has already been applied and ignores the current log record.
Review the following considerations:
- For a non-data sharing environment, use STARTRBA and ENDRBA to identify the log RBA from which to recover the tablespace.
- You can recover a tablespace on a data sharing subsystem using the image copies and logs from a non-data sharing environment. Use STARTLOGPOINT and ENDLOGPOINT to define the log point from which to recover the tablespace.
- Consistency checks cannot be performed on the log ranges to be applied. Verify that the specified range does not include any activity that is not logged; for example, REORG with LOG=NO.
STARTLOGPOINT requires SORTLOG YES and FULLDD.
STARTLOGPOINT is not supported with RECOVER DATABASE, RECOVER INDEX, or REBUILD INDEX.
This keyword has the following format:
- X'byte-string'Specifies the RBA or LRSN. If the RBA or LRSN of a log record isbyte-stringor greater, that record is used in the recovery. Enter the RBA or LRSN as a hexadecimal number preceded by X and enclosed in single quotes.
- HPRBASpecifies that HPRBA determines the starting RBA value. Use this setting when you do not know the value to specify. HPRBA uses the larger value between the HPGRBRBA and PGLOGRBA as the starting RBA value. If the RBA of a log record is equal to or greater than this value, that record is used in the recovery.