ORA-01208 的原因與解決方法
You encounter the following errors being signaled in the alert log periodically:
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
ORA-01122: database file %d failed verification check
ORA-01110: data file %d: '%s'
ORA-01208: data file is an old version - not accessing current version
The data file specified however stays on-line and available so no apparent corruption exists, and no I/O errors are encountered on the underlying disk.
Cause
This problem can occur when running a database in NOARCHIVELOG mode due to heavy disk I/O usage such that I/O performance is impacted, for example when redo log switches are occurring too frequently, such that the control file gets updated with the latest checkpoint scn, but the data file is then accessed prior to its header being updated with the same checkpoint scn information, and so Oracle reports the ORA-1208 error as the data file is older than listed in the control file. Subsequently the data file header is updated and so can be accessed normally with no corruption having occurred.
Solution
The solution here is to resolve the underlying disk I/O performance issue. If this is occurring due to redo log switches occurring too quickly, i.e. a few seconds apart, then refer to Note:147468.1 on how to tune checkpoint operations and in particular section 4 relating to correct redo log file sizing (see Note:1038851.6) to resolve the problem.
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
ORA-01122: database file %d failed verification check
ORA-01110: data file %d: '%s'
ORA-01208: data file is an old version - not accessing current version
The data file specified however stays on-line and available so no apparent corruption exists, and no I/O errors are encountered on the underlying disk.
Cause
This problem can occur when running a database in NOARCHIVELOG mode due to heavy disk I/O usage such that I/O performance is impacted, for example when redo log switches are occurring too frequently, such that the control file gets updated with the latest checkpoint scn, but the data file is then accessed prior to its header being updated with the same checkpoint scn information, and so Oracle reports the ORA-1208 error as the data file is older than listed in the control file. Subsequently the data file header is updated and so can be accessed normally with no corruption having occurred.
Solution
The solution here is to resolve the underlying disk I/O performance issue. If this is occurring due to redo log switches occurring too quickly, i.e. a few seconds apart, then refer to Note:147468.1 on how to tune checkpoint operations and in particular section 4 relating to correct redo log file sizing (see Note:1038851.6) to resolve the problem.
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/22664653/viewspace-676045/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- MSSQL資料庫超時的原因與解決方法SQL資料庫
- ANR原因及解決方法
- iMac和MBP乙太網介面失效的原因與解決方法Mac
- Linux 動態庫 undefined symbol 原因定位與解決方法LinuxUndefinedSymbol
- mysqldump意外終止的原因以及解決方法MySql
- ORA-04031 的原因分析解決方法
- Mac電腦無法透過有線上網的原因與解決方法Mac
- 總結mysql伺服器查詢慢原因與解決方法MySql伺服器
- ORA-00214 錯誤產生原因與解決方法
- No input file specified 出現的原因及解決方法
- computer browser關閉原因解決方法
- DVR常見故障原因及解決方法VR
- mysql伺服器查詢慢原因分析與解決方法小結MySql伺服器
- Linux中產生zombie的原因詳解及解決方法!Linux
- 網站內頁不收錄的原因及解決方法網站
- 專案成本超支的主要原因以及解決方法
- DNS故障的幾種常見原因及解決方法DNS
- impdp操作產生大量UNDO的原因及解決方法
- Windows變慢原因分析及解決方法(轉)Windows
- 揭秘繞線電感線圈感量偏低的原因與解決方法gujing
- 印表機無法列印的原因與解決辦法
- 百度快照被劫持的原因及解決方法、百度快照劫持的解決方法全
- 撥號VPS中691的可能原因及解決方法?
- 技術分享 | DNS解析不生效的原因及解決方法DNS
- u盤複製速度慢的原因及解決方法
- 資料庫連線失敗的原因及解決方法資料庫
- 資料庫連線錯誤的原因及解決方法資料庫
- Ajax跨越問題原因分析與解決思路
- DEDECMS織夢採集時提示讀取網址失敗的原因與解決方法
- 【MySQL】常見slave 延遲原因以及解決方法MySql
- 造成跨域的原因和解決方法跨域
- 引起索引失效的原因和解決方法索引
- 海外常見的http錯誤程式碼原因與解決HTTP
- IE打不開網頁的原因與解決辦法網頁
- 筆記本螢幕暗的原因與解決辦法筆記
- 網通封路由器的原因與解決辦法路由器
- 路由器常見故障的原因與解決辦法路由器
- 伺服器自動重啟的原因及解決方法-VeCloud伺服器Cloud