redat 5.8由於檔案系統100%,導致oracle資料庫例項掛起處理例項
環境描述:
作業系統 redhatlinux 5.8
資料庫版本 oracle 11.2.0.1 單例項
狀況資訊:
由於本例項屬於外圍小系統並沒有對其 檔案系統,資料庫例項等狀態進行監控,故導致檔案系統滿了 導致例項掛起;
處理過程:
1. 經過檢視alter 日誌:如下文標紅部分 檔案系統無空間了,導致redolog 無法進行切換,導致例項掛起;
2. 由於出問題的時間為晚上10點左右,沒有告警機制,導致到第二天早上過來後,清理檔案系統,啟動資料庫例項後解決問題;
經驗總結:
增加相關監控項
增加檔案系統;
alter 告警日誌如下:
VKRM started with pid=133, OS id=12948
Mon Jul 18 22:00:01 2015
Begin automatic SQL Tuning Advisor run for special tuning task "SYS_AUTO_SQL_TUNING_TASK"
Mon Jul 18 22:00:03 2015
DM00 started with pid=156, OS id=12966, job WAPAPP.SYS_EXPORT_SCHEMA_09
Mon Jul 18 22:00:04 2015
DW00 started with pid=158, OS id=12970, wid=1, job WAPAPP.SYS_EXPORT_SCHEMA_09
Mon Jul 18 22:00:27 2015
End automatic SQL Tuning Advisor run for special tuning task "SYS_AUTO_SQL_TUNING_TASK"
Mon Jul 18 22:01:05 2015
Thread 1 cannot allocate new log, sequence 3948
Private strand flush not complete
Current log# 3 seq# 3947 mem# 0: /u08/app/oracle/oradata/*/redo03.log
Mon Jul 18 22:01:21 2015
Thread 1 advanced to log sequence 3948 (LGWR switch)
Current log# 4 seq# 3948 mem# 0: /u08/app/oracle/oradata/*/redo04.log
Mon Jul 18 22:02:08 2015
Non critical error ORA-00001 caught while writing to trace file "/u08/app/oracle/diag/rdbms/*/*/trace/*_dw00_12970.trc"
Error message:
Writing to the above trace file is disabled for now on...
Mon Jul 18 22:02:09 2015
opidcl aborting process unknown ospid (12861) as a result of ORA-9945
Mon Jul 18 22:02:09 2015
opidcl aborting process unknown ospid (12792) as a result of ORA-9945
Mon Jul 18 22:02:09 2015
Non critical error ORA-00001 caught while writing to trace file "/u08/app/oracle/diag/rdbms/*/*/trace/*_dm00_12966.trc"
Error message:
Writing to the above trace file is disabled for now on...
Mon Jul 18 22:02:10 2015
opidcl aborting process unknown ospid (12604) as a result of ORA-9945
Mon Jul 18 22:02:12 2015
opidcl aborting process unknown ospid (12639) as a result of ORA-9945
Mon Jul 18 22:02:13 2015
opidcl aborting process unknown ospid (12663) as a result of ORA-9945
Mon Jul 18 22:02:13 2015
opidcl aborting process unknown ospid (12691) as a result of ORA-9945
Mon Jul 18 22:02:13 2015
opidcl aborting process unknown ospid (12881) as a result of ORA-9945
Mon Jul 18 22:02:13 2015
Errors in file /u08/app/oracle/diag/rdbms/*/*/trace/*_pmon_11072.trc:
ORA-09817: Write to audit file failed.
Linux-x86_64 Error: 28: No space left on device
Additional information: 12
Errors in file /u08/app/oracle/diag/rdbms/*/*/trace/*_pmon_11072.trc:
ORA-09817: Write to audit file failed.
Linux-x86_64 Error: 28: No space left on device
Additional information: 12
Errors in file /u08/app/oracle/diag/rdbms/*/*/trace/*_pmon_11072.trc:
ORA-09817: Write to audit file failed.
Linux-x86_64 Error: 28: No space left on device
Additional information: 12
Errors in file /u08/app/oracle/diag/rdbms/*/*/trace/*_pmon_11072.trc:
ORA-09817: Write to audit file failed.Tue Jul 19 08:52:38 2015
作業系統 redhatlinux 5.8
資料庫版本 oracle 11.2.0.1 單例項
狀況資訊:
由於本例項屬於外圍小系統並沒有對其 檔案系統,資料庫例項等狀態進行監控,故導致檔案系統滿了 導致例項掛起;
處理過程:
1. 經過檢視alter 日誌:如下文標紅部分 檔案系統無空間了,導致redolog 無法進行切換,導致例項掛起;
2. 由於出問題的時間為晚上10點左右,沒有告警機制,導致到第二天早上過來後,清理檔案系統,啟動資料庫例項後解決問題;
經驗總結:
增加相關監控項
增加檔案系統;
alter 告警日誌如下:
VKRM started with pid=133, OS id=12948
Mon Jul 18 22:00:01 2015
Begin automatic SQL Tuning Advisor run for special tuning task "SYS_AUTO_SQL_TUNING_TASK"
Mon Jul 18 22:00:03 2015
DM00 started with pid=156, OS id=12966, job WAPAPP.SYS_EXPORT_SCHEMA_09
Mon Jul 18 22:00:04 2015
DW00 started with pid=158, OS id=12970, wid=1, job WAPAPP.SYS_EXPORT_SCHEMA_09
Mon Jul 18 22:00:27 2015
End automatic SQL Tuning Advisor run for special tuning task "SYS_AUTO_SQL_TUNING_TASK"
Mon Jul 18 22:01:05 2015
Thread 1 cannot allocate new log, sequence 3948
Private strand flush not complete
Current log# 3 seq# 3947 mem# 0: /u08/app/oracle/oradata/*/redo03.log
Mon Jul 18 22:01:21 2015
Thread 1 advanced to log sequence 3948 (LGWR switch)
Current log# 4 seq# 3948 mem# 0: /u08/app/oracle/oradata/*/redo04.log
Mon Jul 18 22:02:08 2015
Non critical error ORA-00001 caught while writing to trace file "/u08/app/oracle/diag/rdbms/*/*/trace/*_dw00_12970.trc"
Error message:
Writing to the above trace file is disabled for now on...
Mon Jul 18 22:02:09 2015
opidcl aborting process unknown ospid (12861) as a result of ORA-9945
Mon Jul 18 22:02:09 2015
opidcl aborting process unknown ospid (12792) as a result of ORA-9945
Mon Jul 18 22:02:09 2015
Non critical error ORA-00001 caught while writing to trace file "/u08/app/oracle/diag/rdbms/*/*/trace/*_dm00_12966.trc"
Error message:
Writing to the above trace file is disabled for now on...
Mon Jul 18 22:02:10 2015
opidcl aborting process unknown ospid (12604) as a result of ORA-9945
Mon Jul 18 22:02:12 2015
opidcl aborting process unknown ospid (12639) as a result of ORA-9945
Mon Jul 18 22:02:13 2015
opidcl aborting process unknown ospid (12663) as a result of ORA-9945
Mon Jul 18 22:02:13 2015
opidcl aborting process unknown ospid (12691) as a result of ORA-9945
Mon Jul 18 22:02:13 2015
opidcl aborting process unknown ospid (12881) as a result of ORA-9945
Mon Jul 18 22:02:13 2015
Errors in file /u08/app/oracle/diag/rdbms/*/*/trace/*_pmon_11072.trc:
ORA-09817: Write to audit file failed.
Linux-x86_64 Error: 28: No space left on device
Additional information: 12
Errors in file /u08/app/oracle/diag/rdbms/*/*/trace/*_pmon_11072.trc:
ORA-09817: Write to audit file failed.
Linux-x86_64 Error: 28: No space left on device
Additional information: 12
Errors in file /u08/app/oracle/diag/rdbms/*/*/trace/*_pmon_11072.trc:
ORA-09817: Write to audit file failed.
Linux-x86_64 Error: 28: No space left on device
Additional information: 12
Errors in file /u08/app/oracle/diag/rdbms/*/*/trace/*_pmon_11072.trc:
ORA-09817: Write to audit file failed.Tue Jul 19 08:52:38 2015
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/25462274/viewspace-2122211/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 由AIX系統故障導致系統重啟,使Oracle資料庫自動啟動例項AIOracle資料庫
- oracle 資料庫例項Oracle資料庫
- Oracle資料檔案收縮例項Oracle
- 歸檔日誌滿導致的資料庫掛起故障處理資料庫
- 建立物化檢視導致資料庫例項崩潰資料庫
- Oracle例項和Oracle資料庫Oracle資料庫
- oracle資料庫與oracle例項Oracle資料庫
- oracle資料庫例項狀態Oracle資料庫
- 歸檔日誌滿導致的資料庫掛起故障處理【轉載】資料庫
- jQuery如何處理xml檔案程式碼例項jQueryXML
- 【問題處理】因ASM磁碟組空間不足導致資料庫例項無法啟動的故障處理ASM資料庫
- 利用RMAN將資料庫從檔案系統遷移到ASM(單例項)資料庫ASM單例
- Oracle例項和Oracle資料庫(Oracle體系結構)Oracle資料庫
- 搗蛋SQL導致例項iops100%SQL
- [oracle]undo表空間出錯,導致資料庫例項無法開啟Oracle資料庫
- 多個ORACLE資料庫例項下listener.ora檔案配置Oracle資料庫
- 資料處理等待效果例項程式碼
- 【RAC】處理因ASM例項異常導致RAC第一節點例項異常終止故障ASM
- 歸檔空間不足導致例項死鎖
- 資料庫和例項資料庫
- 演示中斷處理的例項(例項六)(轉)
- 記一次:歸檔檔案系統問題導致資料庫hang處理資料庫
- SAX處理XML例項XML
- 多例項資料庫刪除例項資料庫
- Oracle Restart啟動資料庫例項故障一例OracleREST資料庫
- 2 Day DBA-管理Oracle例項-管理資料庫儲存結構-關於資料檔案Oracle資料庫
- Oracle資料檔案損壞恢復例項二則Oracle
- 3.1.5.1 關於啟動資料庫例項資料庫
- 11.2.0.3 ASM例項出現ORA-4031導致資料庫歸檔失敗ASM資料庫
- Oracle 11g單例項ASM遷移到檔案系統Oracle單例ASM
- 系統出現cursor: mutex X等待導致例項HANG死Mutex
- oracle資料庫建立資料庫例項-九五小龐Oracle資料庫
- oracle例項和資料庫的區別Oracle資料庫
- 【故障處理】修改主機名導致oracle例項無法啟動暨如何修改hostnameOracle
- 資料庫例項 (SQL Server)資料庫SQLServer
- 資料庫設計例項資料庫
- 重灌系統後,使用oradim建立資料庫例項!資料庫
- jQuery處理json格式資料程式碼例項jQueryJSON