Why is an "active" RMAN duplicate trying to access a backup file?
Trying to do an 11g database clone from Prod to Test on a Widows 2008 server. Source and destination instances are on the same server, different directories. Had this working in a very simple fashion before. Now, after the regular backups were switched from running as RMAN scripts locally on this server to using Unitrends backup appliance, the duplicate command fails with ora-19505, trying to access a backup piece on the Unitrends appliance.
My understanding from Oracle RMAN doc is that if I connect to the source database (Prod) as "target" and the destination (Test) as "auxiliary", this made it an "active" duplication and is not supposed to require access to previous backups. Up until now, it was this simple: