archive log 日誌已滿“ORA-00257: archiver error”
archive log 日誌已滿
ORA-00257: archiver error. Connect internal only, until freed 錯誤的處理方法
1. 用sys使用者登入
sqlplus as sysdba
2. 看看archiv log所在位置
SQL> show parameter log_archive_dest;
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
log_archive_dest string
log_archive_dest_1 string
log_archive_dest_10 string
3. 一般VALUE為空時,可以用archive log list;檢查一下歸檔目錄和log sequence
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 360
Next log sequence to archive 360
Current log sequence 362
4. 檢查flash recovery area的使用情況,可以看見archivelog已經很大了,達到96.62
SQL> select * from V$FLASH_RECOVERY_AREA_USAGE;
FILE_TYPE PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
------------ ------------------ ------------------------- ---------------
CONTROLFILE .13 0 1
ONLINELOG 2.93 0 3
ARCHIVELOG 96.62 0 141
BACKUPPIECE 0 0 0
IMAGECOPY 0 0 0
FLASHBACKLOG 0 0 0
5. 計算flash recovery area已經佔用的空間
SQL> select sum(percent_space_used)*3/100 from v$flash_recovery_area_usage;
SUM(PERCENT_SPACE_USED)*3/100
-----------------------------
2.9904
6. 找到recovery目錄, show parameter recover
SQL> show parameter recover;
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
db_recovery_file_dest string /u01/app/oracle/flash_recovery_area
db_recovery_file_dest_size big integer 5G
recovery_parallelism integer 0
7 上述結果告訴我們,歸檔位置用的是預設值,放在flash_recovery_area下(db_recovery_file_dest目錄=/u01/app/oracle/flash_recovery_area)
[root@sha3 10.2.0]# echo $ORACLE_BASE
/u01/app/oracle
[root@sha3 10.2.0]# cd $ORACLE_BASE/flash_recovery_area/tt/archivelog
轉移或清除對應的歸檔日誌, 刪除一些不用的日期目錄的檔案,注意保留最後幾個檔案(比如360以後的)
---------------------------------------------------------------------------------------
注意:
在刪除歸檔日誌後,必須用RMAN維護控制檔案,否則空間顯示仍然不釋放。
---------------------------------------------------------------------------------------
8. rman target sys/pass
[root@sha3 oracle]# rman target sys/pass
Recovery Manager: Release 10.2.0.4.0 - Production on Tue Jan 20 01:41:26 2009
Copyright (c) 1982, 2007, . All rights reserved.
connected to target database: tt (DBID=4147983671)
9. 檢查一些無用的archivelog
RMAN> crosscheck archivelog all;
10. 刪除過期的歸檔
RMAN> delete expired archivelog all;
delete archivelog until time 'sysdate-1' ; 刪除截止到前一天的所有archivelog
11. 再次查詢,發現使用率正常,已經降到23.03
SQL> select * from V$FLASH_RECOVERY_AREA_USAGE;
FILE_TYPE PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
------------ ------------------ ------------------------- ---------------
CONTROLFILE .13 0 1
ONLINELOG 2.93 0 3
ARCHIVELOG 23.03 0 36
BACKUPPIECE 0 0 0
IMAGECOPY 0 0 0
FLASHBACKLOG 0 0 0
其它有用的Command:
----------------------------------
如果archive log模式下不能正常startup,則先恢復成noarchive log,startup成功後,再shutdown;
shutdown immediate;
startup mount;
alter database noarchivelog;
alter database open;
shutdown immediate;
再次startup以archive log模式
shutdown immediate;
startup mount;
show parameter log_archive_dest;
alter database archivelog;
archive log list;
alter database open;
如果還不行,則刪除一些archlog log
SQL> select group#,sequence# from v$log;
GROUP# SEQUENCE#
---------- ----------
1 62
3 64
2 63
原來是日誌組一的一個日誌不能歸檔
SQL> alter database clear unarchived logfile group 1;
alter database open;
最後,也可以指定位置Arch Log, 請按照如下配置
select name from v$datafile;
alter system set log_archive_dest='/opt/app/oracle/oradata/usagedb/arch' scope=spfile
或者修改大小
SQL> alter system set db_recovery_file_dest_size=3G scope=both;
ORA-00257: archiver error. Connect internal only, until freed 錯誤的處理方法
1. 用sys使用者登入
sqlplus as sysdba
2. 看看archiv log所在位置
SQL> show parameter log_archive_dest;
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
log_archive_dest string
log_archive_dest_1 string
log_archive_dest_10 string
3. 一般VALUE為空時,可以用archive log list;檢查一下歸檔目錄和log sequence
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 360
Next log sequence to archive 360
Current log sequence 362
4. 檢查flash recovery area的使用情況,可以看見archivelog已經很大了,達到96.62
SQL> select * from V$FLASH_RECOVERY_AREA_USAGE;
FILE_TYPE PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
------------ ------------------ ------------------------- ---------------
CONTROLFILE .13 0 1
ONLINELOG 2.93 0 3
ARCHIVELOG 96.62 0 141
BACKUPPIECE 0 0 0
IMAGECOPY 0 0 0
FLASHBACKLOG 0 0 0
5. 計算flash recovery area已經佔用的空間
SQL> select sum(percent_space_used)*3/100 from v$flash_recovery_area_usage;
SUM(PERCENT_SPACE_USED)*3/100
-----------------------------
2.9904
6. 找到recovery目錄, show parameter recover
SQL> show parameter recover;
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
db_recovery_file_dest string /u01/app/oracle/flash_recovery_area
db_recovery_file_dest_size big integer 5G
recovery_parallelism integer 0
7 上述結果告訴我們,歸檔位置用的是預設值,放在flash_recovery_area下(db_recovery_file_dest目錄=/u01/app/oracle/flash_recovery_area)
[root@sha3 10.2.0]# echo $ORACLE_BASE
/u01/app/oracle
[root@sha3 10.2.0]# cd $ORACLE_BASE/flash_recovery_area/tt/archivelog
轉移或清除對應的歸檔日誌, 刪除一些不用的日期目錄的檔案,注意保留最後幾個檔案(比如360以後的)
---------------------------------------------------------------------------------------
注意:
在刪除歸檔日誌後,必須用RMAN維護控制檔案,否則空間顯示仍然不釋放。
---------------------------------------------------------------------------------------
8. rman target sys/pass
[root@sha3 oracle]# rman target sys/pass
Recovery Manager: Release 10.2.0.4.0 - Production on Tue Jan 20 01:41:26 2009
Copyright (c) 1982, 2007, . All rights reserved.
connected to target database: tt (DBID=4147983671)
9. 檢查一些無用的archivelog
RMAN> crosscheck archivelog all;
10. 刪除過期的歸檔
RMAN> delete expired archivelog all;
delete archivelog until time 'sysdate-1' ; 刪除截止到前一天的所有archivelog
11. 再次查詢,發現使用率正常,已經降到23.03
SQL> select * from V$FLASH_RECOVERY_AREA_USAGE;
FILE_TYPE PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
------------ ------------------ ------------------------- ---------------
CONTROLFILE .13 0 1
ONLINELOG 2.93 0 3
ARCHIVELOG 23.03 0 36
BACKUPPIECE 0 0 0
IMAGECOPY 0 0 0
FLASHBACKLOG 0 0 0
其它有用的Command:
----------------------------------
如果archive log模式下不能正常startup,則先恢復成noarchive log,startup成功後,再shutdown;
shutdown immediate;
startup mount;
alter database noarchivelog;
alter database open;
shutdown immediate;
再次startup以archive log模式
shutdown immediate;
startup mount;
show parameter log_archive_dest;
alter database archivelog;
archive log list;
alter database open;
如果還不行,則刪除一些archlog log
SQL> select group#,sequence# from v$log;
GROUP# SEQUENCE#
---------- ----------
1 62
3 64
2 63
原來是日誌組一的一個日誌不能歸檔
SQL> alter database clear unarchived logfile group 1;
alter database open;
最後,也可以指定位置Arch Log, 請按照如下配置
select name from v$datafile;
alter system set log_archive_dest='/opt/app/oracle/oradata/usagedb/arch' scope=spfile
或者修改大小
SQL> alter system set db_recovery_file_dest_size=3G scope=both;
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/76103/viewspace-1474479/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- ARCHIVE歸檔日誌爆滿故障ORA-00257Hive
- ORA-00257歸檔日誌空間已滿
- ORA-00257歸檔日誌滿
- archive log 歸檔日誌Hive
- oracle archive log 歸檔日誌OracleHive
- ORA-00257: archiver error. Connect internal onlyHiveError
- ORA-00257 archiver error--資料閃回區滿導致無法歸檔HiveError
- SQLSERVER事務日誌已滿 the transaction log for database 'xx' is fullSQLServerDatabase
- Oracle archive log 歸檔日誌管理OracleHive
- ORA-00257 archiver error. 錯誤的處理方法HiveError
- 登入 Oracle 資料庫報錯,ORA-00257: archiver errorOracle資料庫HiveError
- ORA-00257: archiver error. Connect internal only, until freedHiveError
- ORA-00257歸檔日誌寫滿的解決方法
- ORA-00257:archiver error. Connect internal only,until freed.HiveError
- ORA-00257: archiver error. Connect internal only, until freed.HiveError
- SQL Sever 7日誌檔案已滿SQL
- 解決ORA-00257:archiver error.Connect internal only, until freedHiveError
- 解決ORA-00257: archiver error. Connect internal only, until freedHiveError
- ORA-16014/ORA-00257 archiver error Connect internal onlyHiveError
- ORA-00257: archiver error. Connect internal only, until freed 解決方法HiveError
- logstash nginx error access 日誌處理NginxError
- 如果資料庫日誌已滿,怎麼辦?資料庫
- 2、MySQL錯誤日誌(Error Log)詳解MySqlError
- 伺服器事務日誌已滿解決方法伺服器
- nginx error_log 錯誤日誌配置說明NginxError
- ORA-00257: archiver error. Connect internal only, until freed 錯誤的處理方法HiveError
- (f)--閃回恢復區-- 報錯ORA-00257: archiver error. Connect internal HiveError
- 歸檔日誌路徑三個引數DB_RECOVERY_FILE_DEST和LOG_ARCHIVE_DEST和LOG_ARCHIVE_DEST_nHive
- Log日誌
- 【歸檔日誌路徑】之引數 log_archive_dest、LOG_ARCHIVE_DEST_n及快速恢復區路徑關係Hive
- 2011.1.13報錯。.ORA-00257: archiver error. Connect internal only, until freed.HiveError
- DB2報“資料庫日誌已滿”問題解決DB2資料庫
- Weblogic日誌Web
- log 日誌原理
- SQL Server中 error log 日誌檔案如何手動切換SQLServerError
- SQLServer 2008中事務日誌已滿問題處理SQLServer
- Python 日誌(Log)Python
- Logminer日誌挖掘