SMON Signals ORA-00600 [ktspfupdst-1] and Instance Terminates (Doc ID 1353076.1)

Last updated on JANUARY 31, 2022

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 and later
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.

Symptoms

After changing the database from NOARCHIVELOG to ARCHIVELOG Mode , the following error is reported by SMON :

ERROR
-----------------------
ORA-00600: internal error code, arguments: [ktspfupdst-1], [], [], [], [], [], [], [], [], [], [], []

Alert Log File Shows :

ORA-00600: internal error code, arguments: [ktspfupdst-1], [], [], [], [], [], [], [], [], [], [], []
Incident details in: /<oracle_base>/diag/rdbms/<sid>/<dbname>/incident/incdir_14418/<sid>_smon_6431_i14418.trc
PMON (ospid: 6365): terminating the instance due to error 474
System state dump requested by (instance=1, osid=6365 (PMON)), summary=[abnormal instance termination].
System State dumped to trace file /<oracle_base>/diag/rdbms/<sid>/<dbname>/trace/<sid>_diag_6383.trc
Instance terminated by PMON, pid = 6365

The SMON incident trace file shows the following as Current SQL Statement :

Changes

Changing the database from NOARCHIVELOG to ARCHIVELOG mode .

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

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

SMON Signals ORA-00600 [ktspfupdst-1] and Instance Terminates (Doc ID 1353076.1)

Applies to:

Symptoms

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!