请问，重建过控制文件,现在导致数据库2小时内必挂一次！
请问，重建过控制文件，现在导致数据库一段时间就自动挂掉？这个是什么原因？
报ora-00600[kdsgrpl],但是没有坏块
oracle11g 32位，操作系统64位的
报ora-00600[kdsgrpl],但是没有坏块
oracle11g 32位，操作系统64位的
7同行回答
Type B - Defect Fixed in Product Version
Severity 3 - Minimal Loss of Service Product Version 11.2.0.3
Status 32 - Not a Bug. To Filer Platform 226 - Linux x86-64
Created 11-Sep-2013 Platform Version RED HAT ENTERPRISE LINUX 6
Updated 17-Oct-2013 Base Bug N/A
Database Version 11.2.0.3 Affects Platforms Generic
Product Source Oracle Knowledge, Patches, Service Requests and Bugs related to this bug
Related Products
Line Oracle Database Products Family Oracle Database Suite
Area Application Development Product 11 - PL/SQL
Hdr: 17440418 11.2.0.3 PLSQL 11.2.0.3 RUNTIME PRODID-11 PORTID-226
Abstract: ORA-700: SOFT INTERNAL ERROR, ARGUMENTS: [KGEREV1], [600], [600], [700]
*** VSTEFANC 09/11/13 01:58 am ***
@ SR Number: SR:3-7620397301
@
BUG TYPE CHOSEN
===============
Code
== Component: RDBMS ==
======================
DETAILED PROBLEM DESCRIPTION
============================
ORA-700: soft internal error, arguments: [kgerev1], [600], [600], [700]
folloed by :
ORA-600: internal error code, arguments: [], [], [], [], [], [], [], [],
[], [], [], []
@ EXPLAIN WHY YOU BELIEVE THIS TO BE A PRODUCT DEFECT
@ ===================================================
@ ora-600 encountered
@
DIAGNOSTIC ANALYSIS
===================
*** 2013-08-19 12:45:14.642
*** SESSION ID:(644.12075) 2013-08-19 12:45:14.642
*** CLIENT ID:() 2013-08-19 12:45:14.642
*** SERVICE NAME:(SYS$USERS) 2013-08-19 12:45:14.642
*** MODULE NAME:(DBMS_SCHEDULER) 2013-08-19 12:45:14.642
*** ACTION NAME:(MMD_OCIS_REQ_REQUEST_3) 2013-08-19 12:45:14.642
DDE: Problem Key 'ORA-700 [kgerev1]' was flood controlled (0x2) (incident:
104529)
ORA-700: soft internal error, arguments: [kgerev1], [600], [600], [700],
[], [], [], [], [], [], [], []
DDE: Problem Key 'ORA-600' was flood controlled (0x2) (incident: 104530)
ORA-600: internal error code, arguments: [], [], [], [], [], [], [], [],
[], [], [], []
*** 2013-08-19 12:45:14.700
dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x0, level=3,
mask=0x0)
----- Error Stack Dump -----
ORA-600: internal error code, arguments: [], [], [], [], [], [], [], [],
[], [], [], []
----- Current SQL Statement for this session (sql_id=23wjujqgfm4ft) -----
DECLARE job BINARY_INTEGER := :job; next_date TIMESTAMP WITH TIME ZONE :=
:mydate; broken BOOLEAN := FALSE; job_name VARCHAR2(30) := :job_name;
job_subname VARCHAR2(30) := :job_subname; job_owner VARCHAR2(30) :=
:job_owner; job_start TIMESTAMP WITH TIME ZONE := :job_start;
job_scheduled_start TIMESTAMP WITH TIME ZONE := :job_scheduled_start;
window_start TIMESTAMP WITH TIME ZONE := :window_start; window_end TIMESTAMP
WITH TIME ZONE := :window_end; chain_id VARCHAR2(14) := :chainid;
credential_owner varchar2(30) := :credown; credential_name varchar2(30) :=
:crednam; destination_owner varchar2(30) := :destown; destination_name
varchar2(30) := :destnam; job_dest_id varchar2(14) := :jdestid; log_id
number := :log_id; BEGIN DECLARE
RetVal NUMBER;
PO_MESSAGE_GROUP_ID VARCHAR2(200);
BEGIN
PO_MESSAGE_GROUP_ID := NULL;
RetVal :=
MMD_OCIS_SET_ROUTERS.EXECUTE_SET_ITEMS_TO_ROUTER
(PO_MESSAGE_GROUP_ID);
END; :mydate := next_date; IF broken THEN :b :=
1; ELSE :b := 0; END IF; END;
----- PL/SQL Stack -----
----- PL/SQL Call Stack -----
object line object
handle number name
0x753722e1e0 1829 package body MSTMFG.MMD_SETROUTER_API
0x753722e1e0 618 package body MSTMFG.MMD_SETROUTER_API
0x35d84393a0 210 package body MSTMFG.MMD_OCIS_SET_ROUTERS
0x35d84393a0 317 package body MSTMFG.MMD_OCIS_SET_ROUTERS
0x32781d0048 6 anonymous block
however if the following statement is executed:
DECLARE
RetVal NUMBER;
PO_MESSAGE_GROUP_ID VARCHAR2(200);
BEGIN
PO_MESSAGE_GROUP_ID := NULL;
RetVal := MMD_OCIS_SET_ROUTERS.EXECUTE_SET_ITEMS_TO_ROUTER
(PO_MESSAGE_GROUP_ID);
END;
it works fine
WORKAROUND?
===========
No
TECHNICAL IMPACT
================
job does not finish properly
RELATED ISSUES (bugs, forums, RFAs)
===================================
na
HOW OFTEN DOES THE ISSUE REPRODUCE AT CUSTOMER SITE?
====================================================
Intermittent
DOES THE ISSUE REPRODUCE INTERNALLY?
====================================
No
IS A TESTCASE AVAILABLE?
========================
No
@ DID THIS WORK PREVIOUSLY?
@ =========================
@ Yes
@
@ WHAT WAS THE VERSION AND/OR PATCHSET RELEASE WHERE IT WORKED?
@ =============================================================
@ no
@
@ WHAT HAS CHANGED SINCE THE TIME THAT IT WORKED?
@ ===============================================
@ no
@
@ DID YOU TEST THIS ON THE LATEST RELEASE/PATCHSET?
@ =================================================
@ Yes
@
@ DOES THE ISSUE STILL REPRODUCE IN THE LATEST RELEASE/PATCHSET?
@ ==============================================================
@ Yes
@
@ PROVIDE THE COMPLETE VERSION(S) YOU HAVE TESTED THIS UNDER AND THE RESULTS
@ FOR EACH.
@ ============================================================================
@ na
@
@ STACK TRACE/FILE Information
@ ============================
@ skdstdst <- ksedst1 <- ksedst <- dbkedDefDump <- ksedmp
@ <- dbkdaKsdActDriver <- dbgdaExecuteAction <- dbgdaRunAction <-
@ dbgdRunActions <- dbgdProcessEventAct
@ <- ions <- dbgdChkEventKgErr <- dbkdChkEventRdbmsEr <- ksfpec <-
@ dbgePostErrorKGE
@ <- 1129 <- dbkePostKGE_kgsf <- kgeade <- kgerelv <- kgerev
@ <- kgerec0 <- pfrrexc_record_excp <- pfrexc <- pfrrun <- plsql_run
@ <- peicnt <- kkxexe <- opiexe <- kpoal8 <- opiodr
@ <- kpoodr <- upirtrc <- kpurcsc <- kpuexec <- OCIStmtExecute
@ <- jslvec_execcb <- jslvswu <- jslve_execute0 <- jslve_execute
@ <- rpiswu2
@ <- kkjex1e <- kkjsexe <- kkjrdp <- opirip <- opidrv
@ <- sou2o <- opimai_real <- ssthrdmain <- main <-
@ libc_start_main
@
Link to IPS Package:
====================
not avalaible
@ P1 Defect?
@ ==========
@ No
@
@ *** (CHG: SR: 3-7620397301 (ORION) Attached)
@ *** VSTEFANC 09/11/13 01:58 am *** (Ref. Added: PREBUG(PreBug Ref.) - 1744...)
*** VSTEFANC 09/11/13 02:01 am ***
@ Attachment:msmmdpep2_j002_20972.trc:trace file
*** VSTEFANC 09/11/13 02:38 am *** (CHG: Sta->16)
@ *** VVISHWES 09/11/13 02:47 am *** (CHG: Support Contact->VSTEFANC->VVISHWES)
*** VVISHWES 09/11/13 02:47 am *** (CHG: Asg->VVISHWES)
*** VSTEFANC 09/13/13 02:26 am ***
@ customer is asking if there is any update as he encounters lots of errors
*** VVISHWES 09/16/13 12:04 am *** (CHG: Sta->10 Asg->PLSREP Prod->11 Comp->PLSQL)
*** VVISHWES 09/16/13 12:04 am ***
@ this is the same issue as addressed in bug13580189 for the same customer.
@ please provide a testcase, as had been requested in the previously opened bug.
*** YSAEZ 10/14/13 02:19 am *** (CHG: Sta->16)
*** YSAEZ 10/14/13 02:19 am ***
@ No testcase is possible. The issue happens randomly and the error is not
@ reproduced when the plsql block to create the job, or the task included in
@ the job are executed manually.
@ .
@ The customer is able to apply a diagnostic patch to progress on the issue.
*** VVISHWES 10/16/13 02:00 am *** (CHG: Sta->10)
*** VVISHWES 10/16/13 02:00 am ***
@ upload the code for MMD_SETROUTER_API and MMD_OCIS_SET_ROUTERS.
@ Were there any changes done, after which the issue started occurring.
*** YSAEZ 10/16/13 05:15 am ***
@ ISS:3-7620397301:pkgs.rar:packages
*** YSAEZ 10/16/13 05:17 am *** (CHG: Sta->16)
*** YSAEZ 10/16/13 05:17 am ***
@ Attached the packages. The customer says that there was not any change at
@ aapplication level or database level before the errors started
@ *** SCASTLED 10/17/13 03:48 am *** (CHG: Support Contact->VVISHWES->SCASTLED)
*** SCASTLED 10/17/13 03:48 am *** (CHG: Asg->SCASTLED SubComp->RUNTIME)
*** SCASTLED 10/17/13 07:28 am *** (CHG: Sta->32)
*** SCASTLED 10/17/13 07:28 am ***
@ EMEA Languages BDE:
You get an empty (ie no arguments) ora-600 with the ora-700 above when
you explicitly raise an ora-600 from plsql. For instance running:
DECLARE
sys_exc EXCEPTION;
PRAGMA EXCEPTION_INIT (sys_exc, -600);
BEGIN
RAISE sys_exc;
END;
/
gives:
DECLARE
*
ERROR at line 1:
ORA-600: internal error code, arguments: [], [], [], [], [], [], [], [],
[],
[], [], []
ORA-6512: at line 5
and creates a trace containing:
ORA-700: soft internal error, arguments: [kgerev1], [600], [600],
[700], [], [], [], [], [], [], [], []
with a very similar stack to here.
Looking at the code that's been uploaded. The error is raised from the call
to MMD_OCIS_SET_ROUTERS.EXECUTE_SET_ITEMS_TO_ROUTER in the failing plsql
block.
Line 317 of package MMD_OCIS_SET_ROUTERS is a call to
MMD_OCIS_SET_ROUTERS.set_items_to_router from a cursor for loop.
Line 210 is a call to mmd_setrouter_api.mmdsetrouters_3 whilst looping
through entries of a collection.
Line 618 of package mmd_setrouter_api looking at the uploaded code is an ELSE
from parse_string_to_array which is clearly not correct so this does not
appear to be the code they are running in the d/b.
There are two overloaded copies of function mmdsetrouters_3. The first
starts at line 470 and ends at line 546; the second starts at line 1323 and
ends at line 1860.
Line 1829 in this copy is "WHEN err_derive_member_reasons" in the second
mmdsetrouters_3 which is called from the first but clearly not right again.
There are a number of raise calls in this package. Pragma excpetion_init is
declared for the following errors in the package body:
-54, -100, -200, -300, -600, -700, -800, -900, -901, -1000, -1001, -1002
Of these only -54 is being used for the corresponding oracle error case of
resource busy. The rest are being used as user defined errors even
though all but 500 is a predefined oracle error code so oracle will check and
handle accordingly.
Even though this isn't quite the right copy of the package we can see that
the code is incorrectly raising oracle error codes. When one of these is an
internal error such as 600 or 700 a corresponding trace file is created. For
user defined errors they should be in the 20,000 range.
The generation of trace files is therefore expected behaviour.
If the customer needs to know why the app is now hitting the places where it
wants to raise 600 or 700 when previously it didn't then this needs
investigating by Apps and Apps should fix this code to only raise 20K range
errors for user defined ones.
Since there is no bug from the d/b side, closing this at 32.
你核对下是否是该bug？
另外，你的oracle11g 32位，操作系统64位的 这个做法本身就有问题
这样的问题，如果不能解决，可以私下联系我收起
Severity 3 - Minimal Loss of Service Product Version 11.2.0.3
Status 32 - Not a Bug. To Filer Platform 226 - Linux x86-64
Created 11-Sep-2013 Platform Version RED HAT ENTERPRISE LINUX 6
Updated 17-Oct-2013 Base Bug N/A
Database Version 11.2.0.3 Affects Platforms Generic
Product Source Oracle Knowledge, Patches, Service Requests and Bugs related to this bug
Related Products
Line Oracle Database Products Family Oracle Database Suite
Area Application Development Product 11 - PL/SQL
Hdr: 17440418 11.2.0.3 PLSQL 11.2.0.3 RUNTIME PRODID-11 PORTID-226
Abstract: ORA-700: SOFT INTERNAL ERROR, ARGUMENTS: [KGEREV1], [600], [600], [700]
*** VSTEFANC 09/11/13 01:58 am ***
@ SR Number: SR:3-7620397301
@
BUG TYPE CHOSEN
===============
Code
== Component: RDBMS ==
======================
DETAILED PROBLEM DESCRIPTION
============================
ORA-700: soft internal error, arguments: [kgerev1], [600], [600], [700]
folloed by :
ORA-600: internal error code, arguments: [], [], [], [], [], [], [], [],
[], [], [], []
@ EXPLAIN WHY YOU BELIEVE THIS TO BE A PRODUCT DEFECT
@ ===================================================
@ ora-600 encountered
@
DIAGNOSTIC ANALYSIS
===================
*** 2013-08-19 12:45:14.642
*** SESSION ID:(644.12075) 2013-08-19 12:45:14.642
*** CLIENT ID:() 2013-08-19 12:45:14.642
*** SERVICE NAME:(SYS$USERS) 2013-08-19 12:45:14.642
*** MODULE NAME:(DBMS_SCHEDULER) 2013-08-19 12:45:14.642
*** ACTION NAME:(MMD_OCIS_REQ_REQUEST_3) 2013-08-19 12:45:14.642
DDE: Problem Key 'ORA-700 [kgerev1]' was flood controlled (0x2) (incident:
104529)
ORA-700: soft internal error, arguments: [kgerev1], [600], [600], [700],
[], [], [], [], [], [], [], []
DDE: Problem Key 'ORA-600' was flood controlled (0x2) (incident: 104530)
ORA-600: internal error code, arguments: [], [], [], [], [], [], [], [],
[], [], [], []
*** 2013-08-19 12:45:14.700
dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x0, level=3,
mask=0x0)
----- Error Stack Dump -----
ORA-600: internal error code, arguments: [], [], [], [], [], [], [], [],
[], [], [], []
----- Current SQL Statement for this session (sql_id=23wjujqgfm4ft) -----
DECLARE job BINARY_INTEGER := :job; next_date TIMESTAMP WITH TIME ZONE :=
:mydate; broken BOOLEAN := FALSE; job_name VARCHAR2(30) := :job_name;
job_subname VARCHAR2(30) := :job_subname; job_owner VARCHAR2(30) :=
:job_owner; job_start TIMESTAMP WITH TIME ZONE := :job_start;
job_scheduled_start TIMESTAMP WITH TIME ZONE := :job_scheduled_start;
window_start TIMESTAMP WITH TIME ZONE := :window_start; window_end TIMESTAMP
WITH TIME ZONE := :window_end; chain_id VARCHAR2(14) := :chainid;
credential_owner varchar2(30) := :credown; credential_name varchar2(30) :=
:crednam; destination_owner varchar2(30) := :destown; destination_name
varchar2(30) := :destnam; job_dest_id varchar2(14) := :jdestid; log_id
number := :log_id; BEGIN DECLARE
RetVal NUMBER;
PO_MESSAGE_GROUP_ID VARCHAR2(200);
BEGIN
PO_MESSAGE_GROUP_ID := NULL;
RetVal :=
MMD_OCIS_SET_ROUTERS.EXECUTE_SET_ITEMS_TO_ROUTER
(PO_MESSAGE_GROUP_ID);
END; :mydate := next_date; IF broken THEN :b :=
1; ELSE :b := 0; END IF; END;
----- PL/SQL Stack -----
----- PL/SQL Call Stack -----
object line object
handle number name
0x753722e1e0 1829 package body MSTMFG.MMD_SETROUTER_API
0x753722e1e0 618 package body MSTMFG.MMD_SETROUTER_API
0x35d84393a0 210 package body MSTMFG.MMD_OCIS_SET_ROUTERS
0x35d84393a0 317 package body MSTMFG.MMD_OCIS_SET_ROUTERS
0x32781d0048 6 anonymous block
however if the following statement is executed:
DECLARE
RetVal NUMBER;
PO_MESSAGE_GROUP_ID VARCHAR2(200);
BEGIN
PO_MESSAGE_GROUP_ID := NULL;
RetVal := MMD_OCIS_SET_ROUTERS.EXECUTE_SET_ITEMS_TO_ROUTER
(PO_MESSAGE_GROUP_ID);
END;
it works fine
WORKAROUND?
===========
No
TECHNICAL IMPACT
================
job does not finish properly
RELATED ISSUES (bugs, forums, RFAs)
===================================
na
HOW OFTEN DOES THE ISSUE REPRODUCE AT CUSTOMER SITE?
====================================================
Intermittent
DOES THE ISSUE REPRODUCE INTERNALLY?
====================================
No
IS A TESTCASE AVAILABLE?
========================
No
@ DID THIS WORK PREVIOUSLY?
@ =========================
@ Yes
@
@ WHAT WAS THE VERSION AND/OR PATCHSET RELEASE WHERE IT WORKED?
@ =============================================================
@ no
@
@ WHAT HAS CHANGED SINCE THE TIME THAT IT WORKED?
@ ===============================================
@ no
@
@ DID YOU TEST THIS ON THE LATEST RELEASE/PATCHSET?
@ =================================================
@ Yes
@
@ DOES THE ISSUE STILL REPRODUCE IN THE LATEST RELEASE/PATCHSET?
@ ==============================================================
@ Yes
@
@ PROVIDE THE COMPLETE VERSION(S) YOU HAVE TESTED THIS UNDER AND THE RESULTS
@ FOR EACH.
@ ============================================================================
@ na
@
@ STACK TRACE/FILE Information
@ ============================
@ skdstdst <- ksedst1 <- ksedst <- dbkedDefDump <- ksedmp
@ <- dbkdaKsdActDriver <- dbgdaExecuteAction <- dbgdaRunAction <-
@ dbgdRunActions <- dbgdProcessEventAct
@ <- ions <- dbgdChkEventKgErr <- dbkdChkEventRdbmsEr <- ksfpec <-
@ dbgePostErrorKGE
@ <- 1129 <- dbkePostKGE_kgsf <- kgeade <- kgerelv <- kgerev
@ <- kgerec0 <- pfrrexc_record_excp <- pfrexc <- pfrrun <- plsql_run
@ <- peicnt <- kkxexe <- opiexe <- kpoal8 <- opiodr
@ <- kpoodr <- upirtrc <- kpurcsc <- kpuexec <- OCIStmtExecute
@ <- jslvec_execcb <- jslvswu <- jslve_execute0 <- jslve_execute
@ <- rpiswu2
@ <- kkjex1e <- kkjsexe <- kkjrdp <- opirip <- opidrv
@ <- sou2o <- opimai_real <- ssthrdmain <- main <-
@ libc_start_main
@
Link to IPS Package:
====================
not avalaible
@ P1 Defect?
@ ==========
@ No
@
@ *** (CHG: SR: 3-7620397301 (ORION) Attached)
@ *** VSTEFANC 09/11/13 01:58 am *** (Ref. Added: PREBUG(PreBug Ref.) - 1744...)
*** VSTEFANC 09/11/13 02:01 am ***
@ Attachment:msmmdpep2_j002_20972.trc:trace file
*** VSTEFANC 09/11/13 02:38 am *** (CHG: Sta->16)
@ *** VVISHWES 09/11/13 02:47 am *** (CHG: Support Contact->VSTEFANC->VVISHWES)
*** VVISHWES 09/11/13 02:47 am *** (CHG: Asg->VVISHWES)
*** VSTEFANC 09/13/13 02:26 am ***
@ customer is asking if there is any update as he encounters lots of errors
*** VVISHWES 09/16/13 12:04 am *** (CHG: Sta->10 Asg->PLSREP Prod->11 Comp->PLSQL)
*** VVISHWES 09/16/13 12:04 am ***
@ this is the same issue as addressed in bug13580189 for the same customer.
@ please provide a testcase, as had been requested in the previously opened bug.
*** YSAEZ 10/14/13 02:19 am *** (CHG: Sta->16)
*** YSAEZ 10/14/13 02:19 am ***
@ No testcase is possible. The issue happens randomly and the error is not
@ reproduced when the plsql block to create the job, or the task included in
@ the job are executed manually.
@ .
@ The customer is able to apply a diagnostic patch to progress on the issue.
*** VVISHWES 10/16/13 02:00 am *** (CHG: Sta->10)
*** VVISHWES 10/16/13 02:00 am ***
@ upload the code for MMD_SETROUTER_API and MMD_OCIS_SET_ROUTERS.
@ Were there any changes done, after which the issue started occurring.
*** YSAEZ 10/16/13 05:15 am ***
@ ISS:3-7620397301:pkgs.rar:packages
*** YSAEZ 10/16/13 05:17 am *** (CHG: Sta->16)
*** YSAEZ 10/16/13 05:17 am ***
@ Attached the packages. The customer says that there was not any change at
@ aapplication level or database level before the errors started
@ *** SCASTLED 10/17/13 03:48 am *** (CHG: Support Contact->VVISHWES->SCASTLED)
*** SCASTLED 10/17/13 03:48 am *** (CHG: Asg->SCASTLED SubComp->RUNTIME)
*** SCASTLED 10/17/13 07:28 am *** (CHG: Sta->32)
*** SCASTLED 10/17/13 07:28 am ***
@ EMEA Languages BDE:
You get an empty (ie no arguments) ora-600 with the ora-700 above when
you explicitly raise an ora-600 from plsql. For instance running:
DECLARE
sys_exc EXCEPTION;
PRAGMA EXCEPTION_INIT (sys_exc, -600);
BEGIN
RAISE sys_exc;
END;
/
gives:
DECLARE
*
ERROR at line 1:
ORA-600: internal error code, arguments: [], [], [], [], [], [], [], [],
[],
[], [], []
ORA-6512: at line 5
and creates a trace containing:
ORA-700: soft internal error, arguments: [kgerev1], [600], [600],
[700], [], [], [], [], [], [], [], []
with a very similar stack to here.
Looking at the code that's been uploaded. The error is raised from the call
to MMD_OCIS_SET_ROUTERS.EXECUTE_SET_ITEMS_TO_ROUTER in the failing plsql
block.
Line 317 of package MMD_OCIS_SET_ROUTERS is a call to
MMD_OCIS_SET_ROUTERS.set_items_to_router from a cursor for loop.
Line 210 is a call to mmd_setrouter_api.mmdsetrouters_3 whilst looping
through entries of a collection.
Line 618 of package mmd_setrouter_api looking at the uploaded code is an ELSE
from parse_string_to_array which is clearly not correct so this does not
appear to be the code they are running in the d/b.
There are two overloaded copies of function mmdsetrouters_3. The first
starts at line 470 and ends at line 546; the second starts at line 1323 and
ends at line 1860.
Line 1829 in this copy is "WHEN err_derive_member_reasons" in the second
mmdsetrouters_3 which is called from the first but clearly not right again.
There are a number of raise calls in this package. Pragma excpetion_init is
declared for the following errors in the package body:
-54, -100, -200, -300, -600, -700, -800, -900, -901, -1000, -1001, -1002
Of these only -54 is being used for the corresponding oracle error case of
resource busy. The rest are being used as user defined errors even
though all but 500 is a predefined oracle error code so oracle will check and
handle accordingly.
Even though this isn't quite the right copy of the package we can see that
the code is incorrectly raising oracle error codes. When one of these is an
internal error such as 600 or 700 a corresponding trace file is created. For
user defined errors they should be in the 20,000 range.
The generation of trace files is therefore expected behaviour.
If the customer needs to know why the app is now hitting the places where it
wants to raise 600 or 700 when previously it didn't then this needs
investigating by Apps and Apps should fix this code to only raise 20K range
errors for user defined ones.
Since there is no bug from the d/b side, closing this at 32.
你核对下是否是该bug？
另外，你的oracle11g 32位，操作系统64位的 这个做法本身就有问题
这样的问题，如果不能解决，可以私下联系我收起
浏览1862
回复 3# 致知
Sweep [inc][54534]: completed
Errors in file e:\app\administrator\diag\rdbms\xcky\xcky\trace\xcky_m000_5512.trc (incident=54535):
ORA-00700: soft internal error, arguments: [kgerev1], [600], [600], [700], [], [], [], [], [], [], [], []
Sweep [inc2][54534]: completed
Wed May 20 14:00:45 2015
Sweep [inc][54518]: completed
Incident details in: e:\app\administrator\diag\rdbms\xcky\xcky\incident\incdir_54535\xcky_m000_5512_i54535.trc
Sweep [inc][54535]: completed
Wed May 20 14:00:45 2015
Trace dumping is performing id=[cdmp_20150520140045]
Errors in file e:\app\administrator\diag\rdbms\xcky\xcky\trace\xcky_m000_5512.trc (incident=54536):
ORA-00600: internal error code, arguments: [ORA-00600: internal error code, arguments: [kdsgrp1], [], [], [], [], [], [], [], [], [], [], []
], [], [], [], [], [], [], [], [], [], [], []
Incident details in: e:\app\administrator\diag\rdbms\xcky\xcky\incident\incdir_54536\xcky_m000_5512_i54536.trc
Wed May 20 14:00:46 2015
OER 7451 in Load Indicator : Error Code = OSD-04500: 指定了非法选项
O/S-Error: (OS 1) 函数不正确。 !
Trace dumping is performing id=[cdmp_20150520140047]收起
Sweep [inc][54534]: completed
Errors in file e:\app\administrator\diag\rdbms\xcky\xcky\trace\xcky_m000_5512.trc (incident=54535):
ORA-00700: soft internal error, arguments: [kgerev1], [600], [600], [700], [], [], [], [], [], [], [], []
Sweep [inc2][54534]: completed
Wed May 20 14:00:45 2015
Sweep [inc][54518]: completed
Incident details in: e:\app\administrator\diag\rdbms\xcky\xcky\incident\incdir_54535\xcky_m000_5512_i54535.trc
Sweep [inc][54535]: completed
Wed May 20 14:00:45 2015
Trace dumping is performing id=[cdmp_20150520140045]
Errors in file e:\app\administrator\diag\rdbms\xcky\xcky\trace\xcky_m000_5512.trc (incident=54536):
ORA-00600: internal error code, arguments: [ORA-00600: internal error code, arguments: [kdsgrp1], [], [], [], [], [], [], [], [], [], [], []
], [], [], [], [], [], [], [], [], [], [], []
Incident details in: e:\app\administrator\diag\rdbms\xcky\xcky\incident\incdir_54536\xcky_m000_5512_i54536.trc
Wed May 20 14:00:46 2015
OER 7451 in Load Indicator : Error Code = OSD-04500: 指定了非法选项
O/S-Error: (OS 1) 函数不正确。 !
Trace dumping is performing id=[cdmp_20150520140047]收起
浏览1776
回复 2# bygt2010
Sweep [inc][54534]: completed
Errors in file e:\app\administrator\diag\rdbms\xcky\xcky\trace\xcky_m000_5512.trc (incident=54535):
ORA-00700: soft internal error, arguments: [kgerev1], [600], [600], [700], [], [], [], [], [], [], [], []
Sweep [inc2][54534]: completed
Wed May 20 14:00:45 2015
Sweep [inc][54518]: completed
Incident details in: e:\app\administrator\diag\rdbms\xcky\xcky\incident\incdir_54535\xcky_m000_5512_i54535.trc
Sweep [inc][54535]: completed
Wed May 20 14:00:45 2015
Trace dumping is performing id=[cdmp_20150520140045]
Errors in file e:\app\administrator\diag\rdbms\xcky\xcky\trace\xcky_m000_5512.trc (incident=54536):
ORA-00600: internal error code, arguments: [ORA-00600: internal error code, arguments: [kdsgrp1], [], [], [], [], [], [], [], [], [], [], []
], [], [], [], [], [], [], [], [], [], [], []
Incident details in: e:\app\administrator\diag\rdbms\xcky\xcky\incident\incdir_54536\xcky_m000_5512_i54536.trc
Wed May 20 14:00:46 2015
OER 7451 in Load Indicator : Error Code = OSD-04500: 指定了非法选项
O/S-Error: (OS 1) 函数不正确。 !
Trace dumping is performing id=[cdmp_20150520140047]收起
Sweep [inc][54534]: completed
Errors in file e:\app\administrator\diag\rdbms\xcky\xcky\trace\xcky_m000_5512.trc (incident=54535):
ORA-00700: soft internal error, arguments: [kgerev1], [600], [600], [700], [], [], [], [], [], [], [], []
Sweep [inc2][54534]: completed
Wed May 20 14:00:45 2015
Sweep [inc][54518]: completed
Incident details in: e:\app\administrator\diag\rdbms\xcky\xcky\incident\incdir_54535\xcky_m000_5512_i54535.trc
Sweep [inc][54535]: completed
Wed May 20 14:00:45 2015
Trace dumping is performing id=[cdmp_20150520140045]
Errors in file e:\app\administrator\diag\rdbms\xcky\xcky\trace\xcky_m000_5512.trc (incident=54536):
ORA-00600: internal error code, arguments: [ORA-00600: internal error code, arguments: [kdsgrp1], [], [], [], [], [], [], [], [], [], [], []
], [], [], [], [], [], [], [], [], [], [], []
Incident details in: e:\app\administrator\diag\rdbms\xcky\xcky\incident\incdir_54536\xcky_m000_5512_i54536.trc
Wed May 20 14:00:46 2015
OER 7451 in Load Indicator : Error Code = OSD-04500: 指定了非法选项
O/S-Error: (OS 1) 函数不正确。 !
Trace dumping is performing id=[cdmp_20150520140047]收起
浏览1750
浏览1717
