Ora-00600 Error Lookup
Contents |
By user706992 on Jun 09, 2010
QUICKLINK: Note 600.1 ORA-600/ORA-7445 Lookup toolNote 1082674.1 : A Video To Demonstrate The Usage Of The ORA-600/ORA-7445 Lookup Tool [Video] Have you observed an ORA-0600 error reported in your alert log? The ORA-600 error is the generic ora-00600 internal error code arguments in oracle internal error number for Oracle program exceptions. It indicates that a process has encountered aOra-00600 Solution
low-level, unexpected condition. The ORA-600 error statement includes a list of arguments in square brackets: ORA 600 "internal error code, arguments: [%s], [%s],[%s], ora 600 lookup tool on metalink [%s], [%s]" The first argument is the internal message number or character string. This argument and the database version number are critical in identifying the root cause and the potential impact to your system. The remaining arguments in ora 00600 internal error code arguments 2141 the ORA-600 error text are used to supply further information (e.g. values of internal variables etc). The first argument may help to narrow your problem to known issues. However, this argument can point to functionality that is referenced by many areas in the Oracle source code. The more detailed call stack information reported in the ORA-600 error trace may be needed to find a solution.
Looking for the best way to diagnose? Whenever an ORA-600Ora-7445
error is raised, a trace file is generated and an entry is written to the alert.log with details of the trace file location. As of Oracle 11g, the database includes an advanced fault diagnosability infrastructure to manage trace data. For more detail on this functionality see the FAQ and quick steps video.
Note 453125.1 11g Diagnosability Frequently Asked Questions Note 443529.1 11g Quick Steps to Package and Send Critical Error Diagnostic Information to Support[Video] 1. Check the Alert Log The alert log may indicate additional errors or other internal errors at the time of the problem. Focus your analysis of the problem on the first internal error in the sequence. There are some exceptions, but often additional internal errors are side-effects of the first error condition. The associated trace file may be truncated if the MAX_DUMP_FILE_SIZE parameter is not setup high enough or to „unlimited‟. If you see a message at the end of the trace file "MAX DUMP FILE SIZE EXCEEDED" there could be vital diagnostic information missing in the file and finding the root issue may be very difficult. Set the MAX_DUMP_FILE_SIZE appropriately and regenerate the error for complete trace information. 2. Search 600/7445 Lookup Tool Visit My Oracle Support to access the ORA-00600 Lookup tool (Note 600.1). The ORA-600/ORA-7445 Lookup tool may lead you to applicable content in Mythe generic kernel code of the Oracle RDBMS software. It is different from other Oracle errors in many ways. The following is a list of these differences: 1. An ORA-600 error may or may not be ora-00600 kcratr_nab_less_than_odr displayed on the screen. Therefore, screen output should not be relied on for capturing information ora 600 error oracle 10g on this error. Information on ORA-600 errors are found in the database alert and trace files. We recommend that you check these files
Ora-00600 Rwoirw: Check Ret Val
frequently for database errors. (See the Alert and Trace Files section for more information.) 2. Each ORA-600 error comes with a list of arguments They usually enclosed in square brackets and follow the error on the same https://blogs.oracle.com/db/entry/ora-600_troubleshooting line for example: 3. Also some time, if we have used many cte's in a SP then it throws same error because of memory used by these ctc's exceed. ORA-00600 [14000][51202][1][51200][][] Each argument has a specific meaning which can only be interpreted by an Oracle support analyst. The arguments may also change meaning from version to version therefore customers are not advised to memorize them. 4. Every occurrence of an ORA-600 should be reported to http://www.orafaq.com/wiki/ORA-00600 Oracle Support. Unlike other errors, you can not find help text for these errors. Only Oracle technical support should diagnose and take actions to prevent or resolve damage to the database. 5. Each ORA-600 error generates a database trace file. Possible causes[edit] Possible causes include: time-outs, file corruption, failed data checks in memory, hardware, memory, or I/O messages, incorrectly restored files a SELECT FROM DUAL statement in PL/SQL within Oracle Forms (you have to use SELECT FROM SYS.DUAL instead!) How to fix it[edit] Contact Oracle Support with the following information: events that led up to the error the operations that were attempted that led to the error the conditions of the operating system and database at the time of the error any unusual circumstances that occurred prior to receiving the ORA-00600 message. contents of any trace files generated by the error the relevant portions of the Alert file in Oracle Forms PL/SQL, use SELECT FROM SYS.DUAL to access the system "dual" table Sometimes gathering statistics on the involved tables resolves the problem. Deleting statistics for a table involved would also solve the problem Try to reduce the no of CTE blocks in Stored Procedure.It's work in some scenarios as oracle doesn't support more than 20 cte's in single SP. Also see[edit] adrci - Automatic Diagnostic Repository Command Interface Troubleshooting Internal Errors. Retrieved from "http://www.orafaq.com/wiki/index.php?tit
SQL TuningSecurityOracle UNIXOracle LinuxMonitoringRemote supportRemote plansRemote servicesApplication Server ApplicationsOracle FormsOracle PortalApp UpgradesSQL ServerOracle ConceptsSoftware SupportRemote Support Development Implementation Consulting StaffConsulting PricesHelp Wanted! Oracle PostersOracle Books Oracle Scripts Ion Excel-DB Don Burleson Blog
http://www.dba-oracle.com/oracle_tips_ora_600.htm Lookup Oracle ORA-600 Internal Errors Oracle Tips http://dba.stackexchange.com/questions/100960/ora-00600-argument-description by Burleson Consulting Don Burleson The ORA-00600 (ORA 600) error is a generic internal error from Oracle, and you must look-up the numeric arguments to understand the nature of the internal error. A typical ORA-00600 error does not include descriptive text and might look like this, with various arguments following the message in the internal error Oracle alert log:: ORA-00600 [723][51202][1][51200][][] Oracle MOSC now provides Note 153788.1 to allow you to get the description for an ORA-600 error. In this web form, we can enter the 723 argument for the ORA-600 error: You can type-in the numeric argument for the ORA-600 message and get the a MOSC note relating to the error: Or you can type-in the the call stack trace from the trace file internal error code that was generated from the ORA-600 trace file. Remember, all ORA-600 errors in the alert log should be reported to Oracle Technical Support, and most Oracle DBAs open an iTAR. �� Burleson is the American Team Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals. Feel free to ask questions on our Oracle forum. Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications. Errata? Oracle technology is changing and we strive to update our BC Oracle support information. If you find an error or have a suggestion for improving our content, we would appreciate your feedback. Just e-mail: and include the URL for the page. Burleson Consulting The Oracle of Database Support Oracle Performance Tuning Remote DBA Services Copyright © 1996 - 2016 All rights reserved by Burleson Oracle is the registered trademark of Oracle Corporatilog in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Database Administrators Questions Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top ORA-00600 argument description up vote 0 down vote favorite I am experiencing several ORA-00600 error events, presumably during exceptionally high I/O. Does anyone know where I can lookup the meaning of the following arguments for ktspfmdb:objdchk_kcbnew_3? I.e. what does 13, 873730 and 4 stand for? ORA-00600: internal error code, arguments: [ktspfmdb:objdchk_kcbnew_3], [13], [873730], [4], [], [], [], [], [], [], [], [] oracle oracle-11g-r2 share|improve this question edited May 8 '15 at 11:43 asked May 8 '15 at 11:34 Matthias 1177 1 Use the ORA-600 lookup tool on the Oracle support site. –Philᵀᴹ May 8 '15 at 13:30 add a comment| 2 Answers 2 active oldest votes up vote 2 down vote accepted You are facing a bug. You need to gather more information using RDA in order to perform an in-depth analysis. These are known bugs related to your ORA-600 message. 10043021 11.2.0.4, 12.1.0.1 ORA-600 [kcbnew_3] after select / analyze on RECYCLEBIN object 17586955 11.2.0.4.4, 11.2.0.4.BP11 ORA-600 [ktspfmdb:objdchk_kcbnew_3] in RAC 12747437 11.2.0.3.8, 11.2.0.3.BP21, 11.2.0.4, 12.1.0.1 ORA-600 [ktspfmdb:objdchk_kcbnew_3] after purging single consumer queue table 12323180 11.2.0.2.7, 11.2.0.2.BP17, 11.2.0.3, 12.1.0.1 ORA-600 [ktspfmdb:objdchk_kcbnew_3] due to re-used block read into cache 11902008 11.2.0.4, 12.1.0.1 SMON may crash with ORA-600 [kcbgcur_3] or ORA-600 [kcbnew_3] during Transaction recovery 10137834 11.2.0.2 ORA-600 running DBMS_XDB.MOVEXDB_TABLESPA