Recovery Server Offline Error Handling
Offline redo/undo processing occurs during installation startup if the installation previously shut down abnormally. Before other servers start, the Recovery Server processes the log file. It first re-does all updates in the log from the last consistency point, then un-does any open transactions.
You can specify how the Recovery Server will handle errors that may occur during this processing by using configuration parameters in CBF:
offline_error_action
Specifies the action the Recovery Server takes if errors occur during Recovery Server startup, offline redo/undo recovery processing, after an abnormal shutdown.
Valid values are:
CONTINUE_IGNORE_TABLE
Marks the table inconsistent and continues recovery on all other tables in the database.
The database will be marked TABLE/INDEX inconsistent. A table rollforward is required to make the database consistent.
CONTINUE_IGNORE_DB
(Default) Marks the database inconsistent, does not shut down the installation.
A database rollforward is required to make the database consistent.
STOP
Shuts down the installation instead of marking a database inconsistent. Error messages in the error log and the RCP log file may help to diagnose the recovery problems. If the problem is related to a resource or environment, you should fix the problem before restarting the installation.
Last modified date: 08/28/2024