This section describes how to troubleshoot an inaccessible database
The Directory Server database may be inaccessible for one of the following reasons:
Shared region file corruption
Missing change log
Corrupted change log
Database offline, for example it is being reimported
Missing transaction log
If the server refuses to start, remove the guardian file and all shared memory files while the server is offline and then retry a new start.
# install-path/instance-name/db/guardian # install-path/instance-name/db/_db.00*
If the start succeeds and the database still cannot be loaded, continue with this procedure.
Backup up all database file stored in the db/ directory.
Collect error and access log files from the time during which the database was inaccessible.
# install-path/instance-name/logs/errors* # install-path/instance-name/access*