DB Crashes When MEMORY_TARGET Increased (Doc ID 2232390.1)

Last updated on FEBRUARY 13, 2017

Applies to:

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

Symptoms

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

Symptoms show in alert log right after 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

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms