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 : 26-04-2017
ORA-16237

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

  • ora-40106 : positive target value not specified for computing Lift
  • ora-25195 : invalid option for index on an index-organized table
  • ora-38103 : Invalid column in the UPDATE SET Clause: string
  • ora-01660 : tablespace 'string' is already permanent
  • ora-07579 : spini: $DCLEXH failure
  • ora-19951 : cannot modify control file until DBNEWID is completed
  • ora-06129 : NETTCP: unable to transfer socket ownership to ORASRV
  • ora-13525 : error with computing space usage for sysaux occupant
  • ora-07339 : spcre: maximum number of semaphore sets exceeded.
  • ora-09261 : spdcr: error creating detached (background) process
  • ora-39139 : Data Pump does not support XMLSchema objects. string will be skipped.
  • ora-07253 : spdes: semctl error, unable to destroy semaphore set.
  • ora-22609 : error string during initialization of FDO
  • ora-29337 : tablespace 'string' has a non-standard block size (string)
  • ora-13516 : AWR Operation failed: string
  • ora-00956 : missing or invalid auditing option
  • ora-06701 : TLI Driver: incorrect number of bytes written
  • ora-14323 : cannot add partition when DEFAULT partition exists
  • ora-29279 : SMTP permanent error: string
  • ora-06315 : IPA: Invalid connect string
  • ora-38439 : invalid operation "string"
  • ora-25305 : enqueue failed, expiration must be zero for queue string.string
  • ora-38760 : This database instance failed to turn on flashback database
  • ora-02274 : duplicate referential constraint specifications
  • ora-39087 : directory name string is invalid
  • ora-23407 : object name string must be shaped like "schema"."object" or "object"
  • ora-06779 : TLI Driver: error reading ccode
  • ora-09740 : slsget: cannot get virtual memory region statistics.
  • ora-02270 : no matching unique or primary key for this column-list
  • ora-01228 : SET DATABASE option required to install seed database
  • 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.