My Oracle Support Banner

ORA-823 Specified value of sga_target greater than sga_max_size (Doc ID 968413.1)

Last updated on JANUARY 24, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 to 11.2.0.1.0 [Release 10.2 to 11.2]
Information in this document applies to any platform.

Symptoms


ORA-823 still happens after changing sga_max_size value greater than sga_target.

Changes

The value of sga_max_size has been changed without specifying "M" meaning "Megabyte", which is definitely smaller than the current sga_target. And ORA-823 occurs when trying to correct it.


1. Setting sga_max_size without specifying "M"
SQL>alter system SET sga_max_size = 14336 scope=spfile sid='<INST_NAME>1';
SQL>alter system SET sga_max_size = 14336 scope=spfile sid='<INST_NAME>2';

2. Setting sga_max_size without specifying "M"
SQL>alter system SET sga_max_size = 14336 scope=spfile sid='*';

3. Shutdown

4. startup
    ORA-823 happens. 

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


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