What is an ORA-600 Internal Error? (文档 ID 146580.1)
2014-01-12 15:10
351 查看
In this Document
Oracle Server - Personal Edition
Oracle Server - Standard Edition
Oracle Server - Enterprise Edition - Version 7.0.16.0 and later
Information in this document applies to any platform.
***Checked for relevance on 16-Jan-2013***
This article provides a brief description of ORA-600 Internal Errors.
ORA-600 errors are raised from the kernel code of the Oracle RDBMS software when an internal inconsistency is detected or an unexpected condition is met. This situation is not necessarily a bug as it might be caused by problems with the Operating System,
lack of resources, hardware failures, etc.
With the ORA-600 error comes a list of arguments in square brackets. The first of these arguments tells us from where in the code the error was caught and thus is the key information in identifying the problem. This argument is either a number or a character
string. The remaining arguments are used to supply further information (e.g. values of internal variables etc).
Whenever an ORA-600 error is raised a trace file is generated and an entry written to the alert.log with details of the trace file location. Starting with Oracle Database 11g Release 1, the diagnosability infrastructure was introduced which places the trace
and core files into a location controlled by the DIAGNOSTIC_DEST initialization parameter when an incident, such as an ORA-600 is created. For earlier versions, the trace file will be written to either USER_DUMP_DEST (if the error was caught in a user process)
or BACKGROUND_DUMP_DEST (if the error was caught in a background process like PMON or SMON). The trace file contains vital information about what led to the error condition.
Video - What
is an ORA-600 Internal Error? (03:21)
NOTE:18485.1 - OERR: ORA 600 "internal error code, arguments: [%s],[%s],[%s], [%s], [%s],
Note
146580.1.
(3 MB)
Oracle
Database Products > Oracle
Database > Oracle
Database > Oracle
Database - Personal Edition > RDBMS > ORA-600
by dbase unrelated to another product or component
Oracle
Database Products > Oracle
Database > Oracle
Database > Oracle
Database - Standard Edition > Generic
RDBMS > ORA-600
by dbase unrelated to another product or component
Oracle
Database Products > Oracle
Database > Oracle
Database > Oracle
Database - Enterprise Edition > RDBMS > ORA-600
by dbase unrelated to another product or component
BACKGROUND_DUMP_DEST;
DYNAMIC
ADV USE;
USER_DUMP_DEST
600
ERROR
Purpose |
Details |
References |
APPLIES TO:
Oracle Server - Personal EditionOracle Server - Standard Edition
Oracle Server - Enterprise Edition - Version 7.0.16.0 and later
Information in this document applies to any platform.
***Checked for relevance on 16-Jan-2013***
PURPOSE
This article provides a brief description of ORA-600 Internal Errors.
DETAILS
ORA-600 errors are raised from the kernel code of the Oracle RDBMS software when an internal inconsistency is detected or an unexpected condition is met. This situation is not necessarily a bug as it might be caused by problems with the Operating System,lack of resources, hardware failures, etc.
With the ORA-600 error comes a list of arguments in square brackets. The first of these arguments tells us from where in the code the error was caught and thus is the key information in identifying the problem. This argument is either a number or a character
string. The remaining arguments are used to supply further information (e.g. values of internal variables etc).
Whenever an ORA-600 error is raised a trace file is generated and an entry written to the alert.log with details of the trace file location. Starting with Oracle Database 11g Release 1, the diagnosability infrastructure was introduced which places the trace
and core files into a location controlled by the DIAGNOSTIC_DEST initialization parameter when an incident, such as an ORA-600 is created. For earlier versions, the trace file will be written to either USER_DUMP_DEST (if the error was caught in a user process)
or BACKGROUND_DUMP_DEST (if the error was caught in a background process like PMON or SMON). The trace file contains vital information about what led to the error condition.
Video - What
is an ORA-600 Internal Error? (03:21)
REFERENCES
NOTE:18485.1 - OERR: ORA 600 "internal error code, arguments: [%s],[%s],[%s], [%s], [%s],
|
Note
146580.1.
(3 MB)
|
|
Database Products > Oracle
Database > Oracle
Database > Oracle
Database - Personal Edition > RDBMS > ORA-600
by dbase unrelated to another product or component
Oracle
Database Products > Oracle
Database > Oracle
Database > Oracle
Database - Standard Edition > Generic
RDBMS > ORA-600
by dbase unrelated to another product or component
Oracle
Database Products > Oracle
Database > Oracle
Database > Oracle
Database - Enterprise Edition > RDBMS > ORA-600
by dbase unrelated to another product or component
|
BACKGROUND_DUMP_DEST;
DYNAMIC
ADV USE;
USER_DUMP_DEST
|
600
ERROR
相关文章推荐
- What is an ORA-600 Internal Error? (文档 ID 146580.1)
- What Is The Maximum Tablespace Size And Database Limit For An Oracle Database ? (文档 ID 1372905.1)
- ORA-600 [13004] Raised With CREATE INDEX (文档 ID 1667585.1)
- Master Note for Diagnosing ORA-600 (文档 ID 1092832.1)
- How to Analyze Problems Related to Internal Errors (ORA-600) and Core Dumps (ORA-7445) using My Oracle Support (文档 ID 260459.1)
- What is a Flash Recovery Area and how to configure it ? (文档 ID 305648.1)
- ORA-600 [2662] Block SCN is ahead of Current SCN [ID 28929.1]
- ORA-600 [kghstack_free2] Raised by Corrupt Datafile (文档 ID 748310.1)
- What is Split Brain in Oracle Clusterware and Real Application Cluster (文档 ID 1425586.1)
- ORA-600/ORA-7445/ORA-700 Error Look-up Tool (文档 ID 153788.1)
- What is a Flash Recovery Area and how to configure it ? (文档 ID 305648.1)
- How to Find the Offending SQL from a ORA-600 or ORA-7445 Trace File (文档 ID 154170.1) 转到底部 In this
- ORA-600 [2662] Block SCN is ahead of Current SCN [ID 28929.1]
- Memory Notification: Library Cache Object loaded into SGA / ORA-600 [KGL-heap-size-exceeded] (文档 ID
- ORA-600 [2662] Block SCN is ahead of Current SCN [ID 28929.1]
- ORA-07445 or ORA-600 Errors With a Big Stack or a Corrupted Stack (文档 ID 1318825.1)
- What is the Database Initialization Parameter That is Associated to an ORA-32004 Error ?
- ORA-600 [2662] Block SCN is ahead of Current SCN [ID 28929.1]
- What is an ORA-04031 Error?
- ORA-07445 [kksumc] And ORA-600 [17087] During Insert Into Table (文档 ID 580347.1)