Kbase P16380: -norecover Option To Backup a Standby Database with PROBKUP
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Unverified
SYMPTOM(s):
SYSTEM ERROR: Roll forward of file <file name> did not complete normally (1046)
SYSTEM ERROR: End of last note read is at file offset (1048)
SYSTEM ERROR: Physical redo, BKUPDCTR=<number>, note updctr=<number>. (1028)
CHANGE:
Deleted standby database. Recreated standby database out of sync with after-image files.
CAUSE:
Standby database out of sink with after-image files being applied to roll fowrard.
FIX:
In order to execute the roll forward operation, the standby database needs to be in sync with the after image files. If you try to apply subsequent after image files from the production database to the standby database you might get the above errors.
To avoid synchronization problems with the standby database and the after image files, you can use the parameter -norecover with the probkup utility. Using -norecover will not perform the crash recovery process and you will be able to keep the timestamp of the standby database.
Syntax for probkup with -norecover parameter is:
probkup <dbname> <devicename> -norecover