I created an RMAN script to copy an Oracle 11.2.0.1 target database called BUSPROD into an auxiliary database called BUSSOUT2. I left it running overnight but when I looked at the log the following day, I noticed it had failed with RMAN-04022:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03004: fatal error during execution of command
RMAN-04022: target database mount id 1608114561 does not match channel's mount id 1608162051
ORA-03114: not connected to ORACLE
RMAN-03002: failure of Duplicate Db command at 03/25/2019 20:00:45
RMAN-03015: error occurred in stored script Memory Script
ORA-03114: not connected to ORACLE
ORA-01109: database not open
Apparently this happens if the target database is closed during the recovery operation. I checked and saw that it had been bounced shortly before the failure took place:
SQL> conn system@busprod
Enter password:
Connected.
SQL> select to_char(startup_time,'dd-mon-yy hh24:mi:ss')
2 from v$instance
3 /
TO_CHAR(STARTUP_TI
------------------
25-mar-19 19:35:29
SQL>
Shared on LinkedIn on 26th March 2019.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03004: fatal error during execution of command
RMAN-04022: target database mount id 1608114561 does not match channel's mount id 1608162051
ORA-03114: not connected to ORACLE
RMAN-03002: failure of Duplicate Db command at 03/25/2019 20:00:45
RMAN-03015: error occurred in stored script Memory Script
ORA-03114: not connected to ORACLE
ORA-01109: database not open
Apparently this happens if the target database is closed during the recovery operation. I checked and saw that it had been bounced shortly before the failure took place:
SQL> conn system@busprod
Enter password:
Connected.
SQL> select to_char(startup_time,'dd-mon-yy hh24:mi:ss')
2 from v$instance
3 /
TO_CHAR(STARTUP_TI
------------------
25-mar-19 19:35:29
SQL>
Shared on LinkedIn on 26th March 2019.