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

MOSC Banner

Physical Standby Database stopped apply after TSPITR on Primary

edited Dec 4, 2012 8:54PM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 7 commentsAnswered
Hello,

 

a few days ago I did a RMAN tablespace point-in-time recovery on our Primary Database. The Physical Standby Database stopped the apply process with the following alerts: 

Recovery deleting file #140:'+MYDB1DATA/mydb1b/datafile/mydata.343.779560911' from controlfile.

Recovery dropped tablespace 'MYDATA'

Errors in file /u01/app/oracle/diag/rdbms/mydb1b/MYDB1B1/trace/MYDB1B1_dbw0_9177.trc:

ORA-01157: cannot identify/lock data file 98 - see DBWR trace file

ORA-01110: data file 98: '+MYDB1DATA/mydb1a/datafile/mydata.467.750770973'

ORA-17503: ksfdopn:2 Failed to open file +MYDB1DATA/mydb1a/datafile/mydata.467.750770973

ORA-15012: ASM file '+MYDB1DATA/mydb1a/datafile/mydata.467.750770973' does not exist

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