Kbase P10239: Attempted start of database after operating system crash, registers errors 49 and 801
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
02/01/2009 |
|
Status: Verified
SYMPTOM(s):
Cannot start broker.
SYSTEM ERROR: Memory violation. (49)
Core file generated.
** The server terminated due to signal <number>. (801)
The server terminated due to signal 3. (801)
There is no backup of this database.
Proutil dbname -C truncate bi fails with same errors.
Proutil dbname -C truncate bi -F fails with the same errors.
Stack trace from _mprosrv reads:
uttdrExitOnTerm
sigaction
_getfp
_fork
System rebooted while the database was running
FACT(s) (Environment):
All Supported Operating Systems
Progress/OpenEdge Product Family
CAUSE:
The exact cause is unknown at the time of this writing
FIX:
Restore from the most recent backup, if that is not an option, do the following:
1. Perform an OS copy of all your database files
2. Remove dbname.lk file
rm <dbname.lk>
3. Run prostrct unlock
prostrct unlock <dbname>
4. Truncate the bi file
proutil <dbname> -C truncate bi
5. Start up the database.