High Availability Data Guard, Sharding and Global Data Services (MOSC)

MOSC Banner

After Upgrade to 19c tnsnames in DGMGRL for Parameter 'DGConnectIdentifier' will ignored

edited Jan 14, 2021 6:22PM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 5 comments

Hi,

OL 7.8 with OEE, Upgrade from 12.1 to 19c

After Upgrading the 12.1. DG environment to 19c I observed following error:

When successfully connect in DGMGRL it raised error „ORA-12154: TNS:could not resolve the connect identifier" while trying to get infos from the other DB with "DGMGRL>show database ora2" or "DGMGRL>show configuration". No matter if I try that from DB-Host of ora1 getting infos of ora2 DB-Host and vice versa.

The property 'DGConnectIdentifier' is always set to a resolvable TNS Alias. I can successfully TNSPing /SQLPLUS Connect to all aliases. It seems that DGMGRL ignores tnsnames.ora aliases for 'DGConnectIdentifier' property. I also try to set TNS_ADMIN but no success.

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