oracle10.2.0.5.0遭遇ORA-26773錯誤-Bug 5623403
昨天下午檢視測試庫發現stream的capture程式abort掉了,歸檔日誌有將近100個沒有應用了,檢視告警日誌發現如下錯誤:
ORA-26744: STREAMS capture process "UAT$CAP" does not support "MYNET_APP"."M_EDM_RESULT" because of the following reason:
ORA-26773: Invalid data type for column "malformed redo"
查了很多資料,居然是BUG,官方描述如下:
Bug No. 5623403
Filed 26-OCT-2006 Updated 15-NOV-2007
Product Oracle Server - Enterprise Edition Product Version 10.2.0.1.0
Platform. Microsoft Windows XP Platform. Version No Data
Database Version 10.2.0.1 Affects Platforms Generic
Severity Severe Loss of Service Status Development to Q/A
Base Bug N/A Fixed in Product Version 11.0
ORA-26744: STREAMS capture process "UAT$CAP" does not support "MYNET_APP"."M_EDM_RESULT" because of the following reason:
ORA-26773: Invalid data type for column "malformed redo"
查了很多資料,居然是BUG,官方描述如下:
Bug No. 5623403
Filed 26-OCT-2006 Updated 15-NOV-2007
Product Oracle Server - Enterprise Edition Product Version 10.2.0.1.0
Platform. Microsoft Windows XP Platform. Version No Data
Database Version 10.2.0.1 Affects Platforms Generic
Severity Severe Loss of Service Status Development to Q/A
Base Bug N/A Fixed in Product Version 11.0
Problem statement:
ORA-26773: INVALID DATA TYPE FOR COLUMN ''MALFORMED REDO'' IN STREAMS CAPTURE
納悶了,都升級到最終版本了,居然還會遇到這個BUG,太悲催了,想辦法解決吧:
首先想到的就是嘗試,從資料字典裡對這張表的例項化移除:
exec DBMS_CAPTURE_ADM.ABORT_TABLE_INSTANTIATION(table_name => 'mynet_app.M_EDM_RESULT');
執行完了之後,重新啟動capture程式,依然報錯,然後abort,
沒辦法,此路不通,再次嘗試對這張表指定規則:
BEGIN
DBMS_STREAMS_ADM.ADD_TABLE_RULES (
table_name => 'MYNET_APP.M_EDM_RESULT',
streams_type => 'capture',
streams_name => 'UAT$CAP',
queue_name => 'STRMADMIN.UAT$CAPQ',
include_dml => true,
include_ddl => true,
source_database => 'UAT',
inclusion_rule => false ); --specifies the negative rule set
END;
/
之後重新啟動capture程式,歸檔日誌終於開始應用了,沒多久報錯ORA-600:
Thu Nov 24 15:32:05 CST 2011
Errors in file /oracle/admin/mydev/bdump/mydev_q003_18164.trc:
ORA-00600: internal error code, arguments: [kwqbdrcp101], [], [], [], [], [], [], []
索性直接重啟target資料庫,起來之後檢視相應的propagation、capture和apply程式都是enabled狀態,但是告警日誌裡沒相關應用日誌的資訊,等吧,沒2分鐘,歸檔再次開始應用了,之後就沒有再報錯:
LOGMINER: End mining logfile: /arch/arch1_6226_716985918.arc
Thu Nov 24 15:32:42 CST 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 6227, /arch/arch1_6227_716985918.arc
Thu Nov 24 15:32:45 CST 2011
LOGMINER: End mining logfile: /arch/arch1_6227_716985918.arc
Thu Nov 24 15:32:45 CST 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 6228, /arch/arch1_6228_716985918.arc
Thu Nov 24 15:32:46 CST 2011
LOGMINER: End mining logfile: /arch/arch1_6228_716985918.arc
Thu Nov 24 15:32:46 CST 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 6229, /arch/arch1_6229_716985918.arc
Thu Nov 24 15:32:51 CST 2011
LOGMINER: End mining logfile: /arch/arch1_6229_716985918.arc
Thu Nov 24 15:32:51 CST 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 6230, /arch/arch1_6230_716985918.arc
Thu Nov 24 15:33:03 CST 2011
LOGMINER: End mining logfile: /arch/arch1_6230_716985918.arc
Thu Nov 24 15:33:03 CST 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 6231, /arch/arch1_6231_716985918.arc
Thu Nov 24 15:33:05 CST 2011
LOGMINER: End mining logfile: /arch/arch1_6231_716985918.arc
Thu Nov 24 15:33:05 CST 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 6232, /arch/arch1_6232_716985918.arc
exec DBMS_CAPTURE_ADM.ABORT_TABLE_INSTANTIATION(table_name => 'mynet_app.M_EDM_RESULT');
執行完了之後,重新啟動capture程式,依然報錯,然後abort,
沒辦法,此路不通,再次嘗試對這張表指定規則:
BEGIN
DBMS_STREAMS_ADM.ADD_TABLE_RULES (
table_name => 'MYNET_APP.M_EDM_RESULT',
streams_type => 'capture',
streams_name => 'UAT$CAP',
queue_name => 'STRMADMIN.UAT$CAPQ',
include_dml => true,
include_ddl => true,
source_database => 'UAT',
inclusion_rule => false ); --specifies the negative rule set
END;
/
之後重新啟動capture程式,歸檔日誌終於開始應用了,沒多久報錯ORA-600:
Thu Nov 24 15:32:05 CST 2011
Errors in file /oracle/admin/mydev/bdump/mydev_q003_18164.trc:
ORA-00600: internal error code, arguments: [kwqbdrcp101], [], [], [], [], [], [], []
索性直接重啟target資料庫,起來之後檢視相應的propagation、capture和apply程式都是enabled狀態,但是告警日誌裡沒相關應用日誌的資訊,等吧,沒2分鐘,歸檔再次開始應用了,之後就沒有再報錯:
LOGMINER: End mining logfile: /arch/arch1_6226_716985918.arc
Thu Nov 24 15:32:42 CST 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 6227, /arch/arch1_6227_716985918.arc
Thu Nov 24 15:32:45 CST 2011
LOGMINER: End mining logfile: /arch/arch1_6227_716985918.arc
Thu Nov 24 15:32:45 CST 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 6228, /arch/arch1_6228_716985918.arc
Thu Nov 24 15:32:46 CST 2011
LOGMINER: End mining logfile: /arch/arch1_6228_716985918.arc
Thu Nov 24 15:32:46 CST 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 6229, /arch/arch1_6229_716985918.arc
Thu Nov 24 15:32:51 CST 2011
LOGMINER: End mining logfile: /arch/arch1_6229_716985918.arc
Thu Nov 24 15:32:51 CST 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 6230, /arch/arch1_6230_716985918.arc
Thu Nov 24 15:33:03 CST 2011
LOGMINER: End mining logfile: /arch/arch1_6230_716985918.arc
Thu Nov 24 15:33:03 CST 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 6231, /arch/arch1_6231_716985918.arc
Thu Nov 24 15:33:05 CST 2011
LOGMINER: End mining logfile: /arch/arch1_6231_716985918.arc
Thu Nov 24 15:33:05 CST 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 6232, /arch/arch1_6232_716985918.arc
後記:一直想不通oracle版本都升級到最終版本了,居然還會遇到這個BUG,看來stream技術還不是很穩定。
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/25618347/viewspace-711956/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 遭遇BUG 4483368出現ORA-19693錯誤後的處理辦法
- app:processDebugManifest 錯誤APP
- IOS 配置錯誤的BUGiOS
- mysql xtrabackup 遭遇嚴重bugMySql
- oracle 10.2.4 遭遇bug 當機Oracle
- 32 位 oracle 安裝到 64 位os ,遭遇的錯誤Oracle
- 遭遇mysql 5.6.10 BUG 一例MySql
- AIX 5.1平臺下遭遇TNS-12531錯誤AI
- [記錄]在高光譜影像分類中遭遇的愚蠢錯誤
- [BUG反饋]獨立模型-刪除錯誤模型除錯
- android Studio遇到transformClassesWithDexForDebug錯誤AndroidORM
- 【Bug】vs生成失敗但沒提示錯誤
- MySQL 5.6 遭遇 OS bug INNODB MONITOR OUTPUT 事件MySql事件
- delete操作時遭遇ora-600 bug[kntgslm]delete
- CS0234 錯誤,奇葩bug,解決方案
- RMAN遠端連線目標資料庫遭遇RMAN-06429錯誤資料庫
- 通過NFS方式來保留rac歸檔日誌遭遇ORA-27054錯誤NFS
- AIX RAC9i 節點2啟動時遭遇到7445錯誤AI
- DEBUG : Eclipse Debug 時出現 Cannot connect to VM select failed錯誤EclipseAI
- 升級Grid Infrastructure到10.2.0.2 遭遇bug 9413827ASTStruct
- 遭遇ORA-600 [kgscLogOff-notempty] bugGo
- [ORACLE BUG]查詢結果錯誤--臨時表並行Oracle並行
- Vue.js@2.6.10更新內建錯誤處機制,Fundebug同步支援相應錯誤監控Vue.js
- 遭遇Bug 5766310 Bad join cardinality is in the presence of histogramsHistogram
- DBMS_STATS.GATHER_SCHEMA_STATS執行過程中遭遇ORA-01476錯誤
- 由9itemp表空間遭遇ORA-01652錯誤蔓延開來 zt
- cls_oracle_logs.sh指令碼遭遇TNS-12508錯誤淺析Oracle指令碼
- [BUG反饋]登陸沒反應,審查元素提示錯誤
- [BUG反饋]下載開發版安裝出現錯誤
- 【BUG系列】transformClassesWithJarMergingForRelease BuildConfig.class 合併錯誤ORMJARUI
- 12.2.0.1bug導致的Failed to register in OCRLOCAL group.錯誤AI
- 藉助SpotBugs將程式錯誤扼殺在搖籃中
- Debug: 樣式規則、元素選擇器 錯誤嵌用
- [BUG反饋]1.1版本錯誤,新建模型,無法使用,出現SQLSTATE[23000]:錯誤模型SQL
- 【expdp】資料泵備份遭遇ORA-00600: internal error code, arguments: [17020]錯誤Error
- 資料庫遭遇 ora-07445 + ora-00108 錯誤 收藏此主題資料庫
- 遭遇ora-600 [qkacon:FJswrwo], [3] oracle 10.2.0.4 bugJSOracle
- [BUG反饋]U方法linux下錯誤連結。求指導Linux