ORA-16237: SGA specified for Logical Standby is too small

Cause : MAX_SGA must be at least 10 Megabytes for proper functioning of Logical Standby.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Specify the value of MAX_SGA to be greater than or equal to 10Mb. Alternatively, increase the shared_pool_size/sga_target so that 1/4 of it will amount to 10 Megabytes.

update : 20-08-2017

ORA-16237 - SGA specified for Logical Standby is too small
ORA-16237 - SGA specified for Logical Standby is too small

  • ora-02179 : valid options: ISOLATION LEVEL { SERIALIZABLE | READ COMMITTED }
  • ora-32833 : failure string trying to release administration lock
  • ora-14407 : partitioned table contains subpartitions in a different tablespace
  • ora-39137 : cannot specify a TABLE_EXISTS_ACTION of string for a job with no metadata
  • ora-19250 : XQ0030 - too many values to validate expression
  • ora-00319 : log string of thread string has incorrect log reset status
  • ora-13046 : invalid number of arguments
  • ora-01173 : data dictionary indicates missing data file from system tablespace
  • ora-36846 : (XSLMGEN16) AW name is greater than 30 bytes
  • ora-19901 : database needs more recovery to create new incarnation
  • ora-36278 : (XSCGMDLAGG07) workspace object does not exist or is not valueset.
  • ora-13291 : conversion error between the specified unit and standard unit
  • ora-14645 : STORE IN clause cannot be specified for Range List objects
  • ora-27463 : invalid program type string
  • ora-19019 : Invalid context passed to DBMS_XMLGEN.GETXML
  • ora-08000 : maximum number of session sequence lists exceeded
  • ora-27472 : invalid metadata attribute string
  • ora-31505 : cannot alter or drop predefined change set
  • ora-15060 : template "string" does not exist
  • ora-29362 : plan directive string, string does not exist
  • ora-16163 : LGWR network server host attach error
  • ora-25234 : NEXT_TRANSACTION navigation option invalid for queue table string.string
  • ora-12713 : Character data loss in NCHAR/CHAR conversion
  • ora-22298 : length of directory alias name or file name too long
  • ora-25202 : invalid value NULL, string should be non-NULL
  • ora-01163 : SIZE clause indicates string (blocks), but should match header string
  • ora-00321 : log string of thread string, cannot update log file header
  • ora-25331 : cannot downgrade because there are commit-time queue tables
  • ora-24360 : Type Descriptor Object not specified for Object Bind/Define
  • ora-01494 : invalid SIZE specified
  • Oracle Database Error Messages

    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.