Last updated on SEPTEMBER 13, 2016
Applies to:Oracle Internet Directory - Version 220.127.116.11 and later
Information in this document applies to any platform.
***Checked for relevance on 30-July-2013***
Oracle Internet Directory (OID) 11g R1 (18.104.22.168) or 11gR1 Patchset1 (22.214.171.124.0).
Due to previous failed installations/re-installations, OID was reinstalled one last time reconfigured for new ports using a new componentname called oid2, and everything had been working properly, including OID replication.
However, process entries for an old componentname oid1 is still referenced in the ods.ods_process_status table, from the previous installs/reinstalls. Also, unwanted / incorrect statuses for oid1 processes are still getting displayed from opmnctl and oidctl status commands.
In order to clean up / remove these references of leftover / invalid / unwanted oid1 component process entries, everything has been shutdown with opmnctl stopall, and all processes have been verified to be down with ps -ef | grep oid and ps -ef | grep odi. Next, needs to attempted to run just oidmon and oidctl by themselves to cleanly remove the unwanted refences, as per <Document 889673.1>.
Startup of oidmon fails with:
exec(): 0509-036 Cannot load program oidmon because of the following errors:
rtld: 0712-001 Symbol nzcsf_oid_read was referenced from module oidmon(), but a runtime definition of the symbol was not found.
rtld: 0712-001 Symbol nzcsfCLS_CloseLdapStore was referenced from module oidmon(), but a runtime definition of the symbol was not found.
This being a 64 bit platform, the following was also tried, but the same error continued:
- Removing /lib from the $LD_LIBRARY_PATH environment variable.
- unset the $LD_LIBRARY_PATH variable.
After changing /lib to /lib32 on the $LD_LIBRARY_PATH, the error then changed to:
0509-022 Cannot load module <path/lib>
0509-150 Dependent module <path/lib> could not be loaded.
0509-103 The module has an invalid magic number.
Continued trying different settings for the lib path variable, but oidmon start either returned the same above error or hung.
After applying the Solution #1 (see below), a subsequent oidctl stop command (to remove the invalid references to componentname oid1 on the table) succeeded, but the table still showed the invalid/unwanted row(s).
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms