Automatic Archiving does not Restart if Disk Space is Full(轉自Metalink)

 Automatic Archiving does not Restart if Disk Space is Full

[@more@]

文件 ID:  註釋:131427.1
主題:  Automatic Archiving does not Restart if Disk Space is Full
型別:  PROBLEM
狀態:  PUBLISHED
 內容型別:  TEXT/PLAIN
建立日期:  03-JAN-2001
上次修訂日期:  22-JAN-2002
 

Problem Description ------------------- 

The database is running in archive log mode with automatic archiving turned on. When the archive log destination diskspace becomes full the automatic archiving will stop.  This is expected to happen.  At this point a message should appear  on the screen:  ORACLE Instance v816 - Can not allocate log, archival required  When all of the online redo logs are filled up, the database will be in a hang  state.  After freeing up diskspace the online redo logs are still not archiving.  In  most cases this is the CORRECT behaviour. 

If you attempt to manually archive the files you may receive the following errors: 

SVRMGR> archive log next ORA-16014: log 1 sequence# 199 not archived, no available destinations ORA-00312: online log 1 thread 1: 'C:ORACLEORADATAV816REDO01.LOG' 

SVRMGR> archive log all ORA-16020: less destinations available than specified by LOG_ARCHIVE_MIN_SUCCEED_DEST  

Solution Description -------------------- 

Some of the possible ways to fix this problem: 

1.  Use the command:     

  alter system archive log all to 'c:oracleoradatav816archive';        *NOTE:  You MUST specify a location ref - ora-16014 

2.  Shutdown and restart the database.  It may be necessary to do a Shutdown     abort. 

3. Use the REOPEN attribute of the LOG_ARCHIVE_DEST_n init.ora parameter.    

  LOG_ARCHIVE_DEST_n='  REOPEN=30'     Or run the following comand:      

  alter system set LOG_ARCHIVE_DEST_n = 'reopen' 

4. Use the commands:        

alter system archive log stop;     alter system archive log start;  

Explanation ----------- 

The error ora-16014 is the real clue for this problem.  Once the archive  destination becomes full the location also becomes invalid.  Normally Oracle  does not do a recheck to see if space has been made available. 

1.  Using the command: alter system archive log all to 'c:oracleoradatav816archive';   gives Oracle a valid location for the archive logs.  Even after using this the  archive log destination parameter is still invalid and automatic achive does not work.  This solution is best for systems that do not archive regularly but cannot be shutdown.  You can also use this to allow you to do a Shutdown  immediate instead of Shutdown abort. 

2.  Shutdown and restart of the database resets the archive log destinstation  parameter to be valid.  Do not forget to make disk space available before  starting the database. 

3. Use the REOPEN attribute of the LOG_ARCHIVE_DEST_n parameter to determine  whether and when ARCn attempts to re-archive to a failed destination following an error.  REOPEN applies to all errors, not just OPEN errors.   REOPEN=n sets the minimum number of seconds before ARCn should try to reopen a failed destination.  The default value for n is 300 seconds.  A value of 0 is the same as turning off the REOPEN option, in other words, ARCn will not  attempt to archive after a failure.  If you do not specify the REOPEN keyword,  ARCn will never reopen a destination following an error.  The Server  Administration Guide has more information on REOPEN.  

References ---------- 

[BUG:1271752] AUTOMATIC ARCHIVING HAS NOT RESUMED AFTER SPACE IS FREED UP Server Administration Guide:  Chapter 7 

[NOTE:74324.1] Auto Archive Stopped - 8i LOG_ARCHIVE_DEST_n Issues . 

--------------------------------------------------------------------------------
 
 Copyright (c) 1995,2000 Oracle Corporation. All Rights Reserved. 法律宣告和使用條款。