Check if the previous backups are done propelry. remove all the archive log files before the backup. or keep on moving. Purging is the best idea. regards - Chirag On 9/16/05, Thiagoo <thiagoodba@xxxxxxxxx> wrote: > > Hi, > > Yesterday, I had problem with Archive Log, Pls tell me whether am I > following the right steps. > > My Prod Archive Log destination got full. No one was able to connect to > the DB, it was hanging. > > The Tivoli Storage Monitor which should have alerted me, but it didnt > work for some reason in their server. > > Once the Archive Log destination got full 100%, I got the page and when I > realized that it must be with ARCH log, I started moving few ARCH files to a > temporary folder and started RMAN backup(for ARCH Files only) & once backup > is done it will delete the ARCH files and I moved back those ARCH files from > the temporary folder to the original destination. > > Moving those ARCH log files from one folder to another will it cause > corruption? My colleague cautioned that this corrupted files may corrupt the > whole RMAN database and we will loose the whole backup, Pls explain. > > TIA > > -Thiagu > > ------------------------------ > Yahoo! for Good > Click here to donate <http://store.yahoo.com/redcross-donate3/> to the > Hurricane Katrina relief effort. > >