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

MOSC Banner

Why am I unable to set my oracle_sid to the instance name when creating standby db?

edited Aug 11, 2020 5:29PM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 9 commentsAnswered ✓

Curious question.  When creating a DataGuard physical standby, I would like to set my ORACLE_SID=stndby1 for the auxliary database.  However, doing this always results in RMAN producing the ORA-12514 error.  However, I have 0 problems when I set ORACLE_SID to stndby.  RMAN is able to connect without issue.  My listener.ora has the service name but not the instance name, as that causes an ORA-12523 error.  I have seen other examples of users using "export ORACLE_SID=stndby1" and duplicating their databases without issues.  Thoughts?

Tagged:

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