If the RMAN restore hangs with the “starting implicit crosscheck backup” error and has not been completed for a long time, you may have problems with setting the db_recovery_file_dest parameter.
If RMAN started to wait as follows , the process to be performed is to reset the value of the db_recovery_file_dest parameter.
|
1 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 43 44 45 |
using target database control file instead of recovery catalog allocated channel: a1 channel a1: SID=5420 instance=ORCL device type=DISK allocated channel: a2 channel a2: SID=4217 instance=ORCL device type=DISK allocated channel: a3 channel a3: SID=4389 instance=ORCL device type=DISK allocated channel: a4 channel a4: SID=4561 instance=ORCL device type=DISK allocated channel: a5 channel a5: SID=4733 instance=ORCL device type=DISK allocated channel: a6 channel a6: SID=4905 instance=ORCL device type=DISK executing command: SET NEWNAME executing command: SET NEWNAME executing command: SET NEWNAME executing command: SET NEWNAME executing command: SET NEWNAME executing command: SET NEWNAME executing command: SET NEWNAME executing command: SET NEWNAME executing command: SET NEWNAME executing command: SET NEWNAME executing command: SET NEWNAME executing command: SET NEWNAME Starting restore at 09-MAY-17 Starting implicit crosscheck backup at 09-MAY-17 |
change the value of the db_recovery_file_dest parameter as follows. Then RMAN will continue to work without error.
|
1 2 3 |
SQL> alter system set db_recovery_file_dest='' scope=both sid='*'; System altered. |
