Skip to main content

ORA-00600: internal error code, arguments: [7005],

Hi all,

Today i am going to write another one of mine analysis by using My oracle support site document.

In one of our client's database, we are getting the following error message continuously.

Alert log entry:
Wed Jul 23 11:45:43 2014
Errors in file /home/oracle/app/oracle/diag/rdbms/db/db/trace/db_ora_14547.trc  (incident=149824):
ORA-00600: internal error code, arguments: [7005], [0], [], [], [], [], [], [], [], [], [], []

SQL_TEXT involved in this error is 

select iso_country_code  from countries  where (SDO_RELATE(geom,SDO_GEOMETRY(:"SYS_B_0",:"SYS_B_1"),:"SYS_B_2")=:"SYS_B_3")


So one of our dba has reported like below after searching the document for the error.

According to Doc ID 138935.1

The error occurred due to Bug 8770557

Description:

ORA-600 [7005] from SQL with user defined selectivity function (eg: Text queries)

Solution:

The issue is fixed in 11.2.0.2, 12.1.0.1


But our manager didn't want to take this analysis completely  He wrote us that "Please explain your analysis with respect to the statement involved".

So i came up with the solution to which he agreed with us that it is a bug.

My analysis is given below. 

I have gone through the same oracle support document (Doc ID 138935.1) for my reference.

As per the same MOSC  Doc ID 138935.1

ORA-00600: internal error code, arguments: [7005] is raised because of predicate used in the where clause of the below sql statement. 

 Description
User-defined selectivity functions may be called with not all bind values having being bound.  This can lead to subsequent ORA-600 [7005] errors.
 This could occur when using Text queries with a CONTAINS predicate. 

But in our sql statement (given above) is using bind variables. 
Hence I have decided to check the value for bind variables it is using from view V$SQL_BIND_CAPTURE.

Values of Bind variables
:SYS_B_0             -              POINT(10.476937 45.617856) (This value captured on today & This value is different every day)
:SYS_B_1             -              4326
:SYS_B_2             -              MASK=CONTAINS+COVERS
:SYS_B_3             -              TRUE

So our sql statement uses the CONTAINS predicate in the user defined operator. 
This is how we made our manager to agree with us.

Comments

Post a Comment

Popular posts from this blog

Export and import multiple schema using expdp/impdp (Data Pump utility)

Use the below sql query to export and import multiple schema: expdp schemas=schema1,schema2,schema3 directory=DATA_PUMP_DIR dumpfile=schemas120514bkp.dmp exclude=statistics logfile=expdpschemas120514.log impdp schemas=schema1,schema2,schema3 directory=DATA_PUMP_DIR dumpfile=schemas120514bkp.dmp logfile=impdpschemas120514.log sql query to export and import a schema: expdp schemas=schema directory=DATA_PUMP_DIR dumpfile=schema120514bkp.dmp exclude=statistics logfile=expdpschema120514.log impdp schemas=schema directory=DATA_PUMP_DIR dumpfile=schema120514bkp.dmp logfile=expdpschema120514.log Parameter STATISTICS=NONE can either be used in export or import. No need to use the parameter in both. To export meta data only to get ddl of the schemas: expdp schemas=schema1,schema2,schema3 directory=TEST_DIR dumpfile=content.dat content=METADATA_ONLY exclude=statistics To get the DDL in a text file: impdp directory=TEST_DIR sqlfile=sql.dat logfile=sql.log dumpfil...
3 comments
Read more

Pinning execution plan for a sql_id using 'SQL Profile' to consistently reproduce a good plan

Deal all, Below post content is not my own. It is taken from MOSC document but the example shown below is taken from our environment. I got to know the below topic when we had experienced the bad SQL query performance in one of our production environment during daily batch running time. Hence we had implemented the same mentioned in the title "Pinning execution plan for a sql_id using 'SQL Profile' to consistently reproduce a good plan". Introduction The "cost-based optimizer (CBO or just optimizer) is the part of database software that determines the most efficient means of accessing the specified data (or at least what it "calculates" as the most efficient). The optimizer determines which execution plan is most efficient by considering several sources of information, including query conditions, available access paths, statistics gathered for the system, and hints. Some changes in those conditions may affect the calculations of the plan...
9 comments
Read more

Metrics Process Limit Usage percentage (%) is critical or warning in OEM or Cloud Control 12c or Cloud Control 13c

Please run the below queries to trace details during Metric alert "Process Limit % is >= 75" in OEM or Cloud Control 12c or Cloud Control 13c To check the Metrics Process Limit Usage (%): ***************************************************** set lines 300 col INITIAL_ALLOCATION for a17 col LIMIT_VALUE for a12 select resource_name,current_utilization,max_utilization, INITIAL_ALLOCATION,LIMIT_VALUE,((current_utilization*100)/(INITIAL_ALLOCATION)) as "Process limit %" from v$resource_limit where resource_name in ('processes'); The below query will give you all connected sessions (ACTIVE and INACTIVE) to instance: ******************************************************************************************************* set pages 100 set lines 1000 col SPID heading 'PID' for a06 col SID for 99999 col SERIAL# heading 'serial' for 999999 col SQL_ID for a14 col USERNAME for a10 col PROGRAM for a20 col MODULE for a18 col OSU...
Post a Comment
Read more