Kbase P88309: Cannot start database via dbman due to no integrity errors - conmgr.properties
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/17/2005 |
|
Status: Unverified
SYMPTOM(s):
Cannot start the database via proserve, dbman or Progress Explorer.
Receive no-integrity errors when attempting to start the database.
** This session is being run with the no-integrity (-i) option. (512)
** The last session was run with the no integrity (-i) parameter. (509)
** Your database cannot be repaired. You must restore a backup copy. (510)
Previous database session was successfully shutdown using dbman -stop command
The database log file indicates the database experienced an automated Emergency Shutdown message. An Emergency Shutdown occurs when a normal shutdown fails to complete within a certain amount of time.
Parameter files do not indicate use of the -i startup parameter.
CHANGE:
Database shutdown was issued using dbman -stop. Automated Emergency Shutdown occurred.
CAUSE:
The database was started via dbman command which reads the conmgr.properties file. In the conmgr.properties file, crashprotection was set to false. This parameter is consistent with the -i startup parameter. Therefore the database was running without integrity.
The database had also experienced an Emergency Shutdown. The Emergency Shutdown marks the database master block to indicate the database as crashed. When the database is started, the database manager will attempt to go through crash recovery and reset the flag in the master block. Because the database was running with the -i or crashprotection set to false, the database manager has insufficient notes in the BI file to perform crash recovery.
FIX:
Restore a backup of the database.