If we are sure that transaction logs are persisted by making the bdb flags DB_TXN_SYNC, then there will not be problem if hardware fails and restarts right?
**************************************************************************** ****************************
This e-mail and attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient's) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!
-----Original Message----- From: Howard Chu [mailto:hyc@symas.com] Sent: Wednesday, June 20, 2007 11:09 PM To: John Drescher Cc: arunachalamp@huawei.com; openldap-software@openldap.org Subject: Re: Recovery after system shutdown
John Drescher wrote:
Hello,
When I started adding some entries to openldap server (2.3.36), suddenly
my
system powered off,
When I started my sytem after rebooting, my slapd with BDB as backend ,
is
unable to recover , I am getting an error as below, Please say , what am
I
doing wrong
I am not sure if this is your problem but have you tried running the
bdb utilities to recover from a corrupted database. I believe the
command is db_recover. We have had to do this a few times in the past.
It's clear from his error log that such actions will be useless. His
transaction log is clearly missing a large amount of data. The BDB transaction
support can't help you if your hardware fails to preserve the transaction log data.