OUD 11G / 12c: Database Net Services TNS Lookups Fail in OUD Replication Topology With Error TNS-03505: Failed to resolve name
(Doc ID 2287971.1)
Last updated on FEBRUARY 22, 2023
Applies to:
Oracle Net Services - Version 12.1.0.1 and laterOracle Unified Directory - Version 11.1.2.3.161018 and later
Information in this document applies to any platform.
Symptoms
This issue affects OUD 11.1.2.3.161018 or any later version of OUD.
Steps:
===========
1. Create oud1 instance and add some data which is going to be used for tnsnames resolution.
2. Create oud2 instance and add same data that of oud1, which is going to be used for tnsnames resolution
3. Enable Replication between oud1 and oud2 directory servers. Then initialize the replication between oud1 and oud2.
4. After which when tnsnames via OUD is tested from Oracle DB client machine or DB Server machine , tnsnames resolution fails against second oud2 node. But works fine against oud1.
$ ./tnsping TEST-A
TNS Ping Utility for Linux: Version 12.1.0.1.0 - Production on 18-JUL-2017
08:40:40
Copyright (c) 1997, 2013, Oracle. All rights reserved.
Used parameter files:
DB_ORACLE_HOME/network/admin/sqlnet.ora
TNS-03505: Failed to resolve name
5. If a third OUD node oud3 is added to above replication topology, then same error is thrown against OUD per step-4 above.
6. So in Generic found that whenever any new OUD node is added to replication topology, the tnsnames resolution fails.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |