Pro Oracle Database 11g Administration - Plot & Excerpts
This approach is dangerous because you may need those archive-redo logs for a subsequent recovery. If you do remove archive-redo log files, and you don’t have a backup of them, you should make a full backup of your database as soon as possible. If another location on your server has plenty of space, you can consider changing the location to which the archive-redo logs are being written. For example: SQL> alter system set log_archive_dest_1='location=/oraarch02'; After you’ve resolve the issue with the primary location, you can switch back the original location. You can perform this operation while the database is up and running. When the archive-redo log-file destination is full, you have to scramble to resolve it. This is why a good deal of thought should precede enabling archiving for production 24x7 databases. For most databases, writing the archive-redo logs to one location is sufficient. However, if you have any type of disaster-recovery or high-availability requirement, then you should write to multiple locations.
What do You think about Pro Oracle Database 11g Administration?
