ORA-00600 [13013] [5001] [474] [4198011] [102]-Oracle 問題處理過程
ORA-00600 [13013] [5001] [474] [4198011] [102] [4198011] [17]-記錄一次Oracle ORA-00600 [13013]處理過程
redhat linux 4.7 平臺下 32bit Oracle 10.1.0.3 升級至10.2.0.5版本,並安裝了14275629 patchset,升級完後發現Oracle中一些元件狀態為invalid,升級後要到一些Oracle ORA問題,記錄下處理過程
1. ORA-00322、ORA-00312問題
兩臺機器做HA,由於HA管理軟體問題,致使兩臺機器的Oracle啟動,資料庫alert日誌報錯ORA-00322、ORA-00312問題,最先報出問題的機器上的Oracle alert日誌如下:
......
Tue Dec 25 20:32:23 CST 2012
ALTER DATABASE OPEN
Tue Dec 25 20:32:25 CST 2012
Errors in file /bases/oracle/admin/ctwapgw/bdump/ctwapgw_lgwr_20423.trc:
ORA-00322: Message 322 not found; No message file for product=RDBMS, facility=ORA; arguments: [5] [1]
ORA-00312: Message 312 not found; No message file for product=RDBMS, facility=ORA; arguments: [5] [1] [/bases/oracle/oradata/ctwapgw/redo05.log]
Tue Dec 25 20:32:25 CST 2012
Errors in file /bases/oracle/admin/ctwapgw/bdump/ctwapgw_lgwr_20423.trc:
ORA-00322: Message 322 not found; No message file for product=RDBMS, facility=ORA; arguments: [5] [1]
ORA-00312: Message 312 not found; No message file for product=RDBMS, facility=ORA; arguments: [5] [1] [/bases/oracle/oradata/ctwapgw/redo05.log]
ORA-322 signalled during: ALTER DATABASE OPEN...
Tue Dec 25 20:38:05 CST 2012
alter database open
Tue Dec 25 20:38:06 CST 2012
Errors in file /bases/oracle/admin/ctwapgw/bdump/ctwapgw_lgwr_20423.trc:
ORA-00322: Message 322 not found; No message file for product=RDBMS, facility=ORA; arguments: [5] [1]
ORA-00312: Message 312 not found; No message file for product=RDBMS, facility=ORA; arguments: [5] [1] [/bases/oracle/oradata/ctwapgw/redo05.log]
Tue Dec 25 20:38:06 CST 2012
Errors in file /bases/oracle/admin/ctwapgw/bdump/ctwapgw_lgwr_20423.trc:
ORA-00322: Message 322 not found; No message file for product=RDBMS, facility=ORA; arguments: [5] [1]
ORA-00312: Message 312 not found; No message file for product=RDBMS, facility=ORA; arguments: [5] [1] [/bases/oracle/oradata/ctwapgw/redo05.log]
Tue Dec 25 20:38:06 CST 2012
ORA-322 signalled during: alter database open..
ALTER DATABASE OPEN
Tue Dec 25 20:32:25 CST 2012
Errors in file /bases/oracle/admin/ctwapgw/bdump/ctwapgw_lgwr_20423.trc:
ORA-00322: Message 322 not found; No message file for product=RDBMS, facility=ORA; arguments: [5] [1]
ORA-00312: Message 312 not found; No message file for product=RDBMS, facility=ORA; arguments: [5] [1] [/bases/oracle/oradata/ctwapgw/redo05.log]
Tue Dec 25 20:32:25 CST 2012
Errors in file /bases/oracle/admin/ctwapgw/bdump/ctwapgw_lgwr_20423.trc:
ORA-00322: Message 322 not found; No message file for product=RDBMS, facility=ORA; arguments: [5] [1]
ORA-00312: Message 312 not found; No message file for product=RDBMS, facility=ORA; arguments: [5] [1] [/bases/oracle/oradata/ctwapgw/redo05.log]
ORA-322 signalled during: ALTER DATABASE OPEN...
Tue Dec 25 20:38:05 CST 2012
alter database open
Tue Dec 25 20:38:06 CST 2012
Errors in file /bases/oracle/admin/ctwapgw/bdump/ctwapgw_lgwr_20423.trc:
ORA-00322: Message 322 not found; No message file for product=RDBMS, facility=ORA; arguments: [5] [1]
ORA-00312: Message 312 not found; No message file for product=RDBMS, facility=ORA; arguments: [5] [1] [/bases/oracle/oradata/ctwapgw/redo05.log]
Tue Dec 25 20:38:06 CST 2012
Errors in file /bases/oracle/admin/ctwapgw/bdump/ctwapgw_lgwr_20423.trc:
ORA-00322: Message 322 not found; No message file for product=RDBMS, facility=ORA; arguments: [5] [1]
ORA-00312: Message 312 not found; No message file for product=RDBMS, facility=ORA; arguments: [5] [1] [/bases/oracle/oradata/ctwapgw/redo05.log]
Tue Dec 25 20:38:06 CST 2012
ORA-322 signalled during: alter database open..
......
另外一臺機器的oracle alert日誌也報ORA-00322、ORA-00312問題
查詢oracle error code:
$ oerr ora 00312
00312, 00000, "online log %s thread %s: '%s'"
// *Cause: This message reports the filename for details of another message.
// *Action: Other messages will accompany this message. See the
// associated messages for the appropriate action to take.
00312, 00000, "online log %s thread %s: '%s'"
// *Cause: This message reports the filename for details of another message.
// *Action: Other messages will accompany this message. See the
// associated messages for the appropriate action to take.
$ oerr ora 00322
00322, 00000, "log %s of thread %s is not current copy"
// *Cause: Check of log file header at database open found that an online
// log appears to be an incorrectly restored backup.
// *Action: Restore correct file or reset logs.
00322, 00000, "log %s of thread %s is not current copy"
// *Cause: Check of log file header at database open found that an online
// log appears to be an incorrectly restored backup.
// *Action: Restore correct file or reset logs.
清除報錯日誌/bases/oracle/oradata/ctwapgw/redo05.log的內容
SQL> ALTER DATABASE CLEAR LOGFILE '/bases/oracle/oradata/ctwapgw/redo05.log';
alert log檔案中部分日誌如下:
......
Tue Dec 25 22:45:50 CST 2012
alter database clear logfile '/bases/oracle/oradata/ctwapgw/redo05.log'
Tue Dec 25 22:45:50 CST 2012
Clearing online log 5 of thread 1 sequence number 27475
Completed: alter database clear logfile '/bases/oracle/oradata/ctwapgw/redo05.log'
Tue Dec 25 22:46:37 CST 2012
alter database open
Tue Dec 25 22:46:39 CST 2012
Thread 1 advanced to log sequence 27477 (thread open)
Thread 1 opened at log sequence 27477
Current log# 5 seq# 27477 mem# 0: /bases/oracle/oradata/ctwapgw/redo05.log
Successful open of redo thread 1
alter database clear logfile '/bases/oracle/oradata/ctwapgw/redo05.log'
Tue Dec 25 22:45:50 CST 2012
Clearing online log 5 of thread 1 sequence number 27475
Completed: alter database clear logfile '/bases/oracle/oradata/ctwapgw/redo05.log'
Tue Dec 25 22:46:37 CST 2012
alter database open
Tue Dec 25 22:46:39 CST 2012
Thread 1 advanced to log sequence 27477 (thread open)
Thread 1 opened at log sequence 27477
Current log# 5 seq# 27477 mem# 0: /bases/oracle/oradata/ctwapgw/redo05.log
Successful open of redo thread 1
......
開啟資料庫,執行alter database open:
SQL> alter database open;
開啟資料庫後,alert 日誌出現下面異常資訊:
......
Tue Dec 25 22:46:48 CST 2012
Errors in file /bases/oracle/admin/ctwapgw/bdump/ctwapgw_mmon_19553.trc:
ORA-00600: Message 600 not found; No message file for product=RDBMS, facility=ORA; arguments: [4194] [32] [28]
Flush retried for xcb 0x80b9e630, pmd 0x80eeedfc
Doing block recovery for file 17 block 807331
No block recovery was needed
Tue Dec 25 22:47:34 CST 2012
Thread 1 cannot allocate new log, sequence 27478
Private strand flush not complete
Current log# 5 seq# 27477 mem# 0: /bases/oracle/oradata/ctwapgw/redo05.log
Errors in file /bases/oracle/admin/ctwapgw/bdump/ctwapgw_mmon_19553.trc:
ORA-00600: Message 600 not found; No message file for product=RDBMS, facility=ORA; arguments: [4194] [32] [28]
Flush retried for xcb 0x80b9e630, pmd 0x80eeedfc
Doing block recovery for file 17 block 807331
No block recovery was needed
Tue Dec 25 22:47:34 CST 2012
Thread 1 cannot allocate new log, sequence 27478
Private strand flush not complete
Current log# 5 seq# 27477 mem# 0: /bases/oracle/oradata/ctwapgw/redo05.log
......
處理ORA-00600[4194]問題:
SQL> Create pfile='/tmp/corrupt.ora' from spfile ;
SQL> Shutdown immediate;
SQL> Shutdown immediate;
修改corrupt.ora,設定引數 Undo_managment=Manual
SQL> Startup mount pfile='/tmp/corrupt.ora';
SQL> Show parameter undo
NAME TYPE VALUE
------------------------------------ -------------------------------- ------------------------------
undo_management string MANUAL
undo_retention integer 900
undo_tablespace string UNDOTBS2
SQL> Alter database open;
------------------------------------ -------------------------------- ------------------------------
undo_management string MANUAL
undo_retention integer 900
undo_tablespace string UNDOTBS2
SQL> Alter database open;
SQL> Create rollback segment r01;
SQL> Create undo tablespace undotbs1 datafile '/bases/oracle/oradata/ctwapgw/undotbs1.dbf' size 10g;
引用metalink文章ID 281429.1
Please note :- You can delay the drop of the Old undo tablespace this is just to allow the block cleanout to happen for dead transaction.
So the below step can be issued after database has been up and running with new undo tablespace for couple of hours.
Also note if your database has been forced open(datafiles are not in sync and archivelogs missing ) using any unsupported method then please donot drop the Old undo.
So the below step can be issued after database has been up and running with new undo tablespace for couple of hours.
Also note if your database has been forced open(datafiles are not in sync and archivelogs missing ) using any unsupported method then please donot drop the Old undo.
此處刪除原來的undo表空間undotbs2
SQL> drop tablespace undotbs2 including contents and datafiles;
SQL> Shutdown immediate;
SQL> Startup nomount ; ---> Using spfile
SQL> Alter system set undo_tablespace=undotbs1 scope=spfile;
SQL> Shutdown immediate;
SQL> Startup;
檢查alert log 日誌檔案是否還存在ORA-600 [4194]的錯誤
期間,資料庫中job執行,報如下錯誤:
......
Errors in file /bases/oracle/admin/ctwapgw/bdump/ctwapgw_j000_16904.trc:
ORA-12012: error on auto execute of job 7
ORA-01552: cannot use system rollback segment for non-system tablespace 'WAP_USER_DATA_TABLESPACE'
ORA-06512: at "WAP_USER.PROC_LOG", line 23
ORA-06512: at "WAP_USER.WAPGW_IF1_02_RES", line 44
ORA-00942: table or view does not exist
ORA-06512: at line 1
......
後面alert log報如下錯誤:
......
Wed Dec 26 02:07:14 CST 2012
Errors in file /bases/oracle/admin/ctwapgw/bdump/ctwapgw_smon_22065.trc:
ORA-00600: Message 600 not found; No message file for product=RDBMS, facility=ORA; arguments: [13013] [5001] [474] [4198011] [108] [4198011] [17]
Wed Dec 26 02:07:14 CST 2012
Non-fatal internal error happenned while SMON was doing flushing of monitored table stats.
SMON encountered 1 out of maximum 100 non-fatal internal errors.
Wed Dec 26 02:07:15 CST 2012
Errors in file /bases/oracle/admin/ctwapgw/bdump/ctwapgw_smon_22065.trc:
ORA-00600: Message 600 not found; No message file for product=RDBMS, facility=ORA; arguments: [13013] [5001] [474] [4198011] [108] [4198011] [17]
Non-fatal internal error happenned while SMON was doing flushing of monitored table stats.
SMON encountered 2 out of maximum 100 non-fatal internal errors.
Wed Dec 26 02:07:17 CST 2012
Errors in file /bases/oracle/admin/ctwapgw/bdump/ctwapgw_smon_22065.trc:
ORA-00600: Message 600 not found; No message file for product=RDBMS, facility=ORA; arguments: [13013] [5001] [474] [4198011] [108] [4198011] [17]
Non-fatal internal error happenned while SMON was doing flushing of monitored table stats.
SMON encountered 3 out of maximum 100 non-fatal internal errors.
Wed Dec 26 02:07:18 CST 2012
Errors in file /bases/oracle/admin/ctwapgw/bdump/ctwapgw_smon_22065.trc:
ORA-00600: Message 600 not found; No message file for product=RDBMS, facility=ORA; arguments: [13013] [5001] [474] [4198011] [108] [4198011] [17]
Non-fatal internal error happenned while SMON was doing flushing of monitored table stats.
SMON encountered 4 out of maximum 100 non-fatal internal errors.
Wed Dec 26 02:07:20 CST 2012
Errors in file /bases/oracle/admin/ctwapgw/bdump/ctwapgw_smon_22065.trc:
ORA-00600: Message 600 not found; No message file for product=RDBMS, facility=ORA; arguments: [13013] [5001] [474] [4198011] [108] [4198011] [17]
Non-fatal internal error happenned while SMON was doing flushing of monitored table stats.
SMON encountered 5 out of maximum 100 non-fatal internal errors.
Wed Dec 26 02:07:30 CST 2012
Errors in file /bases/oracle/admin/ctwapgw/bdump/ctwapgw_smon_22065.trc:
ORA-00600: Message 600 not found; No message file for product=RDBMS, facility=ORA; arguments: [13013] [5001] [474] [4198011] [108] [4198011] [17]
Wed Dec 26 02:07:31 CST 2012
Non-fatal internal error happenned while SMON was doing flushing of monitored table stats.
SMON encountered 6 out of maximum 100 non-fatal internal errors.
Wed Dec 26 02:07:41 CST 2012
Errors in file /bases/oracle/admin/ctwapgw/bdump/ctwapgw_smon_22065.trc:
ORA-00600: Message 600 not found; No message file for product=RDBMS, facility=ORA; arguments: [13013] [5001] [474] [4198011] [108] [4198011] [17]
Wed Dec 26 02:07:41 CST 2012
Non-fatal internal error happenned while SMON was doing flushing of monitored table stats.
SMON encountered 7 out of maximum 100 non-fatal internal errors.
Wed Dec 26 02:07:51 CST 2012
Errors in file /bases/oracle/admin/ctwapgw/bdump/ctwapgw_smon_22065.trc:
ORA-00600: Message 600 not found; No message file for product=RDBMS, facility=ORA; arguments: [13013] [5001] [474] [4198011] [108] [4198011] [17]
Wed Dec 26 02:07:52 CST 2012
Non-fatal internal error happenned while SMON was doing flushing of monitored table stats.
SMON encountered 8 out of maximum 100 non-fatal internal errors.
Wed Dec 26 02:08:02 CST 2012
Errors in file /bases/oracle/admin/ctwapgw/bdump/ctwapgw_smon_22065.trc:
ORA-00600: Message 600 not found; No message file for product=RDBMS, facility=ORA; arguments: [13013] [5001] [474] [4198011] [108] [4198011] [17]
Wed Dec 26 02:08:02 CST 2012
Errors in file /bases/oracle/admin/ctwapgw/bdump/ctwapgw_pmon_22053.trc:
ORA-00474: Message 474 not found; No message file for product=RDBMS, facility=ORA
Wed Dec 26 02:08:02 CST 2012
PMON: terminating instance due to error 474
Instance terminated by PMON, pid = 22053
Errors in file /bases/oracle/admin/ctwapgw/bdump/ctwapgw_smon_22065.trc:
ORA-00600: Message 600 not found; No message file for product=RDBMS, facility=ORA; arguments: [13013] [5001] [474] [4198011] [108] [4198011] [17]
Wed Dec 26 02:07:14 CST 2012
Non-fatal internal error happenned while SMON was doing flushing of monitored table stats.
SMON encountered 1 out of maximum 100 non-fatal internal errors.
Wed Dec 26 02:07:15 CST 2012
Errors in file /bases/oracle/admin/ctwapgw/bdump/ctwapgw_smon_22065.trc:
ORA-00600: Message 600 not found; No message file for product=RDBMS, facility=ORA; arguments: [13013] [5001] [474] [4198011] [108] [4198011] [17]
Non-fatal internal error happenned while SMON was doing flushing of monitored table stats.
SMON encountered 2 out of maximum 100 non-fatal internal errors.
Wed Dec 26 02:07:17 CST 2012
Errors in file /bases/oracle/admin/ctwapgw/bdump/ctwapgw_smon_22065.trc:
ORA-00600: Message 600 not found; No message file for product=RDBMS, facility=ORA; arguments: [13013] [5001] [474] [4198011] [108] [4198011] [17]
Non-fatal internal error happenned while SMON was doing flushing of monitored table stats.
SMON encountered 3 out of maximum 100 non-fatal internal errors.
Wed Dec 26 02:07:18 CST 2012
Errors in file /bases/oracle/admin/ctwapgw/bdump/ctwapgw_smon_22065.trc:
ORA-00600: Message 600 not found; No message file for product=RDBMS, facility=ORA; arguments: [13013] [5001] [474] [4198011] [108] [4198011] [17]
Non-fatal internal error happenned while SMON was doing flushing of monitored table stats.
SMON encountered 4 out of maximum 100 non-fatal internal errors.
Wed Dec 26 02:07:20 CST 2012
Errors in file /bases/oracle/admin/ctwapgw/bdump/ctwapgw_smon_22065.trc:
ORA-00600: Message 600 not found; No message file for product=RDBMS, facility=ORA; arguments: [13013] [5001] [474] [4198011] [108] [4198011] [17]
Non-fatal internal error happenned while SMON was doing flushing of monitored table stats.
SMON encountered 5 out of maximum 100 non-fatal internal errors.
Wed Dec 26 02:07:30 CST 2012
Errors in file /bases/oracle/admin/ctwapgw/bdump/ctwapgw_smon_22065.trc:
ORA-00600: Message 600 not found; No message file for product=RDBMS, facility=ORA; arguments: [13013] [5001] [474] [4198011] [108] [4198011] [17]
Wed Dec 26 02:07:31 CST 2012
Non-fatal internal error happenned while SMON was doing flushing of monitored table stats.
SMON encountered 6 out of maximum 100 non-fatal internal errors.
Wed Dec 26 02:07:41 CST 2012
Errors in file /bases/oracle/admin/ctwapgw/bdump/ctwapgw_smon_22065.trc:
ORA-00600: Message 600 not found; No message file for product=RDBMS, facility=ORA; arguments: [13013] [5001] [474] [4198011] [108] [4198011] [17]
Wed Dec 26 02:07:41 CST 2012
Non-fatal internal error happenned while SMON was doing flushing of monitored table stats.
SMON encountered 7 out of maximum 100 non-fatal internal errors.
Wed Dec 26 02:07:51 CST 2012
Errors in file /bases/oracle/admin/ctwapgw/bdump/ctwapgw_smon_22065.trc:
ORA-00600: Message 600 not found; No message file for product=RDBMS, facility=ORA; arguments: [13013] [5001] [474] [4198011] [108] [4198011] [17]
Wed Dec 26 02:07:52 CST 2012
Non-fatal internal error happenned while SMON was doing flushing of monitored table stats.
SMON encountered 8 out of maximum 100 non-fatal internal errors.
Wed Dec 26 02:08:02 CST 2012
Errors in file /bases/oracle/admin/ctwapgw/bdump/ctwapgw_smon_22065.trc:
ORA-00600: Message 600 not found; No message file for product=RDBMS, facility=ORA; arguments: [13013] [5001] [474] [4198011] [108] [4198011] [17]
Wed Dec 26 02:08:02 CST 2012
Errors in file /bases/oracle/admin/ctwapgw/bdump/ctwapgw_pmon_22053.trc:
ORA-00474: Message 474 not found; No message file for product=RDBMS, facility=ORA
Wed Dec 26 02:08:02 CST 2012
PMON: terminating instance due to error 474
Instance terminated by PMON, pid = 22053
......
資料庫報ORA-600 [13013] [5001]問題,資料庫因為ORA-00474錯誤,PMON程式終止了Oracle例項
分析ORA-600 [13013] [5001][474] [4198011] [108] [4198011] [17]:
參考metalink文章ID 816784.1:
ORA-600 [13013] [a] [b] [c] [d] [e] [f]
This format relates to Oracle Server 8.0.3 to 10.1
Arg [a] Passcount
Arg [b] Data Object number
Arg [c] Tablespace Relative DBA of block containing the row to be updated
Arg [d] Row Slot number
Arg [e] Relative DBA of block being updated (should be same as [c])
Arg [f] Code
The Second argument would give the information about the data object id.
This would give information about the object involved.
SQL>Select object_name,object_type,owner from dba_objects where data_object_id=
Once the Object is identified run the following :
The below command check if the table has corruption or not .
SQL> Analyze table. validate structure online ;
This format relates to Oracle Server 8.0.3 to 10.1
Arg [a] Passcount
Arg [b] Data Object number
Arg [c] Tablespace Relative DBA of block containing the row to be updated
Arg [d] Row Slot number
Arg [e] Relative DBA of block being updated (should be same as [c])
Arg [f] Code
The Second argument would give the information about the data object id.
This would give information about the object involved.
SQL>Select object_name,object_type,owner from dba_objects where data_object_id=
Once the Object is identified run the following :
The below command check if the table has corruption or not .
SQL> Analyze table
相關文章
- ORA-00600 [13013], [5001]故障處理
- 【故障處理】ORA-600:[13013],[5001]故障處理
- oracle taf unknown 問題處理過程Oracle
- ORA-00600: internal error code, arguments: [13013], [5001], [267], [8389014]Error
- ORA-00600 [25027]問題處理
- 手工模擬Oracle資料塊邏輯訛誤引發,ORA-00600:[13013] [5001]一例Oracle
- rman建立catalog過程及問題處理
- Library cache pin問題的處理過程
- ORA-00600 [kcrfr_update_nab_2]處理過程CRF
- oracle處理SQL的過程OracleSQL
- ora-00600 :internal error code,arguments:[13013],[5001],[338],[12680125],[17]Error
- 一次線上問題處理過程記錄
- 一次Row Cache Lock問題處理過程
- Oracle CPU使用率過高問題處理Oracle
- 前端開發分析-聊聊過程跨域問題處理前端跨域
- 如何處理六西格瑪過程中遇到的問題?
- Mysql安裝過程問題總結及處理方法MySql
- Oracle 12c因bug導致ORA-04031問題處理過程Oracle
- Oracle資料庫 ORA-600 [13013]故障處理Oracle資料庫
- ora-00600 3020 問題分析處理
- ora-00600 [ktspgetmyb-1]問題的處理
- ORACLE 查詢語句處理過程(Oracle
- oracle系統表空間過大問題處理Oracle
- oracle bdump 下.trc檔案過大問題處理Oracle
- PHP5.2.4安裝中出現問題及處理過程PHP
- Oracle啟動問題處理Oracle
- Oracle壞塊問題處理Oracle
- 批處理作業排程問題
- crontab對oracle操作問題處理Oracle
- oracle SP2-問題處理Oracle
- 【VMware vCenter】VMware vCenter Server(VCSA) 5.5 版本證書過期問題處理過程。Server
- oracle 的DML命令的詳細處理過程Oracle
- 異常處理過程
- ORACLE問題處理十個指令碼Oracle指令碼
- Oracle delete 高水位線處理問題Oracledelete
- Oracle DataGuard FAL[client, ARC2]: Error 16191 connecting to 問題處理過程記錄OracleclientError
- ORACLE未繫結變數和硬解析過多問題處理Oracle變數
- 一次不完全恢復中途Kill rman後的問題處理+壞塊處理過程