I'm after opinions and others practice.
At my new site we use RMAN with a catalog, at least some databases do and some didn't. I'm trying to ensure that what and how we backup is policy driven and consistent, primarily so that the recovery and cloning processes are consistent and predictable.
I therefore configured one of our new systems to use RMAN and register its backups with the catalog. Since this system is temporarily extremely short of disk space (and we don't have a media manager) I schedule a deletion of the old backup immediately before I take the new one, which in turn is scheduled just before the tape backup of the server - not great but there you go. Now as RMAN won't know that my nasty little cron has come along and deleted the backup from disk I run a crosscheck backup; delete expired after the new backup has been taken to resync the catalog.
It was suggested to me that best practice was to resync regularly (like every 15 minutes). I've read the docs and they sort of back me up (sorry for the pun!) in that they say that a manual resync is rarely required, but then rather drop themselves in it by suggesting that if you backup 'infrequently' where frequency is defined in terms of log switches not time then because the controlfile doesn't know about archivelogs generated since the last backup you should resync manually between backups. It seems to me that if there is any truth in this last then you should resync after every log switch, but my question is what do others do, and if you have a coherent reason so much the better!
-- Niall Litchfield Oracle DBA http://www.orawin.info -- http://www.freelists.org/webpage/oracle-l