Directory server fails to start after running bulkload
When you run ldap operations after you run bulkload, the directory server fails to start or shows an error. Follow the steps to troubleshoot and resolve this issue.
After performing bulkload, if the directory
server fails to start or displays error when performing LDAP operations,
it could be because of one of the following reasons:
- Check the log file, db2diag.log, if there
is an error that states
ACCESS TABLE WHEN IN RESTRICTED STATE. This means that loading data or bulkload was not complete or was unsuccessful. - The table is in the “Load Pending” or “Locked” state. A previous LOAD attempt on the table might have resulted in failure. Accessing the table is not allowed until the LOAD operation is restarted or terminated.
Consider the following options to rectify the problem:
- Stop or restart the failed LOAD operation on the table by issuing LOAD with the TERMINATE or RESTART option.
- Check if the bulkload_status file is present. This file is created in the home directory of the instance. If this file is present, it means that bulkload was unsuccessful. Check the file for errors and rectify it, and try running the bulk load utility again.