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

MOSC Banner

How to resolve dbf naming conflict between PRIMARY and STANDBY RDMBS 19.11.0.0

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

PRIMARY DBF: "SYSTEM"

STANDBY DBF: "system"

Difference in capitalization of the dbf file causes:

RMAN-03002: failure of recover command at 05/18/2022 19:31:59

ORA-19625: error identifying file 

+DATA_DG/NPTC/DATAFILE/system.17562.1100457481

ORA-17503: ksfdopn:2 Failed to open file +DATA_DG/NPTC/DATAFILE/system.17562.1100457481

ORA-15012: ASM file '+DATA_DG/NPTC/DATAFILE/system.17562.1100457481' does not exist

Renaming the STANDBY "system" file to the PRIMARY "SYSTEM" resulted in error:

ERROR at line 1:

ORA-01511: error in renaming log/data files

ORA-01523: cannot rename data file to '+DATA_DG/NPTC/DATAFILE/SYSTEM.17562.1100457481' - file already part of database

How to resolve dbf name conflict for DG Recovery

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