Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Oracle Archive file

506791Mar 25 2010 — edited Mar 26 2010
My 11g database is in archivelog mode, I noticed that there are sequential files generated in the RDBMS directory with the extension .001 when I also have the Archivedlog file under the flash_recovery_area *.arc files.
Why do I need both files. I know that one is duplication of the other. Can I just delete the .001 files since I already have the *.arc in the flash_recovery_area. If RMAN users the *.arc when recovering the database why do I still need the .001 files. The .001 files consume much of the hard disk space. Can I just delete, does RMAN catalog delete .001 when issuing the delete while recovering.

Thanks
Mhnd.
This post has been answered by EdStevens on Mar 26 2010
Jump to Answer

Comments

avramits
Is it standby database?

yes you can delete .001 log files.
Also can you post output from

sqlplus "/ as sysdba"

show parameter log

It would be interesting to see what is generating those files.
729338
You can delete .00* files, Oracle will need only arcgive logs files and backup to recover the database. Also check why these files are getting generated. They should not be generating if you do not need it.

Regards
506791
I think I figured this out.
They are copy of every *.arc file that get generated.
It gets generated as a duplicate to each archive file that gets gnerated due to enabling one of the other destention for the archive files. Something like a fault tolerance.
*.001 due to enabling the log_archive_dest_1 parameter to that directory.
EdStevens
Answer
Mhnd wrote:
I think I figured this out.
They are copy of every *.arc file that get generated.
It gets generated as a duplicate to each archive file that gets gnerated due to enabling one of the other destention for the archive files. Something like a fault tolerance.
*.001 due to enabling the log_archive_dest_1 parameter to that directory.
rman should take care of that for you. If you issue
rman> backup archivelog delete input;
it will only delete the backed up archivelogs from the FRA, but if you issue
rman> backup archivelog delete all input;
it will delete the backed up archivelogs from all archive destinations.
Marked as Answer by 506791 · Sep 27 2020
506791
Thanks to all participants!
1 - 5
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Apr 23 2010
Added on Mar 25 2010
5 comments
6,003 views