Kbase P102046: When does crash recovery occur?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Unverified
GOAL:
When does crash recovery occur?
GOAL:
What messages indicate a crash recovery
FIX:
Crash recovery occurs each time a database is opened by the (primary) database broker or accessed by a single user session, with some exceptions as
. probkup <db> <device> -no recover
. procopy <db> <db2>
. prodb <db2> <db>
The following message might be displayed in case of no crash recovery on a single user session accessing a database:
. WARNING: Before-image file of database <db> is not truncated. (1552)
Some access of the database are not only triggering the crash recovery but also the truncation of the Before Image (BI). In that case, on " rfutil <db> -C aimage begin" for example, the following message is displayed:
. The BI file is being automatically truncated. (1526)
The two following messages within the database log file (<db>.lg) indicate the first phase of crash recovery:
. Begin Physical Redo Phase at <current address>. (5326)
. Physical Redo Phase Completed at blk off upd . (7161)
If there was opened transactions at the time the database stopped, these additional messages indicate a second phase for crash recovery for the database broker or for a single user session:
. Begin Logical Undo Phase, incomplete transactions are being backed out. (7162)
. Begin Physical Undo transactions at block offset (7163)
On "rfutil <db> -C roll forward -a <AI_file>", just the redo phase of crash recovery occurs.