Rman Targetless Duplicate Fails To Call Sbt_end
(Doc ID 2167675.1)
Last updated on MARCH 14, 2019
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 and later
Oracle Database Cloud Schema 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
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
When running RMAN duplicate database without target, Targetless Duplication, sbtend is not called at the end of the duplicate. This causes media manager processes to remain after RMAN duplicate completes. You can find this by reviewing the sbtio.log file in the target database trace directory. Most media managers write to that file as per sbt specifications. Append to the allocate channel command "trace 5" to have more detailed information written to the sbtio.log.
No, sbt_end is reported.
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