What could have caused this problem?

You configured an OracleAS Identity Management cluster environment for your Oracle Application
Server users that has two nodes. Because of a hardware failure, the first node, NODE1, failed and
the second node, NODE2, is currently being used. After realizing this, you fixed the problem and
restarted the first node.
But then, you realized that the OIDMON process of the second node, NODE2, failed to start OID
processes on the first node automatically. What could have caused this problem?

You configured an OracleAS Identity Management cluster environment for your Oracle Application
Server users that has two nodes. Because of a hardware failure, the first node, NODE1, failed and
the second node, NODE2, is currently being used. After realizing this, you fixed the problem and
restarted the first node.
But then, you realized that the OIDMON process of the second node, NODE2, failed to start OID
processes on the first node automatically. What could have caused this problem?

A.
an inconsistent state of the OracleAS Directory Server

B.
a time discrepancy of more than 250 seconds between the two nodes

C.
failure of the Oracle Directory Integration and Provisioning (ODISRV)

D.
the Directory Replication Server (OIDREPLD) server in the first node not running



Leave a Reply 0

Your email address will not be published. Required fields are marked *