Ora-600[Qsmogetsqlmgmtobjhintsbytype:2] Error from a SELECT statement (Doc ID 1330360.1)

Last updated on JANUARY 13, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 11.1.0.7 and later
Information in this document applies to any platform.

Symptoms

1. Receiving a series of ORA-600[qsmoGetSqlMgmtObjHintsByType:2], [], [], [], [], [], [], [], [], [], [], [] error with trace files names seen in the alert.log file like:

Errors in file /u01/app/oracle/diag/rdbms/e9pd/e9pd1/trace/e9pd1_ora_13984.trc (incident=12181288):
ORA-00600: internal error code, arguments: [qsmoGetSqlMgmtObjHintsByType:2], [], [], [], [], [], [], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/e9pd/e9pd1/incident/incdir_12181288/e9pd1_ora_13984_i12181288.trc
...



2. OEM Grid Control for the same SQL_ID shows that the Parsing Schema Name is DBSNMP.

3. Trace file for the error shows the following Module and Action Names:


Dump continued from file: /u01/app/oracle/diag/rdbms/e9pd/e9pd1/trace/e9pd1_ora_13984.trc
ORA-00600: internal error code, arguments: [qsmoGetSqlMgmtObjHintsByType:2], [], [], [], [], [], [], [], [], [], [], []

========= Dump for incident 12181288 (ORA 600 [qsmoGetSqlMgmtObjHintsByType:2]) ========

*** 2011-06-05 09:05:48.689
----- Current SQL Statement for this session (sql_id=a8j39qb13tqkr) -----
SELECT :B1 TASK_ID, F.FINDING_ID FINDING_ID,DECODE(RECINFO.TYPE,NULL, 'Uncategorized',RECINFO.TYPE) REC_TYPE, RECINFO.RECCOUNT REC_COUNT, F.PERC_ACTIVE_SESS IMPACT_PCT, F.MESSAGE MESSAGE, TO_DATE(:B3 ,'MM-DD-YYYY HH24:MI:SS') START_TIME, TO_DATE(:B2 ,'MM-DD-YYYY HH24:MI:SS') END_TIME, HISTORY.FINDING_COUNT FINDING_COUNT, F.FINDING_NAME FINDING_NAME, F.ACTIVE_SESSIONS ACTIVE_SESSIONS FROM DBA_ADDM_FINDINGS F, (SELECT FINDING_ID, COUNT(R.REC_ID) RECCOUNT,R.TYPE FROM DBA_ADVISOR_RECOMMENDATIONS R WHERE TASK_ID=:B1 GROUP BY R.FINDING_ID, R.TYPE) RECINFO, (SELECT COUNT(F_ALL.TASK_ID) FINDING_COUNT, F_CURR.FINDING_NAME FROM (SELECT FINDING_NAME FROM DBA_ADVISOR_FINDINGS WHERE TASK_ID=:B1 ) F_CURR, (SELECT T.TASK_ID,I.LOCAL_TASK_ID,T.END_TIME, T.BEGIN_TIME FROM DBA_ADDM_TASKS T,DBA_ADDM_INSTANCES I WHERE T.END_TIME>SYSDATE -1 AND T.TASK_ID=I.TASK_ID AND I.INSTANCE_NUMBER=SYS_CONTEXT('USERENV','INSTANCE') AND T.REQUESTED_ANALYSIS='INSTANCE' ) TASKS, DBA_ADVISOR_FINDINGS F_ALL WHERE F_ALL.TASK_ID=TASKS.TASK_ID AND F_ALL.FINDING_NAME=F_CURR.FINDING_NAME AND F_ALL.TYPE<>'INFORMATION' AND F_ALL.TYPE<>'WARNING' AND F_ALL.PARENT=0 GROUP BY F_CURR.FINDING_NAME) HISTORY WHERE F.TASK_ID=:B1 AND F.TYPE<>'INFORMATION' AND F.TYPE<>'WARNING' AND F.FILTERED<>'Y' AND F.PARENT=0 AND F.FINDING_ID=RECINFO.FINDING_ID (+) AND F.FINDING_NAME=HISTORY.FINDING_NAME ORDER BY F.FINDING_ID
----- PL/SQL Stack -----
----- PL/SQL Call Stack -----
object line object
handle number name
0xf7e971898 54 anonymous block


Functions from the call stack from tracefile:

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms