Initiating fast recovery to verify that no open transactions exist

A shutdown procedure does not guarantee a rollback of all open transactions. To guarantee that the source database server has no open transactions, put the source database server in quiescent mode and initiate fast recovery.

Run the following command to enter quiescent mode and initiate a fast recovery:

oninit -s

UNIX/Linux Only: On UNIX™ or Linux™, the oninit-s command rolls forward all committed transactions and rolls back all incomplete transactions since the last checkpoint and then leaves a new checkpoint record in the log with no open transactions pending.

You must run the oninit -s command before you initialize the new version of HCL OneDB™. If any transactions remain when you try to initialize the new database server, the following error message appears when you try to initialize the new database server, and the server goes offline:

An open transaction was detected when the database server changed log versions. 
Start the previous version of the database server in quiescent mode and then shut 
down the server gracefully, before migrating to this version of the server.

For more information about fast recovery, see your HCL OneDB Administrator's Guide.

After you put the database server in quiescent mode and initiate fast recovery, issue the onmode -yuk command to shut down the database server. Then review the online.log file for any possible problems and fix them.

Only after proper shutdown can you bring the new database server (HCL OneDB Version 2.0.0.0) through the migration path. Any transaction that is open during the migration causes an execution failure in fast recovery.