Oracle troubleshooting (ORA-00600), oracleora-00600

Source: Internet
Author: User

Oracle troubleshooting (ORA-00600), oracleora-00600

This error has been shown in the alarm log for the past two days:

ORA-00600:internalerrorcode,arguments:[kcblasm_1],[103],[],[],[],[],[],[]TueAug1209:20:17CST2014Errorsinfile/u01/app/oracle/admin/orcl/udump/orcl_ora_29974.trc:ORA-00600:internalerrorcode,arguments:[kcblasm_1],[103],[],[],[],[],[],[]TueAug1209:30:17CST2014Errorsinfile/u01/app/oracle/admin/orcl/udump/orcl_ora_30084.trc:ORA-00600:internalerrorcode,arguments:[kcblasm_1],[103],[],[],[],[],[],[]TueAug1209:40:17CST2014Errorsinfile/u01/app/oracle/admin/orcl/udump/orcl_ora_29919.trc:ORA-00600:internalerrorcode,arguments:[kcblasm_1],[103],[],[],[],[],[],[]

Solution for online query:

1: temporary solution
If the execution plan is caused by hashjoin, set "_ hash_join_enable" = false in the Session Layer, for example, altersessionset "_ hash_join_enabled" = false;

If the execution plan is caused by hashgroupby, set "_ gby_hash_aggregation_enabled" = false
2: Fundamental Solution
2. 1. Optimize SQL statements to avoid bugs;
2. Upgrade
(1) update the database psu to 10.2.0.5.4 and 11.2 to correct this problem.
(2) For versions 10.2.0.5.0 to 10.2.0.5.3, run PATCH7612454 to avoid the change (this patch replaces the kcbl. o file in lib ).

Example of a temporary solution:

Trace the trace file in the alarm log and find the SQL statement that causes this error.

ORA-00600:internalerrorcode,arguments:[kcblasm_1],[103],[],[],[],[],[],[]CurrentSQLstatementforthissession:

The formatted SQL statement is as follows:

SELECTINDENTDATE,INDENTGROUP,TRANSDATE,TRANSBY,TRANSGROUP,FEEDBACKBY,FEEDBACKGROUP,FINANCEDATE,FINANCEBY,FINANCEGROUP,TOTALCOST,A.TOTALPAY,PAY_CASH,PAY_POINTS,PAY_ADVANCE1,PAY_ADVANCE2,PAY_TYPE,TRANS_PAY,DISCOUNT_STAFF,DISCOUNT_SPECIAL,GAIN_CASH,GAIN_POINTS,GAIN_ADVANCE1,GAIN_ADVANCE2,TRANS_CUSTNAME,TRANS_TEL,TRANS_PROVINCE,TRANS_CITY,TRANS_ADDRESS,TRANS_ZIPCODE,TRANS_WEIGHT,TRANS_COMMENTS,INDENT_COMMENTS,INDENT_ID,A.PARTNER_GUID,A.PROXY_GUID,TRANS_TEL2,CUST_MEDIA_ID,CUST_PARTNER_GUID,CUST_PROXY_GUID,PARTNER_VALUE,PROXY_VALUE,CUST_PARTNER_VALUE,CUST_PROXY_VALUE,DEALBY,A.FAILREASON,ISFOOT,S_REASONID,DEALFAILREASON,A.PRE_FUND,MEDIA_CALLTYPE,PRE_ADVANCE,WEB_FLAG,NEED_INVOICE,INVOICE_TITLE,TRANS_AREA,ORDERTYPE,PAY_POINTSPRICE,A.MEDIA,USERDEFINEDSTATUS,CUSTOMERNAME,CUSTOMERIDFROMELITE.TABCINDENTALEFTJOINELITE.OBJECTIVEBONA.RELATION_ID=B.OBJECTIVE_GUIDLEFTJOINELITE.CUSTOMERCONA.CUSTOMER_GUID=C.CUSTOMER_GUIDWHERE(INDENTDATEBETWEEN:1AND:2ORB.MODIFIEDDATEBETWEEN:3AND:4);

Replace the variable: 1,: 2,: 3,: 4 with a specific value. Execute:

SELECTINDENTDATE,INDENTGROUP,TRANSDATE,TRANSBY,TRANSGROUP,FEEDBACKBY,FEEDBACKGROUP,FINANCEDATE,FINANCEBY,FINANCEGROUP,TOTALCOST,A.TOTALPAY,PAY_CASH,PAY_POINTS,PAY_ADVANCE1,PAY_ADVANCE2,PAY_TYPE,TRANS_PAY,DISCOUNT_STAFF,DISCOUNT_SPECIAL,GAIN_CASH,GAIN_POINTS,GAIN_ADVANCE1,GAIN_ADVANCE2,TRANS_CUSTNAME,TRANS_TEL,TRANS_PROVINCE,TRANS_CITY,TRANS_ADDRESS,TRANS_ZIPCODE,TRANS_WEIGHT,TRANS_COMMENTS,INDENT_COMMENTS,INDENT_ID,A.PARTNER_GUID,A.PROXY_GUID,TRANS_TEL2,CUST_MEDIA_ID,CUST_PARTNER_GUID,CUST_PROXY_GUID,PARTNER_VALUE,PROXY_VALUE,CUST_PARTNER_VALUE,CUST_PROXY_VALUE,DEALBY,A.FAILREASON,ISFOOT,S_REASONID,DEALFAILREASON,A.PRE_FUND,MEDIA_CALLTYPE,PRE_ADVANCE,WEB_FLAG,NEED_INVOICE,INVOICE_TITLE,TRANS_AREA,ORDERTYPE,PAY_POINTSPRICE,A.MEDIA,USERDEFINEDSTATUS,CUSTOMERNAME,CUSTOMERIDFROMELITE.TABCINDENTALEFTJOINELITE.OBJECTIVEBONA.RELATION_ID=B.OBJECTIVE_GUIDLEFTJOINELITE.CUSTOMERCONA.CUSTOMER_GUID=C.CUSTOMER_GUIDWHERE(INDENTDATEBETWEEN'2012-06-19'AND'2012-08-19'ORB.MODIFIEDDATEBETWEEN'2012-06-19'AND'2012-08-1');

Execution error:

Solution:

altersessionset"_hash_join_enabled"=false;

altersessionset"_gby_hash_aggregation_enabled"=false

-- Try it first. If one solution is used, there is no need to set another one.

Then run the preceding query statement again. No error is reported.

Succeeded. (* ^__ ^ *) Hey ......

Let the developer add this command to the program.


The ORACLE database has an SQL error ORA-00600 that uses SYS_CONNECT_BY_PATH to summarize some data.

Bug 4401437 connect by query may fail with OERI: qergiStart1/OERI: qesmmCValStat4
This note gives a brief overview of bug 4401437.
The content was last updated on: 03-APR-2009
Click here for details of each of the sections below.

Affects:
Product (Component) Oracle Server (Rdbms)
Range of versions believed to be affected Versions BELOW 11.1
Versions confirmed as being affected
10.2.0.1
10.1.0.4
9.2.0.8

Platforms affected Generic (all/most platforms affected)

Workaround
Add a "no_filtering" hint to the query.

You can bypass this error by adding no_filtering!

If you are not sure, contact the professional ORACLE Database repair team of shita software to help you recover it!

Shita software professional database repair team

Error code parsing for Oracle ORA-00600

The ORA-600 [4137] transaction id does not match, the problem may exist in the rollback segment or the object itself has a rollback error While backing out an undo record (I. e. at the time of rollback) we found a transaction id mis-match indicating either a resume uption in the rollback segment or resume uption in an object which the rollback segment is trying to apply undo records on.
This wocould indicate a random upted rollback segment. Undo/Redo

DESCRIPTION:

While backing out an undo record (I. e. at the time of rollback) we found
Transaction id mis-match indicating either a transaction uption in the rollback
Segment or partition uption in an object which the rollback segment is trying
Apply undo records on.

Patch undo is required to fix this problem.

If you are not sure, contact the professional ORACLE Database repair team of shita software to help you recover it!

Shita software professional database repair team

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.