Create physical standby using OEM13c
edited Jul 10, 2017 1:51PM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 2 commentsAnswered
I am trying to setup physical standby database (11.2.0.4) using OEM13c. I see failure status for steps:
1. Switch to use Duplicate (Duplicate Database) -
| RMAN-00571: =========================================================== |
| RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== |
| RMAN-00571: =========================================================== |
| RMAN-03002: failure of Duplicate Db command at 06/30/2017 12:47:36 |
| RMAN-05501: aborting duplication of target database |
| RMAN-03015: error occurred in stored script Memory Script |
| RMAN-03009: failure of sql command on dup1 channel at 06/30/2017 12:47:36 |
| RMAN-10038: database session for channel dup1 terminated unexpectedly |
2. Post Cloning (Create standby database) -
| ERROR at line 1: |
| ORA-01503: CREATE CONTROLFILE failed |
| ORA-01565: error in identifying file |
| '+DATA/db1/datafile/system.345.87999239' |
| ORA-17503: ksfdopn:2 Failed to open file |
| +DATA/db1/datafile/system. |
0