Oidldapd start problem

Question

$ ldapbind -p 13060 -h dcxnim01
Cannot connect to the LDAP server
$ oidctl connect=ldapdcx1 server=oidldapd instance=1 configset=1 start
NLS_LANG not set in environment
Setting NLS_LANG to AMERICAN_AMERICA.AL32UTF8
oidctl:Waiting for oidmon to start OIDLDAPD (instance=1)
oidctl:Waiting for oidmon to start OIDLDAPD (instance=1)
oidctl:Waiting for oidmon to start OIDLDAPD (instance=1)
oidctl:Waiting for oidmon to start OIDLDAPD (instance=1)
oidctl:Started OIDLDAPD (instance=1) with PID : 975066 successfully
$ ps -ef | grep oidldapd
oracle 975068 819208 0 16:37:40 pts/0 0:00 grep oidldapd
$ ps -ef | grep 975066
oracle 975072 819208 0 16:37:48 pts/0 0:00 grep 975066
Getting error messages when run netca( to make ldap.ora) or netmgr(for sid entry adding) for entry management.

Answer 1

I find out this.
NOTE: It is important to not mix and match opmnctl and oidmon/oidctl commands. Either start/stop OID using opmnctl OR using oidmon/oidctl. But don't start OID with opmnctl then try to stop it using oidmon/oidctl, or vice versa.
Try to start OID using opmnctl
1. Check the OID status:
opmnctl status
Presumably it will show as Down
2. If it is Down, try to start OID:
opmnctl startproc ias-component=OID
3. Recheck the status. Is it running now?
4. If so, check whether you are able to connect to OID:
ldapbind -h <OID_host> -p <OID_port>
If Steps 1-4 are successful, then OID is up on that host and port, so skip the steps below -- you are done.
Otherwise, issue this command, then continue with the following steps...
opmnctl stopproc ias-component=OID
Clean OID and try starting it using oidmon/oidctl, collecting the logs if OID still doesn't start
5. Check OID $ORACLE_HOME/install/portlist.ini for OID ports. You'll see the non-SSL port, followed by the SSL port.
6. At a command prompt, enter the following to see whether the OID ports are in use:
netstat -a | grep <OID port>
If there is something there, it will need to be stopped before you can use that port for OID
7. UNIX Platforms Only: Confirm the permissions on the following binaries in the OID $ORACLE_HOME/bin directory, which minimally should be set as:
oidldapd
4710 (rws--x---) with owner root and group dba
oidmon, oidrepld
4710 (rws--x---) with owner oracle and group dba
Note the setuid bit must be set on oidldapd, oidmon and oidrepld.
8. Ensure that the OID processes are down:
1. On Windows, check for oidservice.exe and (at least) 2 oidldapd.exe processes in Task Manager > Processes. If they are there, then at least part of OID is running
2. On Unix issue the following command:
ps -ef | grep oid
This should return the oidmon process and (at least) 2 oidldapd processes when all is working.
For now, ensure that nothing is returned. If something is returned, then you will need to shut it down.
9. Sqlplus into the OID database from the OID Oracle Home as the user ODS, using the ias_admin password. This example uses an OID database called 'asdb'.
sqlplus ODS/<ias_admin_pwd>@asdb
Be sure to include the "@asdb" so that we test the same type of connection OPMN will be making
For tnsnames.ora search order, reference Note 114085.1 - TROUBLESHOOTING GUIDE: TNS-12154 TNS:could not resolve service name
10. Issue the following query:
select * from ods_process;
What does this return? Create a backup of the ods_process table before truncating it in the next step:
create table ods.ods_process_backup as select * from ods.ods_process;
11. If there are one or more records, truncate the table:
truncate table ods_process;
12. Remove the current logs from the OID $ORACLE_HOME/ldap/log directory
13. Start oidmon
oidmon connect=<service_name> start
<service_name> is the same database connect string you used in step 9.
14. Start the oidldapd processes with debug:
9.0.4: oidctl connect=<service_name> server=oidldapd instance=1 flags="-p <OID port> -debug 67108863" start
10.1.x: oidctl connect=<service_name> server=oidldapd instance=1 flags="-p <OID port> -debug 117440511" start
<service_name> is the same database connect string you used in step 9.
15. Check the oidmon (oidservice.exe) and oidldapd processes after a minute or so, as you did in step 8.
If the processes still aren't running, review the new log files. Skip the following steps.
Test the OID connection
16. If the OID processes are running, retry the ldapbind in step 4:
ldapbind -h <OID_host> -p <OID_port>
If that fails, review the new logs.
If that is successful, continue with the following steps.
If OID is functional, stop it and try starting it using opmnctl
17. Shut OID down:
oidmon connect=<service_name> stop
oidctl connect=<service_name> server=oidldapd instance=1 stop
18. Ensure OID is really down; repeat step 17, or kill processes as necessary:
netstat -a | grep <OID_port>
(UNIX) ps -ef | grep oid
(Windows) check Task Manager
19. Clean out the ODS_PROCESS table, as you did in steps 9-11:
sqlplus ODS/<ias_admin_pwd>@<service_name>
select * from ods_process;
truncate table ods_process;
20. Start OID using opmnctl:
opmnctl startproc ias-component=OID
21. Check ODS_PROCESS table for new entry:
sqlplus ODS/<ias_admin_pwd>@<service_name>
select * from ods_process;
If you encounter problems with the above steps, please create a TAR at Metalink and upload the following:
- results of the above steps
- OID log from the OPMN $ORACLE_HOME/opmn/log directory
- opmn.xml file from the OPMN $ORACLE_HOME/opmn/conf directory
- OID logs from the OID $ORACLE_HOME/ldap/log directory
Regards.