Kbase P25930: Information on message 4244
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Unverified
GOAL:
Explanation of message 4244: Crash Recovery (-i): <Enabled/Disabled>.
GOAL:
Is the message "Crash Recovery (-i): Not Enabled. (4244)" worrying?
FIX:
The informational message
Crash Recovery (-i): <Enabled/Disabled> (4244).
indicates if you are or are not using the startup parameter "-i".
By default (without "-i") crash recovery is enabled and you have in the database log file a line:
<Time> BROKER 0: Crash Recovery (-i): Enabled. (4244)
When having started a database "sports" with, for example
proserve sports -i
you have in the database log file a line:
<Time> BROKER 0: Crash Recovery (-i): Not Enabled. (4244)
Additionally you have the following message on the screen as well as within the database log file (sports.lg in this sample):
** This session is being run with the no-integrity (-i) option. (512)
The message "Crash Recovery (-i): Not Enabled. (4244)" should make you fully aware that you will certainly need to restore an earlier database backup in case of abnormal database shutdown or abnormal client session end. There is not enough information written within the Before Image log (BI) for undoing the abnormally ended transactions.
For data integrity protection of the database, it is not possible to issue an unconditional shutdown of a database (using proshut -F) when it has been started with no integrity (-i).
The message "Crash Recovery (-i): Not Enabled. (4244)" should make you worry about the time needed for restoring your database backup.