Infodb Command Output – Checkpoint History for Journal Section
The following is sample output from the checkpoint history for journal section:
----Checkpoint History for Journal--------------------------------------
Date Ckp_sequence First_jnl Last_jnl valid mode
--------------------------------------------------------------------
11-NOV-2015 13:23:43.57 1 1 1 1 OFFLINE
11-NOV-2015 13:24:50.40 2 2 2 1 ONLINE
11-NOV-2015 13:58:52.65 3 3 3 1 ONLINE,
TABLE
Fields are as follows:
Date
Indicates the date and time the checkpoint operation was done.
Ckp_sequence
Indicates the sequence number of the checkpoint.
First_jnl
Indicates the journal sequence number of the first (or oldest) journal file corresponding to the checkpoint.
Last_jnl
Indicates the journal sequence number of the last (or youngest) journal file corresponding to the checkpoint.
Valid
Indicates whether the checkpoint is valid (1 implies valid, 0 implies invalid).
Mode
Describes the checkpoint operation:
– OFFLINE indicates the checkpoint operation was offline
– ONLINE indicates the checkpoint operation was online
– TABLE indicates the checkpoint is a table checkpoint
– NO_X100 is set for all checkpoints prior to making a database X100 enabled, and also when a rollforwarddb -j is done. Ckpdb uses this flag to determine the X100 processing required. In the case where it was set after rollforwarddb -j, it does not affect the status of the checkpoint; instead it indicates different X100 processing is required when the next checkpoint is taken.
To recover the entire database, you must specify #c2, for example, in the rollforwarddb command to roll forward from the database checkpoint. Checkpoint 3 was taken on selected tables.
Last modified date: 04/03/2024