Typically, the roll forward process involves multiple AI files, with each AI file being processed by a separate roll forward session. This sequence of sessions should not be interrupted until the final AI file is processed to complete all the phases of the crash recovery.
The OPLOCK qualifier provides the ability to enforce a protection mechanism during the roll forward process, so that there can be no interruption to the target database before the final roll forward session is completed. This option must be enabled together with the rolling forward of an AI file. For example:
rfutil db-name -C roll forward oplock -a ai-name
Once the protection is enabled with OPLOCK, there are two ways to disable it:
At the end of the final roll forward or roll forward retry session (after all the phases of crash recovery have been finished) the protection is automatically turned off.
If you want to disable the protection (in situations where it is not desirable to roll forward to the last extent), use the OPUNLOCK qualifier as shown:
rfutil db-name -C roll opunlock
The OPUNLOCK qualifier:
Disables the protection mechanism, making the database accessible to other users or utilities
Completes the phases of the crash recovery
Note: The OPUNLOCK qualifier should only be used for situations with missing AI files. Once OPUNLOCK is run, the roll forward process stops.
At the end of the final roll forward or roll forward retry session (after all the phases of crash recovery have been finished) the protection is automatically turned off.
