Journal access paths

 

After you have started journaling for physical files, you can set up explicit journaling of access paths.

You can use the Start Journal Access Path (STRJRNAP) command to start journaling access paths owned by physical files or logical files. When you start journaling access paths for a physical file, the system journals any of these, if they exist:

• Keyed access paths

• Access paths for primary key constraints

• Access paths for unique constraints

• Access paths for referential constraints

• Encoded vector access paths

• Many access paths with sort sequence tables

Some access paths that use an international component for Unicode (ICU) sort sequence table may be too complex to be journaled.

All underlying physical files must be journaled to the same journal before you can start journaling for an access path. The entries created when you journal an access path are used to recover the access path after the system ends abnormally. They are not used when you apply or remove journal entries. You can specify RCVSIZOPT(*RMVINTENT) for the journal to have the system remove these entries when they are no longer needed for recovery. This reduces the disk storage requirements for the journal receiver.

You cannot start journaling for an access path that is in use. The STRJRNAP command must obtain an *EXCL lock on the logical file.

The recommended procedure for starting access path journaling is as follows:

1. Use the STRJRNAP command to start journaling the access path.

2. Save all the underlying physical files, specifying ACCPTH(*YES).

If you have target recovery times for access paths set up on your system, you might not need to set up explicit journaling for access paths.

 

Parent topic:

Starting journaling

Related concepts
Reasons to journal access paths

Related reference
Start Journal Access Path (STRJRNAP) command