Operations that do not go through the crash recovery phase are allowed when roll forward protection is enabled with the OPLOCK qualifier. These operations do not modify the target database, and are useful during the roll forward process. For example, you can use PROSTRCT ADD to add more data space so that the roll forward can continue without error.
Operations that go through the crash recovery phase are rejected under the protection because these operations cause the roll forward process to fail. One example is PROUTIL IDXBUILD. Operations that go through crash recovers are rejected even if the -F option is included on the command line, for example, PROUTIL TRUNCATE BI.
Because the OPLOCK qualifier restricts access during the roll forward, you may find that you cannot perform some operations that previously you could perform during the roll forward process. For example, attempting to modify the target database before the entire roll forward process is completed is not allowed while this option is invoked.
Messages that may appear on the screen and .lg file during the utility's operation include:
Target database has been locked during roll forward process.
Please wait until the roll forward process is finished or use the rfutil -C roll opunlock option to disable the protection.
Target database has been unlocked during roll forward process.
Roll forward process has been stopped with the opunlock option.
Target database has been locked during roll forward process.