Identity Management (MOSC)

MOSC Banner

How to avoid the "human intervention changes queued" on repld log file.

edited May 12, 2011 7:16PM in Identity Management (MOSC) 1 commentAnswered
 Hi All,

We are using OID (version 10.1.4.2.0) only for connect string purpose. We setup three replication nodes on the same replication group. The ldap processes are running on HP-UX v11.31.

We add connect string to node1 OID through 10g Net Manager. Then node2 and node3 will be replicated through oidrepld (show below)

node2:/u01/oracle/OraHomeOID>> ps -ef|grep repl

  oracle 23196 10193  0 12:05:01 pts/0     0:00 grep repl

  oracle 11805     1  0 10:28:35 ?         0:03 /u01/oracle/OraHomeOID/bin/oidrepld  -inst 3

node2:/u01/oracle/OraHomeOID>>

-----------------------------

Recently, we found out node2 and node3 has many repeatedly “human intervention changes queued” on log file $ORACLE_HOME/ldap/log/oidrepld03.log

Node1 can send out any update without problem. Please see the following log files on three nodes:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center