db_recover utility displays 'Log sequence error'
Originally Published: 2003-03-20
Article Number
Applies To
Sun Solaris 2.8
Microsoft Windows 2000
Issue
Error: "db_recover: Log sequence error: page LSN 1:2374311; previous LSN 1 2453397" appears during db_recover process
An example of a typical db_recover failure on a Windows system with log sequence errors:
C:\Program Files\RSA Security\RSA_KeonCA\Xudad\db>..\bin\db_recover -v
db_recover: Finding last valid log LSN: file: 1 offset 2489189
db_recover: Checkpoint at: [1][2487660]
db_recover: Checkpoint LSN: [1][2487660]
db_recover: Previous checkpoint: [1][2454289]
db_recover: Checkpoint at: [1][2487660]
db_recover: Checkpoint LSN: [1][2454289]
db_recover: Previous checkpoint: [1][2413038]
db_recover: Recovery starting from [1][2454289]
db_recover: Log sequence error: page LSN 1:2374311; previous LSN 1 2453397
db_recover: Log sequence error: page LSN 1:2310803; previous LSN 1 2378429
db_recover: Log sequence error: page LSN 1:2249753; previous LSN 1 2379596
db_recover: Log sequence error: page LSN 1:2249881; previous LSN 1 2386788
db_recover: Log sequence error: page LSN 1:2279633; previous LSN 1 2389098
db_recover: Log sequence error: page LSN 1:2281797; previous LSN 1 2382304
db_recover: Log sequence error: page LSN 1:2253254; previous LSN 1 2390886
db_recover: Log sequence error: page LSN 1:2369924; previous LSN 1 2449010
db_recover: Log sequence error: page LSN 1:2279115; previous LSN 1 2386416
db_recover: Log sequence error: page LSN 1:2279487; previous LSN 1 2379966
db_recover: Log sequence error: page LSN 1:2279633; previous LSN 1 2456908
db_recover: Log sequence error: page LSN 1:2279633; previous LSN 1 2463454
db_recover: Log sequence error: page LSN 1:2282665; previous LSN 1 2390142
db_recover: Log sequence error: page LSN 1:2283613; previous LSN 1 2382452
db_recover: Log sequence error: page LSN 1:2369924; previous LSN 1 2459401
db_recover: Log sequence error: page LSN 1:2369984; previous LSN 1 2449070
db_recover: Log sequence error: page LSN 1:2369984; previous LSN 1 2471600
db_recover: Log sequence error: page LSN 1:2373735; previous LSN 1 2452821
db_recover: Log sequence error: page LSN 1:2369984; previous LSN 1 2475351
db_recover: Log sequence error: page LSN 1:2369984; previous LSN 1 2475506
db_recover: Log sequence error: page LSN 1:2373735; previous LSN 1 2475429
db_recover: Log sequence error: page LSN 1:2369924; previous LSN 1 2475506
db_recover: Log sequence error: page LSN 1:2369924; previous LSN 1 2482792
db_recover: Log sequence error: page LSN 1:2374311; previous LSN 1 2455010
db_recover: c:\program files\rsa security\rsa_keonca\Xudad\db\cert_status.dbh: close: 1 blocks left pinned
db_recover: c:\program files\rsa security\rsa_keonca\Xudad\db\objectclass.dbh: close: 4 blocks left pinned
db_recover: c:\program files\rsa security\rsa_keonca\Xudad\db\id2entry.dbh: close: 14 blocks left pinned
db_recover: c:\program files\rsa security\rsa_keonca\Xudad\db\dn2id.dbh: close:2 blocks left pinned
db_recover: c:\program files\rsa security\rsa_keonca\Xudad\db\id2children.dbh: close: 2 blocks left pinned
db_recover: c:\program files\rsa security\rsa_keonca\Xudad\db\dn.dbh: close: 2 blocks left pinned
db_recover: DBENV->open: DB_INCOMPLETE: Cache flush was unable to complete
C:\Program Files\RSA Security\RSA_KeonCA\Xudad\db>
Resolution
Parameter explanations for db_recover:
-c perform catastrophic recovery
-v run in verbose mode
?Archived files? means any backed up files. Any time you recover from a backed up database, it is called a ?catastrophic? recovery in BerkeleyDB terminology. The terminology is perhaps unfortunate, however it does not imply integrity issues with the state of the archived data.
With BerkeleyDB, a ?normal? recovery (using db_recover without any parameters) is one performed on the current database files, not from backed up files. If the process using BerkeleyDB does not shutdown cleanly for some reason (e.g. core dump, power failure, etc.), the transaction log files can be left in an inconsistent state, which can cause problems. A ?normal? recovery is used to fix up the log files before proceeding.
NOTE: Every time Keon Certificate Authority (i.e., Xudad) starts up, it performs a normal recovery (in case the previous shutdown was not clean)
?Catastrophic? recovery is simply normal procedure for restoration from any backup. The terminology sounds alarming, but is BerkeleyDB?s terminology and we are using their tools for recovery. Unless errors are encountered when doing a ?db_recover ?c? recovery, there is no concern for data loss during a recovery of archived files.
* The following paragraph provides information on the catastrophic recovery process as supplied by Sleepycat Software (Makers of Berkeley DB). More information is available at URL: http://www.sleepycat.com/docs/ref/transapp/recovery.html.
"The catastrophic recovery process will review the logs and database files to bring the environment databases to a consistent state as of the time of the last uncorrupted log file that is found. It is important to realize that only transactions committed before that date will appear in the databases."
Here is an example of a db_recover utility running on a Windows system using the -c and -v parameters:
C:\Program Files\RSA Security\RSA_KeonCA\Xudad\db>..\bin\db_recover -c -v
db_recover: Finding last valid log LSN: file: 1 offset 2490766
db_recover: Recovery starting from [0][0]
db_recover: Recovery complete at Thu Mar 20 15:31:00 2003
db_recover: Maximum transaction ID 8000060f Recovery checkpoint [1][2490814]
db_recover: Recovery complete at Thu Mar 20 15:31:00 2003
db_recover: Maximum transaction id 80000000 Recovery checkpoint [1][2490814]
C:\Program Files\RSA Security\RSA_KeonCA\Xudad\db>
Related Articles
How to properly utilize Citrix NetScaler load balancer to work with the RSA Authentication Manager 8.1 SP1 Web Tier Number of Views Unsuccessful Registration of the RSA Authenticator app for iOS or Android with a registration code from the Cloud Administ… Number of Views Web Tier Shows "Online, Reinstall Required" After Reinstalling RSA Authentication Manager 8.x Web-Tier Package Number of Views Upgrading RSA Authentication Manager Number of Views AFX Server stuck in 'Not running' State, with error 'timed out waiting for AFX applications to start' Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager 8.9 Setup and Configuration Guide RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings.
Don't see what you're looking for?
