My Oracle Support Banner

DS 5.2P6 - Instance will not start with a bad transaction (txn) log file - Error Reports: magic number 0, not NNN (Doc ID 1288085.1)

Last updated on FEBRUARY 28, 2020

Applies to:

Oracle Directory Server Enterprise Edition - Version 5.1 and later
Information in this document applies to any platform.
***Checked for relevance on 19-Sep-2012***

Symptoms

Customer had the Backup Restore Team restore the LDAP instance DB directory from earlier date.
After RESTORE of db file system the server instance fails to initialize.

Errors:
[26/Jan/2011:06:45:01 -0600] - Sun Java(TM) System Directory Server/5.2_Patch_6 B2007.221.1746 (64-bit) starting up
[26/Jan/2011:06:45:02 -0600] - WARNING<20488> - Backend Database - conn=-1 op=-1 msgId=-1 - Detected Disorderly Shutdown last time Directory Server was running, recovering database.
[26/Jan/2011:06:45:02 -0600] - DEBUG - conn=-1 op=-1 msgId=-1 - libdb: region error detected; run recovery.
[26/Jan/2011:06:45:03 -0600] - DEBUG - conn=-1 op=-1 msgId=-1 - libdb: Ignoring log file: $PATH_TO/slapd-instance/db/log.NNNNNN: magic number 0, not NNN
[26/Jan/2011:06:45:03 -0600] - DEBUG - conn=-1 op=-1 msgId=-1 - libdb: PANIC: Invalid argument
[26/Jan/2011:06:45:03 -0600] - ERROR<20490> - Backend Database - conn=-1 op=-1 msgId=-1 - Database Recovery Process FAILED. The database is not recoverable.
[26/Jan/2011:06:45:03 -0600] - ERROR<20749> - Backend Database - conn=-1 op=-1 msgId=-1 - start: Failed to init database, err=-30989 DB_RUNRECOVERY: Fatal error, run database recovery

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.