My Oracle Support Banner

Database Crashed After an ORA-600 [KSSRMP1] Was Hit (Doc ID 1371273.1)

Last updated on MARCH 09, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 to 11.2.0.2 [Release 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 29-Apr-2013***

Symptoms

In a RAC environment, after hitting a failure in a logon trigger, a job queue process fails with ORA-600 [KSSRMP1], eg. as:

Errors in file <diagnostic_dest>/diag/rdbms/<dbname>/<instname>/trace/<instname>_j000_11891.trc (incident=242787):
ORA-00600: internal error code, arguments:[KSSRMP1], [], [], [], [], [], [], [], [], [], [], []


and subsequently the database crashes due to PMON hitting an ORA-600 [1163], eg.:

Thu Oct 06 15:00:46 2011
Errors in file <diagnostic_dest>/diag/rdbms/<dbname>/<instname>/trace/<instname>_ora_5171.trc (incident=233096):
ORA-00600: internal error code, arguments: [kxsGetRuntimeLock2], [0xA7790AE40], [1], [1], [0], [], [], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/<dbname>/<instname>/incident/incdir_233096/<instname>_ora_5171_i233096.trc
Thu Oct 06 15:00:51 2011
Errors in file<diagnostic_dest>/diag/rdbms/<dbname>/<instname>/trace/<instname>_pmon_2648.trc (incident=231622):
ORA-00600: internal error code, arguments: [1163], [], [], [], [], [], [], [], [], [], [], []
Incident details in:<diagnostic_dest>/diag/rdbms/<dbname>/<instname>/incident/incdir_231622/<instname>_pmon_2648_i231622.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Errors in file <diagnostic_dest>/diag/rdbms/<dbname>/<instname>/trace/<instname>_pmon_2648.trc:
ORA-00600: internal error code, arguments: [1163], [], [], [], [], [], [], [], [], [], [], []
PMON (ospid: 2648): terminating the instance due to error 472


It is also possible that the database may crash due to this problem after a job queue process fails with ORA-600 [ksqcmi:res32] as in:

Errors in file <diagnostic_dest>/diag/rdbms/<dbname>/<instname>/trace/<instname>_cjq0_18344.trc (incident=368756):
ORA-600: internal error code, arguments: [1163], [], [], [], [], [], [], [], [], [], [], []
ORA-600: internal error code, arguments: [ksqcmi:res32], [0x252014D90], [], [], [], [], [], [], [], [], [], []
Incident details in: <diagnostic_dest>/diag/rdbms/<dbname>/<instname>/incident/incdir_368756/<instname>_cjq0_18344_i368756.trc


The key symptoms are:

Changes

 

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.