2. 程式人生 > >ora-00600 內部錯誤程式碼 引數 4415

ora-00600 內部錯誤程式碼 引數 4415

阿新 • • 發佈：2018-11-14

分享一下我老師大神的人工智慧教程！零基礎，通俗易懂！http://blog.csdn.net/jiangjunshow

也歡迎大家轉載本篇文章。分享知識，造福人民，實現我們中華民族偉大復興！

                author：skate
time：2011/12/01

 

環境：
os：CentOS release 5.5
db: 11.2.0.2.0 - 64bit Production
physical dataguard

 

現象：只是報ora-00600: 內部錯誤程式碼, 引數: [4415]；資料庫還是可以正常提供服務

 

診斷：
這套oracle11g的DG已經執行一段時間了，在調整了些小問題後，目前執行還是比較穩定，今天
在primary庫收到報警，在alertlog裡的錯誤資訊如下：


Wed Nov 30 17:58:28 2011
Archived Log entry 1547 added for thread 1 sequence 7842 ID 0xa47b04d0 dest 1:
Wed Nov 30 18:21:33 2011
Media Recovery Waiting for thread 1 sequence 7844
Wed Nov 30 18:21:34 2011
RFS[5]: Selected log 7 for thread 1 sequence 7844 dbid -1535431216 branch 760042576
Recovery of Online Redo Log: Thread 1 Group 7 Seq 7844 Reading mem 0
  Mem# 0: /oracle/oradata/skatedb/sdbyredo07.log
Wed Nov 30 18:21:41 2011
Archived Log entry 1548 added for thread 1 sequence 7843 ID 0xa47b04d0 dest 1:
Wed Nov 30 18:28:20 2011
Errors in file /oracle/app/diag/rdbms/skate03/skatedb/trace/skatedb_ora_31048.trc  (incident=56617):
ora-00600: 內部錯誤程式碼, 引數: [4415], [], [], [], [], [], [], [], [], [], [], []
Incident details in: /oracle/app/diag/rdbms/skate03/skatedb/incident/incdir_56617/skatedb_ora_31048_i56617.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
System State dumped to trace file /oracle/app/diag/rdbms/skate03/skatedb/incident/incdir_56617/skatedb_ora_31048_i56617.trc
Wed Nov 30 18:29:19 2011
Dumping diagnostic data in directory=[cdmp_20111130182919], requested by (instance=1, osid=31048), summary=[incident=56617].
Wed Nov 30 18:29:25 2011
Errors in file /oracle/app/diag/rdbms/skate03/skatedb/trace/skatedb_ora_31048.trc  (incident=56618):
ora-00603: ORACLE 伺服器會話因致命錯誤而終止
ora-00600: 內部錯誤程式碼, 引數: [4415], [], [], [], [], [], [], [], [], [], [], []
Incident details in: /oracle/app/diag/rdbms/skate03/skatedb/incident/incdir_56618/skatedb_ora_31048_i56618.trc
Dumping diagnostic data in directory=[cdmp_20111130182926], requested by (instance=1, osid=31048), summary=[incident=56618].
opiodr aborting process unknown ospid (31048) as a result of ora-603
Wed Nov 30 18:29:29 2011
Sweep [inc][56618]: completed
Sweep [inc][56617]: completed
Sweep [inc2][56618]: completed
Sweep [inc2][56617]: completed
Wed Nov 30 18:44:01 2011
RFS[5]: Selected log 8 for thread 1 sequence 7845 dbid -1535431216 branch 760042576
Wed Nov 30 18:44:20 2011
Archived Log entry 1549 added for thread 1 sequence 7844 ID 0xa47b04d0 dest 1:
Wed Nov 30 18:44:20 2011
Media Recovery Waiting for thread 1 sequence 7845 (in transit)
Recovery of Online Redo Log: Thread 1 Group 8 Seq 7845 Reading mem 0
  Mem# 0: /oracle/oradata/skatedb/sdbyredo08.log
Wed Nov 30 19:08:17 2011

檢視trace檔案

[[email protected] ~]# more /oracle/app/diag/rdbms/skate03/skatedb/incident/incdir_56618/skatedb_ora_31048_i56618.trc
Dump file /oracle/app/diag/rdbms/skate03/skatedb/incident/incdir_56618/skatedb_ora_31048_i56618.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /oracle/app/oracle/product/11.2.0/db_1
System name:    Linux
Node name:      skatedb03
Release:        2.6.18-194.el5
Version:        #1 SMP Fri Apr 2 14:58:14 EDT 2010
Machine:        x86_64
Instance name: skatedb
Redo thread mounted by this instance: 1
Oracle process number: 77
Unix process pid: 31048, image:

[email protected]


*** 2011-11-30 18:29:25.696
*** SESSION ID:(1261.4657) 2011-11-30 18:29:25.696
*** CLIENT ID:() 2011-11-30 18:29:25.696
*** SERVICE NAME:(SYS$USERS) 2011-11-30 18:29:25.696
*** MODULE NAME:(PL/SQL Developer) 2011-11-30 18:29:25.696
*** ACTION NAME:(SQL Window - select * from STATS$DATABASE_INSTANCE select * from) 2011-11-30 18:29:25.696
 
Dump continued from file: /oracle/app/diag/rdbms/skate03/skatedb/trace/skatedb_ora_31048.trc
ORA-00603: ORACLE 伺服器會話因致命錯誤而終止
ORA-00600: 內部錯誤程式碼, 引數: [4415], [], [], [], [], [], [], [], [], [], [], []

========= Dump for incident 56618 (ORA 603) ========

*** 2011-11-30 18:29:25.697
dbkedDefDump(): Starting incident default dumps (flags=0x2, level=3, mask=0x0)
----- SQL Statement (None) -----
Current SQL information unavailable - no cursor.

----- Call Stack Trace -----
calling              call     entry                argument values in hex     
location             type     point                (? means dubious value)    
-------------------- -------- -------------------- ----------------------------
skdstdst()+36        call     kgdsdst()            000000000 ? 000000000 ?
                                                   7FFF58395F98 ? 000000001 ?
                                                   000000001 ? 000000002 ?
ksedst1()+98         call     skdstdst()           000000000 ? 000000000 ?
                                                   7FFF58395F98 ? 000000001 ?
                                                   000000000 ? 000000002 ?
ksedst()+34          call     ksedst1()            000000000 ? 000000001 ?
                                                   7FFF58395F98 ? 000000001 ?
                                                   000000000 ? 000000002 ?
dbkedDefDump()+2741  call     ksedst()             000000000 ? 000000001 ?
                                                   7FFF58395F98 ? 000000001 ?
                                                   000000000 ? 000000002 ?
ksedmp()+36          call     dbkedDefDump()       000000003 ? 000000002 ?
                                                   7FFF58395F98 ? 000000001 ?
                                                   000000000 ? 000000002 ?
ksfdmp()+64          call     ksedmp()             000000003 ? 000000002 ?
                                                   7FFF58395F98 ? 000000001 ?
                                                   000000000 ? 000000002 ?
dbgexPhaseII()+1764  call     ksfdmp()             000000003 ? 000000002 ?
                                                   7FFF58395F98 ? 000000001 ?
                                                   000000000 ? 000000002 ?
dbgexProcessError()  call     dbgexPhaseII()       2B8F76409718 ? 2B8F767AA6A8 ?
+2651                                              7FFF583A2310 ? 000000001 ?
                                                   000000000 ? 000000002 ?
dbgeExecuteForError  call     dbgexProcessError()  2B8F76409718 ? 2B8F767AA6A8 ?
()+83                                              000000001 ? 000000000 ?
                                                   100000000 ? 000000002 ?
dbgePostErrorKGE()+  call     dbgeExecuteForError  2B8F76409718 ? 2B8F767AA6A8 ?
2131                          ()                   000000001 ? 000000001 ?
                                                   000000000 ? 000000002 ?
dbkePostKGE_kgsf()+  call     dbgePostErrorKGE()   000000000 ? 2B8F768412A0 ?
63                                                 00000025B ? 2B8F767AA6A8 ?
                                                   100000000 ? 000000002 ?
kgeade()+351         call     dbkePostKGE_kgsf()   00B7D7EA0 ? 2B8F768412A0 ?
                                                   00000025B ? 2B8F767AA6A8 ?
                                                   100000000 ? 000000002 ?
kgefec()+171         call     kgeade()             00B7D7EA0 ? 00B7D8050 ?
                                                   2B8F768412A0 ? 00000025B ?
                                                   100000000 ? 000000002 ?
ktc_die()+124        call     kgefec()             00B7D7EA0 ? 2B8F768412A0 ?
                                                   000000000 ? 000000001 ?
                                                   100000000 ? 000000002 ?
k2send()+7723        call     ktc_die()            00B7D7EA0 ? 2B8F768412A0 ?
                                                   000000000 ? 000000001 ?
                                                   100000000 ? 000000002 ?
xctRollbackTxn()+52  call     k2send()             000000003 ? 2B8F768412A0 ?
6                                                  000000000 ? 000000000 ?
                                                   7FFF583A4050 ? 7FFF583A40B4 ?
kpoltxen()+158       call     xctRollbackTxn()     000000000 ? 009949E30 ?
                                                   00000062E ? 000000000 ?
                                                   7FFF583A4050 ? 7FFF583A40B4 ?
kpotxen()+2880       call     kpoltxen()           000000000 ? 009949E30 ?
                                                   00000062E ? 000000000 ?
                                                   7FFF583A4050 ? 7FFF583A40B4 ?
opiodr()+910         call     kpotxen()            000000000 ? 009949E30 ?
                                                   7FFF583A70E0 ? 000000000 ?
                                                   7FFF583A4050 ? 7FFF583A40B4 ?
ttcpip()+2289        call     opiodr()             000000068 ? 00000000C ?
                                                   7FFF583A70E0 ? 000000000 ?
                                                   0098AE420 ? 7FFF583A40B4 ?
opitsk()+1665        call     ttcpip()             00B7EDB10 ? 009247700 ?
                                                   7FFF583A70E0 ? 000000000 ?
                                                   7FFF583A6B40 ? 7FFF583A72D8 ?
opiino()+961         call     opitsk()             00B7EDB10 ? 000000001 ?
                                                   7FFF583A70E0 ? 000000000 ?
                                                   7FFF583A6B40 ? 7FFF583A72D8 ?
opiodr()+910         call     opiino()             00000003C ? 000000004 ?
                                                   7FFF583A8868 ? 000000000 ?
                                                   7FFF583A6B40 ? 7FFF583A72D8 ?
opidrv()+565         call     opiodr()             00000003C ? 000000004 ?
                                                   7FFF583A8868 ? 000000000 ?
                                                   0098ADD40 ? 7FFF583A72D8 ?
sou2o()+98           call     opidrv()             00000003C ? 000000004 ?
                                                   7FFF583A8868 ? 000000000 ?
                                                   0098ADD40 ? 7FFF583A72D8 ?
opimai_real()+128    call     sou2o()              7FFF583A8840 ? 00000003C ?
                                                   000000004 ? 7FFF583A8868 ?
                                                   0098ADD40 ? 7FFF583A72D8 ?
ssthrdmain()+252     call     opimai_real()        000000002 ? 7FFF583A8A30 ?
                                                   000000004 ? 7FFF583A8868 ?
                                                   0098ADD40 ? 7FFF583A72D8 ?
main()+196           call     ssthrdmain()         000000002 ? 7FFF583A8A30 ?
                                                   000000001 ? 000000000 ?
                                                   0098ADD40 ? 7FFF583A72D8 ?
__libc_start_main()  call     main()               000000002 ? 7FFF583A8BD8 ?
+244                                               000000001 ? 000000000 ?
                                                   0098ADD40 ? 7FFF583A72D8 ?
_start()+36          call     __libc_start_main()  000A078B8 ? 000000002 ?
                                                   7FFF583A8BC8 ? 000000000 ?
                                                   0098ADD40 ? 000000002 ?
........
.......

從trace檔案可以看到：
*** MODULE NAME:(PL/SQL Developer) 2011-11-30 18:29:25.696
*** ACTION NAME:(SQL Window - select * from STATS$DATABASE_INSTANCE select * from) 2011-11-30 18:29:25.696

這說明是人為操作的，執行了一個select查詢觸發了這個故障。

到metlink查詢，發現這個是bug 9531380，觸發這個bug，可能是如下原因：

A db-link created on the primary and is propageted to the standby.A synonym on the primay using the dblink is progated to the standby.Opening the standby in READ ONLY and selecting the synonym is fine.Using a commit afterwards fails with ORA-600 [4415]

翻譯：
在主庫通過dblink訪問standby庫的同義詞，並採用了commit的操作就會觸發這個bug。
而在trace的stack裡沒有看到commit相關操作，而是看到了函式xctRollbackTxn()，說明
有rollback操作，因為在read only的standby庫是不存在事務的，執行事務操作是有問題的。
從時間上看，那個時間是我在除錯程式，我查了遠端standby庫的同義詞，並rollback了。
從tracelog來看，rollback也會觸發這個600的錯誤。這個錯誤據我的故障來說，對庫
沒有什麼影響，如果是人為觸發的，可以不用管它。oracle在oracle11.2.0.3之後修復了這個bug。

 

 

-----end----

 

 

 

 

 

           

給我老師的人工智慧教程打call！http://blog.csdn.net/jiangjunshow

這裡寫圖片描述

相關推薦

ora-00600 內部錯誤程式碼 引數 4415

分享一下我老師大神的人工智慧教程！零基礎，通俗易懂！http://blog.csdn.net/jiangjunshow 也歡迎大家轉載本篇文章。分享知識，造福人民，實現我們中華民族偉大復興！        

關於Oracle資料庫的ORA-00600:內部錯誤程式碼, 引數: [kcratr_scan_lastbwr解決辦法

問題： 第一，最簡單的解決方式： 1、shutdown immediate; 2、startup mount; 3、alter database open; 第二，如果第一步沒解決，再進行下面的操作 1、shutdown immediate; 2、start

ORA-00600: 內部錯誤程式碼, 引數: [kcm_headroom_warn_1], [], [], [], [], [], [], [], [], [], [], []

SQL*Plus: Release 11.2.0.4.0 Production on 星期三 1月 1 08:53:48 2003 Copyright (c) 1982, 2013, Oracle. All rights reserved. idle> startupORACLE 例程已經啟動。

ORA-00600: 內部錯誤代碼, 參數: [kcm_headroom_warn_1], [], [], [], [], [], [], [], [], [], [], []

byte 12.1 change [] exception server buffers all lead SQL*Plus: Release 11.2.0.4.0 Production on 星期三 1月 1 08:53:48 2003 Copyright (c) 19

ORA-03113: 通訊通道的檔案結束 ORA-24324: 未初始化服務控制代碼 ORA-01041: 內部錯誤, hostdef 副檔名不存在

環境：win7+oracle11g情景：登入OEM失敗：檢查過oracle服務都是開啟狀態，回到命令列，嘗試重新啟動oracle，如下圖：又嘗試重新配置網路，測試不成功：報錯：.ORA-01034: ORACLE not availableORA-27101: sharedm

ORA——00600錯誤的原因是：（Oracle中對clob型別欄位的操作）

ORA——00600錯誤的原因是：（Oracle中對clob型別欄位的操作） 改正的程式碼如下： //3.2生成資料插入語句 （增加的方式） StringBuilder insertSql = new StringBuilder(“INSERT INTO “); insertSql.a

ORA-00600和ORA-08103錯誤處理

iamlaosong文 工作需要每月將總部下發的結算資料匯入到表中，然後進行統計清分。每個月的資料量很大，累計下來後資料量更大。用sqlldr匯入資料速度比較快。本次用sqlldr匯入8月結算資料後，進行統計時報錯：ORA-00600: internal error code, argume

ORA-06553: PLS-801: 內部錯誤 [56319]

在win2003 64bit還原一箇舊的IFS ERP資料庫，資料庫版本為10.2.0.3.0，使用普通賬號ifsapp賬號登記，出現如下錯誤 C:\Documents and Settings\Administrator>set oracle_sid=bjprod C:\Documen

Orcale 錯誤程式碼 ERROR:ORA-01033: ORACLE initialization or shutdown in progress，解決方案

初學Orcale發現這個軟體好讓人.....崩潰，在進行對錶空間進行操作時，顯示已存在表空間，我便直接在資料夾裡刪除那個表空間，沒想到Orcale就登不上去了，百度瞭解決方案。下面就給大家說一下這個解決方案。 造成原因的原因是沒用命令列刪除 1. 首先輸入SQLPLUS

一個SQL語句引發的ORA-00600錯誤排查

作者介紹 楊建榮，【DBAplus社群】聯合發起人。現就職於搜狐暢遊，Oracle ACE-A、YEP成員，超7年資料庫開發和運維經驗，擅長電信資料業務、資料庫遷移和效能調優。持Oracle 10G OCP，OCM，MySQL OCP認證，《Oracle DBA工作筆記》作者。 Merge

Oracle啟動時ORA-00600錯誤處理方法

oracle  startup時 報錯ORA-00600: 內部錯誤程式碼，引數: [kcratr1_lostwrt], [], [], [], [], [], [], [] 原因可能是非法關機或掉電造成,以下是出現的問題及解決方法: C:/Documents and Set

ora-00600

product oracle file Trace file /opt/oracle/app/oracle/diag/rdbms/suseora/suseora2/trace/suseora2_ora_36386.trcOracle Database 11g Enterprise Edition

ora-00600 to check

ner table rom als flag put exec str borde Hi , Let us know issue reproducibility executing following statement from command

ORA-00600: internal error code, arguments: [kkqtSetOp.1]

mit any face limit trace cpi tgs panel post 新數據庫從32升級到64位的11G 11 2 0 3 有條SQL 語句運行的時候會導致內部錯誤. 使用PL/SQL DEVELOPER 查詢該語句的運行機會 按F5鍵 就激發了這個O

SQL Server子查詢填充DataSet時報500內部錯誤的解決辦法

and 但是 itl bsp 出錯 子查詢 企業 sql 數據 運行環境為Visual Studio 2010，數據庫為SQL Server 2008。 執行下面SQL語句 SELECT SubsiteId, SubsiteTitle, count(CollectionI

ORA-00600: internal error code, arguments: [4193]問題解決

分析 mic iat int dbf 表空間 dia mil system 操作環境 SuSE+Oracle11gR2 問題現象 單板宕機自動重啟後，ORACLE運行不正常，主要表現如下： 1、執行shutdown immedate停止數據庫時，提示ORA-00

uwsgi部署django項目—報內部錯誤

reads 查看 cnblogs work soc pre -- 機器 執行命令 在django項目目錄下建立uwsgi.ini文件： [uwsgi] #使用nginx連接時使用 #socket=127.0.0.1:8080 #直接做web服務器使用 http=127.0.

數據庫壞塊觸發ora-00600和ora-07445

發現 http action 所在 ora 資源 mage 時間 重建表 上午10:03分收到資源同步庫的宕機告警，登陸數據庫核實數據庫確實異常，第一反應手動重啟庫，但依舊失敗。 回過頭查看數據庫告警日誌，發現大量的600和7445報錯 查看trace文

ORA-00600 kcratr_nab_less_than_odr 處理小計

客戶現場 聯機 arch enc 參數 rec mounted 嚴重 erro 今天由於客戶現場異常斷電，oracle數據庫又無法啟動了。遠程上去看看吧。 數據庫只能mount，已經無法啟動 SQL> select status from v$instance;

DBCA建庫出錯ORA-00600: internal error code, arguments

eno domain following ldo news bsp cat err idc 正常步驟安裝完成Oralce，通過dbca建庫，報錯如下圖所示： Oracle安裝日誌中報錯如下： [Thread-40] [ 1999-12-15 12:23:54.0