If you dump the archives you must let rman know that they are either no
longer there ore obsolete. Try running the crosscheck command.
1. change archivelog all crosscheck;
or
2. crosscheck archivelog all;
depending on the feedback, you will have to delete obsolete or delete
expired archivelog. You may also have to "allocate channel for
maintenance type disk;" in order to do that.
Hope it works
Sabina.




"Anthony Ballo " <oracledba-ezmlmshield-x97954574.[Email address protected]

01/27/2006 12:08 PM

To
"LazyDBA Discussion" <[Email address protected]
cc

Subject
New server - archive log mode






I'm importing data over to a new (empty) server (9.2.0.7) that was in
archive log mode. The Import stalled b/c I ran out of disc space and
also disabled the auto-archiving in OEM by itself it seems.

I moved files off to another drive and made room, and enabled
auto-archiving again, and everything resumed it seems.

Questions:

1. Can I dump the old archive logs? If so, what do I have to do (if
anything) in RMAN to resync?
2. Can I turn off archiving before a refresh (import) not to create logs
?


-- Anthony


--------
website: http://www.LazyDBA.com
Please don't reply to RTFM questions
Oracle documentation is here: http://tahiti.oracle.com
To unsubscribe: see http://www.lazydba.com/unsubscribe.html
To subscribe: see http://www.lazydba.com
By using this list you agree to these terms:
http://www.lazydba.com/legal.html



Oracle LazyDBA home page