Finished restore at 2015-06-03 19:04:14
Starting recover at 2015-06-03 19:04:14
released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 06/03/2015 19:04:14
RMAN-06004: ORACLE error from recovery catalog database: ORA-03114: not connected to ORACLE
RMAN>
In this case, I was connecting to a catalog database in a remote location, and the run block was setting a tape channel to NBU for restoring data files from tapes.
run
{
allocate channel c1 type 'sbt_tape';
set until scn = 76543658012;
restore database;
recover database;
release channel c1;
}
It might take too long on restoring data files from tapes to maintain the connection to the catalog database. Consequently, the firewall, IDS, IPS, anti-virus or catalog database disconnected from the run block in the middle of the run block.
So we just reconnect to the catalog and run the remaining jobs started from the point interrupted. In this case, I found the restoring of data files was complete, so I do the recovering only in the run block.
run
{
allocate channel c1 type 'sbt_tape';
set until scn = 76543658012;
recover database;
release channel c1;
}