RMAN Duplicate Database does not restore tape backups in parallel
(Doc ID 419987.1)
Last updated on FEBRUARY 28, 2019
Applies to:Oracle Database - Enterprise Edition - Version 10.1.0.2 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
When peforming duplicate with multiple channels where not all pieces
are accessible from all channels duplicate might fail with piece not
found when rman schedules a piece to a channel which cannot restore it.
Here are some examples.
1) If specifying multiple channels with SBT_LIBRARY=oracle.disksbt
and these errors occur during restore, then it's likely related to
ORA-19870: error reading backup piece 05i6l96h_1_1
ORA-19507: failed to retrieve sequential file, handle="<backuppiee name>", parms=""
ORA-27029: skgfrtrv: sbtrestore returned error
ORA-19511: Error received from media manager layer, error text:
sbtpvt_open_input: file /tmp/backup_dir1/<backuppiee name> does not exist or cannot
be accessed, errno = 2
2) If specifying multiple channels from an SBT Media device and RMAN
appears to be hung during restore then enable KRB_TRACE like so:
configure channel...device type sbt... debug 6 trace 6;
Repeat restore and monitor for channel trace dumps. For each channel
trace dump grep for sbt. If no "sbtinfo" is present between "sbtinit"
and "sbtrestore" then the hanging is likely due to this bug.
It may also be possible that an error arising from backup piece not
found is thrown rather then a hung symptom. The actual symptom may
depend on how a given SBT Media Manager handles this issue.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document