ORA-600 [17175] in PMON when the Event 10235 Is Set with a Wrong Level
(Doc ID 737613.1)
Last updated on MARCH 28, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.1 to 11.1.0.6 [Release 10.2 to 11.1]Information in this document applies to any platform.
This problem can occur on any platform.
Symptoms
When the event 10235 is set with a wrong level, for example:
event="10235 trace name context forever, level 10235"
the PMON reports during the startup process the errors:
ORA-00600: internal error code, arguments: [17175], [255], [], [], [], [], [], []
ORA-00601: cleanup lock conflict
ORA-00601: cleanup lock conflict
Changes
NONE
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |