Recover Table Failed On Standby Database failed with RMAN-05010: target database must be opened in READ WRITE
(Doc ID 2552354.1)
Last updated on DECEMBER 25, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.1 to 12.2.0.1 [Release 12.1 to 12.2]Information in this document applies to any platform.
Recover Table Failed On Standby Database failed with RMAN-05010: target database must be opened in READ WRITE
Symptoms
RMAN> RUN {
2> ALLOCATE CHANNEL CH1 device type disk;
3> ALLOCATE CHANNEL CH2 device type disk;
4> ALLOCATE CHANNEL CH3 device type disk;
5> ALLOCATE CHANNEL CH4 device type disk;
6> RECOVER TABLE SCOTT.DEPT
7> UNTIL TIME "TO_DATE('05/01/2018 10:00:00','mm/dd/yyyy hh24:mi:ss')"
8> AUXILIARY DESTINATION '<diskgroup name>'
9> DATAPUMP DESTINATION '/export/'
10> DUMP FILE 'abcd.dmp'
11> NOTABLEIMPORT;
12> RELEASE CHANNEL t1;
13> RELEASE CHANNEL t2;
14> RELEASE CHANNEL t3;
15> RELEASE CHANNEL t4;
16> }
......
sent command to channel: t1
sent command to channel: t2
sent command to channel: t3
sent command to channel: t4
Starting recover at 31-MAY-19
released channel: t1
released channel: t2
released channel: t3
released channel: t4
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 05/31/2019 11:01:28
RMAN-05010: target database must be opened in READ WRITE mode for Tablespace Point-in-Time Recovery
RMAN> **end-of-file**
Changes
No Changes
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 |
| Changes |
| Cause |
| Solution |
| Limitations of Recovering Tables and Table Partitions from RMAN Backups |