Archive log directory going full, what needs to , only 6% available
This is for your information archive log file are using for backup & recovery database using RMAN. Oracle database track all of change log in log files (also called redo log files). When log file are switch then this log file send to archive location (This file called archive log file).
There are more than one solution for this problem ..
1. If you have available disk space in your hard drive then you can add another destination. Database will try to put logs on both destinations, but if one of them is full it will fail and will put it only in the second destination. This is not a problem.
First you need to see current archive destination and size. You can monitor your archive log files details from this dynamic performance view "V$ARCHIVED_LOG".
SQL> SHOW PARAMETER LOG_ARCHIVE_MIN_SUCCEED_DEST
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
log_archive_min_succeed_dest integer 1
SQL>
SQL> SHOW PARAMETER DB_RECOVERY_FILE_DEST
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
db_recovery_file_dest string D:\app\flash_recovery_area
db_recovery_file_dest_size big integer 8000M
SQL> SELECT DEST_NAME,STATUS,DESTINATION FROM V$ARCHIVE_DEST;
DEST_NAME
STATUS DESTINATION
------------------------------------------------------------------------------------
------------------------------------------------------------------------------------
LOG_ARCHIVE_DEST_1
VALID D:\APP\ORADATA\ARCHIVE\
LOG_ARCHIVE_DEST_2
INACTIVE
LOG_ARCHIVE_DEST_3
INACTIVE
SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_2='LOCATION=D:\app\oradata\ARCHIVE2' SCOPE=BOTH;
SYSTEM ALTERED.
SQL> SELECT DEST_NAME,STATUS,DESTINATION FROM V$ARCHIVE_DEST;
DEST_NAME
STATUS DESTINATION
------------------------------------------------------------------------------------------
-------------------------------------------------------- --------- -----------------------
------------------------------------------------------------------------------------------
LOG_ARCHIVE_DEST_1
VALID D:\APP\ORADATA\ARCHIVE\
LOG_ARCHIVE_DEST_2
VALID D:\APP\ORADATA\ARCHIVE2
2. You can manually cut and past to another location all of archive log files. You must remember that if your archive log file backup are not complete by RMAN then you need to put all of this file in same location.
3. You can take backup by using RMAN and remove archive log list.
This is for your information archive log file are using for backup & recovery database using RMAN. Oracle database track all of change log in log files (also called redo log files). When log file are switch then this log file send to archive location (This file called archive log file).
There are more than one solution for this problem ..
1. If you have available disk space in your hard drive then you can add another destination. Database will try to put logs on both destinations, but if one of them is full it will fail and will put it only in the second destination. This is not a problem.
First you need to see current archive destination and size. You can monitor your archive log files details from this dynamic performance view "V$ARCHIVED_LOG".
SQL> SHOW PARAMETER LOG_ARCHIVE_MIN_SUCCEED_DEST
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
log_archive_min_succeed_dest integer 1
SQL>
SQL> SHOW PARAMETER DB_RECOVERY_FILE_DEST
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
db_recovery_file_dest string D:\app\flash_recovery_area
db_recovery_file_dest_size big integer 8000M
SQL> SELECT DEST_NAME,STATUS,DESTINATION FROM V$ARCHIVE_DEST;
DEST_NAME
STATUS DESTINATION
------------------------------------------------------------------------------------
------------------------------------------------------------------------------------
LOG_ARCHIVE_DEST_1
VALID D:\APP\ORADATA\ARCHIVE\
LOG_ARCHIVE_DEST_2
INACTIVE
LOG_ARCHIVE_DEST_3
INACTIVE
SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_2='LOCATION=D:\app\oradata\ARCHIVE2' SCOPE=BOTH;
SYSTEM ALTERED.
SQL> SELECT DEST_NAME,STATUS,DESTINATION FROM V$ARCHIVE_DEST;
DEST_NAME
STATUS DESTINATION
------------------------------------------------------------------------------------------
-------------------------------------------------------- --------- -----------------------
------------------------------------------------------------------------------------------
LOG_ARCHIVE_DEST_1
VALID D:\APP\ORADATA\ARCHIVE\
LOG_ARCHIVE_DEST_2
VALID D:\APP\ORADATA\ARCHIVE2
2. You can manually cut and past to another location all of archive log files. You must remember that if your archive log file backup are not complete by RMAN then you need to put all of this file in same location.
3. You can take backup by using RMAN and remove archive log list.
No comments:
Post a Comment