ORA-00257: archiver error. Connect internal only, until freed.

來源:互聯網
上載者:User
error
環境:winxp+oracle9.2.0.1用戶端
             win2003+oracle9.2.0.5服務端
一、出錯過程:
在用戶端執行以下語句:
conn scott/tiger@pgjt
declare
i number;
begin
select s.nextval into i from dual;
while i<1000
loop
insert into b values (i);
end loop;
end;
出現錯誤,用戶端呈假死機現象。
新開一個視窗:
SQL> conn scott/tiger@pgjt
已串連。
SQL> select sid,serial#,username from v$session;

      SID   SERIAL# USERNAME
--------- --------- ------------------------------
        1         1
        2         1
        3         1
        4         1
        5         1
        6         1
        7         1
        8         1
        9         1
       10         1
       11         1
       12        14
       13         5 SCOTT
       14        15 SCOTT
       15         4
       16         1
       17         1
       18         1
       19         1
       20         4 NCCWGS

已選擇20行。

經過時間:  00: 00: 00.01
SQL> alter system kill session '13,5';

系統已更改。

經過時間:  00: 00: 00.00
SQL>

重複上面步驟大概3次後,
SQL> conn scott/tiger@pgjt
ERROR:
ORA-00257: archiver error. Connect internal only, until freed.

無法串連資料庫。

二、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 .

3、問題解決
歸檔日誌使用的磁碟空間已滿。刪除一些老的磁碟歸檔檔案
SQL> shutdown abort;
ORACLE instance shut down.
SQL> startup
ORACLE instance started.

Total System Global Area  542712360 bytes
Fixed Size                   455208 bytes
Variable Size             427819008 bytes
Database Buffers          109051904 bytes
Redo Buffers                5386240 bytes
Database mounted.
Database opened.
SQL> conn scott/tiger
Connected.
SQL>


相關文章

Cloud Intelligence Leading the Digital Future

Alibaba Cloud ACtivate Online Conference, Nov. 20th & 21st, 2019 (UTC+08)

Register Now >

Starter Package

SSD Cloud server and data transfer for only $2.50 a month

Get Started >

Alibaba Cloud Free Trial

Learn and experience the power of Alibaba Cloud with a free trial worth $300-1200 USD

Learn more >

聯繫我們

該頁面正文內容均來源於網絡整理,並不代表阿里雲官方的觀點,該頁面所提到的產品和服務也與阿里云無關,如果該頁面內容對您造成了困擾,歡迎寫郵件給我們,收到郵件我們將在5個工作日內處理。

如果您發現本社區中有涉嫌抄襲的內容,歡迎發送郵件至: info-contact@alibabacloud.com 進行舉報並提供相關證據,工作人員會在 5 個工作天內聯絡您,一經查實,本站將立刻刪除涉嫌侵權內容。