Skip Navigation Links | |
Exit Print View | |
Oracle Directory Server Enterprise Edition Troubleshooting Guide 11g Release 1 (11.1.1.5.0) |
1. Overview of Troubleshooting Directory Server Enterprise Edition
2. Troubleshooting Installation and Migration Problems
3. Troubleshooting Replication
4. Troubleshooting Directory Proxy Server
5. Troubleshooting Directory Server Problems
6. Troubleshooting Data Management Problems
7. Troubleshooting Identity Synchronization for Windows
General Troubleshooting Guidelines
Configuring and Using the Logs
Using the idsync printstat Command
Troubleshooting Quick Checklist
Troubleshooting Problems with Identity Synchronization for Windows Installation
Troubleshooting Memory Problems
Troubleshooting Problems With Connectors
General Connector Troubleshooting Tips
Determining the ID of a Connector Managing a Directory Source
Getting and Managing the Current State of a Connector
Troubleshooting a Connector in the UNINSTALLED State
Troubleshooting a Connector in the INSTALLED State
Troubleshooting a Connector in the READY State
Troubleshooting a Connector in the SYNCING State
Troubleshooting Problems With the Active Directory Connector
Troubleshooting the Watchdog Process and Core Components
Troubleshooting Processes on Solaris or Linux
Troubleshooting Processes on Windows
Examining the WatchList.properties File
To View Hidden Folders and the Temp Subdirectory on Windows
Troubleshooting the Connector Subcomponents
Verifying Subcomponent Installation
To Turn on the Windows NT Audit Log
Troubleshooting the Message Queue Component
Using telnet to Verify That the Message Queue Broker is Running
Collecting Additional Information About the Message Queue Broker
Troubleshooting Communication Problems With Directory Server
Troubleshooting Memory Problems
To Recover From a Message Queue Broker Low Memory Condition
Troubleshooting Problems With Identity Synchronization for Windows Over SSL
Troubleshooting Problems With SSL Between Core Components
Troubleshooting Problems With SSL Between Connectors and Directory Server or Active Directory
Troubleshooting Problems With SSL Between the Directory Server and Active Directory
Troubleshooting Problems With Certificates
Troubleshooting Active Directory Domain Controller Problems
8. Troubleshooting DSCC Problems
9. Directory Server Error Log Message Reference
This section guides you through the steps you should take to troubleshoot problems with the connector subcomponents. Before you begin, confirm the following:
Are the subcomponents running?
Is the Directory Server where the plug-in was installed running? Is the primary domain controller where the change detector and password filter were installed running?
Verify that all of the subcomponents are installed. Subcomponent installation must be done after the connector is installed. The subcomponents installed depend upon the connectors used as follows:
For Active Directory Connectors, no subcomponents are installed.
For Directory Server Connectors, the Directory Server plug-in must be enabled on the Directory Server being synchronized.
For Windows NT Connectors, the Windows change detector and password filter subcomponents must be installed on the primary domain controller for each Windows NT domain being synchronized. These subcomponents are installed after the Windows NT Connector is installed.
For the Windows NT SAM Change Detector subcomponent to be effective, you must turn on the Windows NT audit log. To turn on the audit log, use the following procedure and then select Policies -> Audit Policies. Select Audit These Events and then both the Success and Failure boxes for User and Group Management.
After you have installed the subcomponents, ensure that the correct post-installation steps have been taken. For example, after the Directory Server plug-in has been installed, the server must be restarted. After the Windows NT change detector and password filter have been installed on the primary domain controller, the server must be restarted.
If your subcomponents are still causing problems, confirm that they have established a network connection with the connector. On the machine where the connector is running, verify that the connector is listening for the subcomponent’s connection by running the following command:
# netstat -n -a
For example, the netstat command shows that the connector is listening for incoming connections on port 9999 and the subcomponent has successfully connected as follows:
# netstat -n -a | grep 9999 *.9999 *.* 0 0 65536 0 LISTEN 12.13.1.2.44397 12.13.1.2.9999 73620 0 73620 0 ESTABLISHED 12.13.1.2.9999 12.13.1.2.44397 73620 0 73620 0 ESTABLISHED
However, if the subcomponent has not connected, the netstat command instead shows the following:
# netstat -n -a | grep 9999 *.9999 *.* 0 0 65536 0 LISTEN
After verifying that the subcomponent is running, examine the subcomponent’s local logs for potential problems.
Verify that the correct port number was specified. Verify that the connector is running and is in the READY state. Examine the connector’s local logs for potential problems.
If the connector is not listening for incoming connections, then the output of the netstat command appears as follows:
# netstat -n -a | grep 9999 #