:
ORA-600 [17285] Error Followed By ORA-604 and/or ORA-7445 Errors
:
464607.1
类型:
PROBLEM
上次修订日期:
02-MAR-2009
状态:
MODERATED
In this Document
This document is being delivered to you via Oracle Support's(RaV) process, and therefore has not been subject to an independent technical review.
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 tocurrently 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
- [9/6] GETTING ORA 600 WHEN DEBUGGING PL/SQL ORA-600- ORA-600 [17285]
Keywords
DBMS_DEBUG ; 17285 ; OERI ;
Help us improve our service. Pleaseus your comments for this document.