All OID Servers Unavailable If One RAC Node Is Down when using SCAN addressing
Last updated on AUGUST 23, 2017
Applies to:Oracle Internet Directory - Version 188.8.131.52.3 and later
Information in this document applies to any platform.
OID server becomes unresponsive if one node in RAC is down.
Multiple OID 184.108.40.206.0 servers installed non-clustered behind load balancer. Servers connected to two-node 220.127.116.11 RAC with SCAN configured.
QA testers shut down one node of the RAC to test HA failover. Both OID servers became non-responsive until the node was restored.
oidmon.log file sample error message:
[2015-06-22T15:09:39-04:00] [OID] [NOTIFICATION:16]  [OIDMON] [host: daloidap01xu.vtitel.net] [pid: 29540] [tid: 0] Guardian: gsl
dudiSetSqlStmt: Sql prepare failed (SELECT attrname, attrval from ds_attrstore where entryid=899 )
ORA error = 3114 message = ORA-03114: not connected to ORACLE
We followed DocId 1494043.1 and DocId 975457.1 to modify the tnsnames.ora file with the three separate IP addresses of the SCAN name but the result was still not working. Need advice on correctly configuring HA because the documentation has conflicting information.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms