1. 程式人生 > >db_recovery_file_dest_size 滿導致資料庫啟動失敗

db_recovery_file_dest_size 滿導致資料庫啟動失敗

啟動資料庫時:
[email protected]>startup
ORACLE instance started.
Total System Global Area  417546240 bytes
Fixed Size                  2213936 bytes
Variable Size             327157712 bytes
Database Buffers           83886080 bytes
Redo Buffers                4288512 bytes
Database mounted.
ORA-03113: end-of-file on communication channel
Process ID: 1935
Session ID: 1 Serial number: 5

利用10046 事件跟蹤資料庫開啟過程:
[email protected]>startup mount
ORACLE instance started.
Total System Global Area  417546240 bytes
Fixed Size                  2213936 bytes
Variable Size             327157712 bytes
Database Buffers           83886080 bytes
Redo Buffers                4288512 bytes
Database mounted.
[email protected]
>oradebug setmypid Statement processed. [email protected]> [email protected]> [email protected]>oradebug event 10046 trace name context forever,level 12; Statement processed. [email protected]> [email protected]> [email protected]>oradebug tracefile_name /opt/oracle/diag/rdbms/orcl11g/orcl11g/trace/orcl11g_ora_1727.trc
[email protected]
>alter database open; alter database open * ERROR at line 1: ORA-03113: end-of-file on communication channel Process ID: 1727 Session ID: 1 Serial number: 5
檢視trace檔案:
ORA-19815: WARNING: db_recovery_file_dest_size of 4070572032 bytes is 100.00% used, and has 0 remaining bytes available.
************************************************************************
You have following choices to free up space from recovery area:
1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
   then consider changing RMAN ARCHIVELOG DELETION POLICY.
2. Back up files to tertiary device such as tape using RMAN
   BACKUP RECOVERY AREA command.
3. Add disk space and increase db_recovery_file_dest_size parameter to
   reflect the new space.
4. Delete unnecessary files using RMAN DELETE command. If an operating
   system command was used to delete files, then use RMAN CROSSCHECK and
   DELETE EXPIRED commands.
************************************************************************
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 43927552 bytes disk space from 4070572032 limit
*** 2014-11-15 21:20:56.648 4132 krsh.c
ARCH: Error 19809 Creating archive log file to '/opt/oracle/flash_recovery_area/ORCL11G/archivelog/2014_11_15/o1_mf_1_52_%u_.arc'
*** 2014-11-15 21:20:56.648 2747 krsi.c
krsi_dst_fail: dest:1 err:19809 force:0 blast:1
WAIT #1: nam='log file sequential read' ela= 5 log#=0 block#=0 blocks=0 obj#=-1 tim=1416104456648722
WAIT #1: nam='Disk file operations I/O' ela= 15 FileOperation=5 fileno=0 filetype=3 obj#=-1 tim=1416104456648774
WAIT #1: nam='control file sequential read' ela= 14 file#=0 block#=1 blocks=1 obj#=-1 tim=1416104456648863
WAIT #1: nam='control file sequential read' ela= 11 file#=0 block#=15 blocks=1 obj#=-1 tim=1416104456648969
WAIT #1: nam='control file sequential read' ela= 10 file#=0 block#=17 blocks=1 obj#=-1 tim=1416104456649013
WAIT #1: nam='control file sequential read' ela= 10 file#=0 block#=22 blocks=1 obj#=-1 tim=1416104456649075
WAIT #1: nam='control file parallel write' ela= 4671 files=1 block#=21 requests=1 obj#=-1 tim=1416104456653795
WAIT #1: nam='control file parallel write' ela= 956 files=1 block#=18 requests=1 obj#=-1 tim=1416104456654862
WAIT #1: nam='control file parallel write' ela= 1817 files=1 block#=16 requests=1 obj#=-1 tim=1416104456656679
WAIT #1: nam='control file parallel write' ela= 1295 files=1 block#=1 requests=1 obj#=-1 tim=1416104456658021
WAIT #1: nam='control file sequential read' ela= 14 file#=0 block#=1 blocks=1 obj#=-1 tim=1416104456658082
WAIT #1: nam='control file sequential read' ela= 12 file#=0 block#=32 blocks=1 obj#=-1 tim=1416104456658162
DDE: Problem Key 'ORA 312' was flood controlled (0x1) (no incident)
ORA-00312: online log 1 thread 1: '/opt/oracle/oradata/orcl11g/redo01.log'
ORA-16038: log 1 sequence# 52 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 1 thread 1: '/opt/oracle/oradata/orcl11g/redo01.log'
www.zbdba.com
*** 2014-11-15 21:20:56.660
USER (ospid: 2247): terminating the instance due to error 16038
原來是flash_recovery_area滿了,無法進行歸檔。增加db_recovery_file_dest_size:
[email protected]>alter system set db_recovery_file_dest_size=8G scope=spfile;

System altered.
[email protected]>startup
ORACLE instance started.
Total System Global Area  417546240 bytes
Fixed Size                  2213936 bytes
Variable Size             327157712 bytes
Database Buffers           83886080 bytes
Redo Buffers                4288512 bytes
Database mounted.
Database opened.
[email protected]>show parameter recover
NAME                                 TYPE                   VALUE
------------------------------------ ---------------------- ------------------------------
db_recovery_file_dest                string                 /opt/oracle/flash_recovery_are
                                                            a
db_recovery_file_dest_size           big integer            8G
recovery_parallelism                 integer                0

至此已經開啟資料庫,所以資料庫啟動失敗,我們利用10046事件跟蹤就能發現具體的原因。

相關推薦

db_recovery_file_dest_size 滿導致資料庫啟動失敗

啟動資料庫時:[email protected]>startup ORACLE instance started. Total System Global Area 417546240 bytes Fixed Size 2

linux環境下根目錄磁碟空間滿導致資料庫無法啟動的問題的解決

1、登陸資料庫時,把磁碟空間不足,無法登陸 [[email protected]flash_recovery_area]$sqlplus/assysdba SQL*Plus: Release10.2.0.1.0-Productionon 星期五 11月 2817:

oracle asm磁碟標籤丟失導致整個叢集和資料庫啟動失敗

應用環境描述一、硬體1、 伺服器:2臺dell r610—16G記憶體、2顆6核xeon cpu、2個146G sas盤,做了raid12、 儲存:dell MD3220 24個300G硬碟3、 儲存連線:6GB HBA卡,2個通道都連線了二、軟體1、 系統:64位centos 5.52、 系統核心版本:Li

hadoop 使用ip配置導致hdfs啟動失敗

hadoop $2 value servers 無法 col reg dfs property dataNode 有守護進行,但hdfs web頁面上顯示沒有live node。 錯誤日誌: 2017-06-21 17:44:59,513 ERROR org.apa

更換記憶體條導致windows啟動失敗,報錯資訊:windows無法驗證此檔案的數字簽名,2018.11;

》 問題描述: 給筆記本更換記憶體條,導致windows7 64開機失敗,並提示windows無法驗證此檔案的數字簽名; 搜了搜度娘,度娘說重灌系統吧;我去,電腦中一堆資料軟體,怎麼可能; 》 解決辦法: 1、會有提示說 F8 進入安全模式

注意了!雲伺服器的一些環境配置有可能導致應用啟動失敗

嘗試用serviceComb框架跟Spring boot框架結合寫了一個測試應用,結果放到雲伺服器上啟動的時候報錯,大概錯誤如下: Caused by: java.lang.IllegalArgumentException: Could not resolve placeholder '

spring-boot不同包結構下,同名類衝突導致服務啟動失敗解決方案

專案背景:   兩個專案的包結構和類名都很多相同,於是開始考慮使用加一級包進行隔離,類似於這種結構 但是在啟動的過程中,丟擲來這樣的異常: 1 2 3 4 5 6 7 8 9 Caused by: org.springframework.

Windows 更新導致 VirtualBox 啟動失敗

我的虛擬機器版本是 4.3.20, Windows 版本是 Windows 8,但今天突然發現 VirtualBox 啟動不了,報的錯誤如下: 為了搜尋引擎能檢索到此錯誤資訊,我將錯誤資訊的文字貼在下面: NtCreateFile(\Device\

selinux導致docker啟動失敗

本文轉載地址:http://www.cnblogs.com/elisun/p/6963818.html 1. 問題描述:一向執行正常的一群容器,突然有一天掛掉了,再也起不來,報錯如下 Error response from daemon: devmapper: Err

非正常關機導致mysql啟動失敗

電腦所有程式都沒有響應,卡的動不了就強制關機了,開機之後發現mysql服務啟動不了,查詢mysql的執行狀態是停止的,但是啟動又會失敗。 報錯:Another MySQL daemon already running with the same unix so

etcd子網配置失效導致Docker啟動失敗

Docker啟動失敗 執行 docker status docker 檢視原因,發現以下錯誤 Oct 14 16:39:10 *.*.* systemd[1]: Dependency failed for Docker Application Container Engi

MySQL資料庫啟動失敗解決

重啟伺服器後-->重啟應用服務(Confluence)-->報錯,資料庫連線失敗(MySQL設定了開機自啟動)-->檢視MySQL資料庫狀態: [[email protected] www.linuxidc.com ~]# ps -ef | grep mys

Breeze部署機非正常關閉導致Breeze啟動失敗

[[email protected] opt]#  docker-compose up -d Starting deploy-yumrepo  ... error Starting deploy-playbook ... Starting deploy-playbo

java web @WebServlet和web.xml衝突,導致tomcat啟動失敗

添加了一個servlet,自動配置了 @WebServlet  ,又在web.xml裡配置映射了這個servlet路徑,然後啟動tomcat失敗,eclipse 出現 下圖的錯誤提示 然後cons

no space left on device 導致伺服器啟動失敗

註冊部落格園很長時間了,一直都沒有寫過東西,只是將他用作收集網頁資料的工具。最近一直在忙其他的東西,昨天下午突然什麼都想幹,就想把糾結了一個月的Ubuntu下low graphic問題解決掉。     我的Ubuntu系統裝在本本原來的系統備份盤上,只有10.8個G,裝完U

NT KERNEL & SYSTEM 程序佔用 80 埠導致 Nginx 啟動失敗

資源更新伺服器被搞蹦了,重啟之後發現 從下載版本號 下載不了了,瀏覽器 IP 直連一看 ,Http伺服器沒開。先用命令測試開啟nginx -t提示說沒有許可權訪問80 埠bind() to 0.0.0.0:80 failed (10013: An attempt was ma

ojdbc14版本過低導致資料庫連線失敗 Connection reset

java.sql.SQLException: Io 異常: Connection resetat oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)at oracle.jdbc.dbaccess.

Rac 安裝後修改使用者名稱導致CRS啟動失敗

問題:RAC安裝成功後,是否可以更改RAC 安裝使用者 1.        執行環境使用administrator安裝RAC,修改administrator為dbuser 2.        重啟動節點1,2,,登陸dbuser 3.       檢查CRS狀態 檢視C

修改RAC中的私網地址導致CRS啟動失敗

在自己的虛擬機器中試驗,由於疏忽,將私網的地址和公網的地址配在了一個網段,導致將私網斷掉後,RAC也不會腦裂, 打算將私網ip 換成另外一個網段: 步驟如下: 1)關閉叢集 [[email protected] ~]$ crsctl stop cluster -a

oracle11g連線數滿導致資料庫重啟

現象: 版本:oracle11.2.0.3 今天資料庫出現連線數滿導致資料庫重啟的現象 PMON failed to acquire latch, see PMON dump Mon Jan 21 16:23:55 2013 ORA-00020: 超出最大程序數 (600)