DBRC and NONRECOV

This does not mean that the database cannot be recovered; it means that the normal recovery methods using image copies and logs are no longer viable.

With NONRECOV databases, no after-image records are written to the logs. A backout is possible because the before-image records are still written, but a roll-forward recovery is not possible because the data is no longer there to roll forward with. Therefore, an alternate recovery method is required.

NONRECOV status should never be an option for a primary database. NONRECOV status is an option for indexes because the Index Build function can rebuild indexes quickly.

The Index Build function checks for your DBRC setting (RECOV or NONRECOV) and sets its default accordingly:

You can specify that the Index Build function not write any records to the RECON data sets for indexes that are defined as NONRECOV. To do this, specify NONRECOV(N) in the DLIGSET0 module. For more information, see DBRC-support.