My Oracle Support Banner

Database Crashes when MEMORY_TARGET is Increased (Doc ID 2232390.1)

Last updated on AUGUST 04, 2018

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.2 and later
Information in this document applies to any platform.

Symptoms

The database crashes when MEMORY_TARGET is set larger than a value.  The ratio MEMORY_TARGET / RAM is still fine.

Symptoms shown in the alert log right after database startup:

Process m000 died, see its trace file
Process m001 died, see its trace file
Process m000 died, see its trace file
Process m001 died, see its trace file
Process m000 died, see its trace file
Process m001 died, see its trace file
Process m000 died, see its trace file
Process m001 died, see its trace file
Process J000 died, see its trace file
...
kkjcre1p: unable to spawn jobq slave process
...

 

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
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.