The RMAN log look like something:
$RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19> 20> 21> 22> 23> 24> 25> 26> 27> 28> 29> 30> 31> 32> 33> 34> 35> 36> 37> 38> 39> 40> 41> 42> $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-10041: Could not re-create polling channel context following failure. $RMAN-10024: error setting up for rpc polling $RMAN-10005: error opening cursor $RMAN-10002: ORACLE error: ORA-03114: not connected to ORACLE $RMAN-03002: failure of allocate command at 03/26/2019 15:47:15 $RMAN-06136: ORACLE error from auxiliary database: ORA-03113: end-of-file on communication channel
Look into the alert log and see if you can find something related with memory:
ORA-04031: unable to allocate 6029352 bytes of shared memory ("shared pool","unknown object","sga heap(1,0)","ksipc pct")
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_ipc0_88913.trc (incident=95082):
ORA-4031 [] [] [] [] [] [] [] [] [] [] [] []
If yes… To fix this issue -> define SGA and PGA values in your pfile that you use to open the auxilary database in nomount state. They might be missing or set to a low value:
*.sga_target=25769803776 *.pga_aggregate_target=12884901888
Other possible causes might be:
- auxiliary pfile specified an invalid undo_tablespace name that is not present in the database that is being duplicated.
- Bug 14478810
- a problem creating the tempfile(s) for the temporary tablespace(s)