This content has been marked as final. Show 2 replies
A log sequence error is generated by the recovery code when a log record references a database
page but the Log Sequence Number on the page is less than the LSN that is recorded in the log record.
In your case the LSN in the log record: previous LSN 69 2363102
is greater than the LSN of the actual record: page LSN 69 2353362
This situation indicates that the database is inconsistent with the information in the log.
You can try using db_dump/db_load to restore the database. You could try using
db_load with -r lsn flag to reset the LSNs in the file.
Are you using DB_PRIVATE? If so is there any way you could have more than one process
accessing the same database and log files?
thanks for your reply. Indeed, dumping and loading solved the problem. Good to know. Although I would rather prefer that recovery would be able to handle such situations :)
Concerning your questions: when such a failure happened, I didn't use the PRIVATE environment. Then, however, I tried to recover it with DB_PRIVATE and no other processes were accessing the environment or database files. Just doing db_load -r lsn db.file didn't solve my issue.