All problems described in this technical note need basic information collected about when the problem occurred and about the system having the problem. Use this task to collect that basic information.
Note the time or times the problem occurred.
If possible, collect explorer output from SUNWexplo software on the system where the problem occurred.
Provide graphical representation of your deployment.
The graphical representation of your deployment is key to understanding the context of the problem. Show the following in the graphical representation.
All computers involved, with their IP addresses, hostnames, roles in the deployment, operating systems, and versions used.
All other relevant systems, including load balancers, firewalls, and so forth.
If possible, collect a copy of the database on spare disk space or backup media to be used later if necessary.
Database files and the transaction log are often indispensable for diagnosing deadlocks involving database locks.
Note the operating system version.
C:\Program Files\Common files\Microsoft Shared\MSInfo\msinfo32.exe /report C:\report.txt
Note the patch level.
Already provided in C:\report.txt.
Collect Directory Server version information.
server-root/bin/slapd/server/ns-slapd -D instance-dir -V
The server executable is slapd.exe on Windows systems.
Collect the Directory Server configuration file, server-root/slapd-serverID/config/dse.ldif.
Collect Directory Server access, errors, and audit logs.
By default, you find these logs in the following locations:
server-root/slapd-serverID/logs/audit (if enabled)
If these log files are not in the default locations, examine the Directory Server configuration file, server-root/slapd-/serverID/config/dse.ldif, to find the paths to the logs. The paths are specified as the values of attributes nsslapd-accesslog, nsslapd-errorlog, and nsslapd-auditlog.