Database Crashes when MEMORY_TARGET is Increased
(Doc ID 2232390.1)
Last updated on MAY 20, 2021
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
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:
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