In this Document
  Symptoms
  Cause
  Solution
  References

Applies to:

Oracle Server Enterprise Edition - Version: 9.2.0.1 to 10.2.0.4
This problem can occur on any platform.
Oracle Server - Enterprise Edition - Version: 10.1.0.1 to 10.2.0.4
The PL/SQL package DBMS_DEBUG is being used.

Symptoms

ORA-600 [17285] followed by an ORA-604 "error occurred at recursive SQL level %d" in module SYS.PBREAK with possible subsequent ORA-7445 errors in modules pfrtcs()/pfrdmp() when using the DBMS_DEBUG package.

Cause

This is due to Bug 4640115 currently under investigation by development, where if an ORA- error occurs in module SYS.PBREAK it may not be trapped and handled correctly.

Solution

Correct the underlying ORA- error that occurred in SYS.PBREAK, such as:
ORA-1031: insufficient privileges:

    Grant DEBUG CONNECT SESSION privilege to any user who uses debug mode in PL/SQL, e.g.:.
    connect / as sysdba
    grant DEBUG CONNECT SESSION to ;
    exit

ORA-1013: user requested cancel of current operation:

Ignore the error which is harmless as the user has already tried to cancel the current operation hence the presence of the ORA-1013 'user requested cancel of current operation' error message, or do not use plsql debugging (plsql_debug=true) either in the database or via the client application, such as PLSQL Developer.

References

Bug 4640115 - [9/6] GETTING ORA 600 WHEN DEBUGGING PL/SQL ORA-600
Note 138602.1 - ORA-600 [17285]

Keywords

DBMS_DEBUG ; 17285 ; OERI ; 

Help us improve our service. Please email us your comments for this document. .