Consultor Eletrônico

SUMMARY:

This Solution provides some guidelines for using the Progress database backup utility PROBKUP with the -norecover parameter to backup a standby database where AI files are being applied.

EXPLANATION:

As part of a contingency plan, you can keep a standby copy of a production database and keep it updated using the Progress journaling capability called After Imaging. You can implement data replication by applying the AI files from the production database to the standby database from time to time (NOTE: For more details about this replication technique, please consult the Progress Database Administration Guide and Reference, Chapter 14.2 Implementing Log-based Site Replication.)

In order to execute the ROLL FORWARD operation, the standby database needs to be in sync with the AI files. If you need to backup the standby database using PROBKUP, the utility will perform a crash recovery if necessary.

If you try to apply the subsequent AI files from the production database to the standby database you might get the following error messages complaining about the database timestamp:

SYSTEM ERROR: Roll forward of file sp2k.a4 did not complete
normally (1046)

SYSTEM ERROR: End of last note read is at file offset 0 (1048)

SOLUTION:

To avoid synchronization problems with the standby database and the AI files, you can use the parameter -norecover with the PROBKUP utility. Using -norecover, the PROBKUP utility will not perform the crash recovery process and you will be able to keep the timestamp of the standby database. The syntax for PROBKUP with the -norecover parameter is:

PROBKUP <db-name> <device-name> -norecover

Using the -norecover parameter with PROBKUP you will get the following message in the database log file:

Probackup session started with the norecover option in effect.
(5581)


References to Written Documentation:

Progress Database Administration Guide and Reference