I think it resyncs the catalog each time you connect.
More specifically each time you
connect target / catalog a/b@c
can you do your browsing by just
connect target /
you could test the theory by
rman ... debug trace = /tmp/rman.trc log=/tmp/rman.log
and look for any evidence of resync.
On Mon, Aug 3, 2020 at 8:22 PM Charlotte Hammond <
What causes an implicit resync of the RMAN catalog? I had thought it was
significant events like running backups or deleting backup pieces. However
I've been using RMAN today, connected to the catalog, just browsing but I
can see that the catalog has periodically updated over the course of the
This shouldn't be a problem of course, but we have a legacy utility that
runs a duplicate from backups without specifying the SCN. In this case the
SCN seems to be plucked from the highest SCN in the AL table. This is
fine if the AL table isn't updated outside of backups but otherwise it ends
up with SCNs from more recent archive logs which aren't in the backup and
so the duplicate fails.
Any workarounds without hacking at the fragile old duplicate utility to
force it to use a specific SCN or time?
Thank you in advance for any advice! (Oracle 11.2)