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-05-2017

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

  • ora-04093 : references to columns of type LONG are not allowed in triggers
  • ora-23540 : Redefinition not defined or initiated
  • ora-16565 : duplicate property, syntax error at "string"
  • ora-31669 : Worker process string violated startup protocol.
  • ora-24087 : Invalid database user string
  • ora-06517 : PL/SQL: Probe error - string
  • ora-31644 : unable to position to block number string in dump file "string"
  • ora-15082 : ASM failed to communicate with database instance
  • ora-30122 : value 'string' for 'string' must be between 'number' and 'number'
  • ora-32700 : error occurred in DIAG Group Service
  • ora-22292 : Cannot open a LOB in read-write mode without a transaction
  • ora-04096 : trigger 'string' has a WHEN clause which is too large, limit 2K
  • ora-03235 : max # extents (string) reached in table string.string subpartition string
  • ora-25263 : no message in queue string.string with message ID string
  • ora-00113 : protocol name string is too long
  • ora-30398 : illegal JOIN KEY clause
  • ora-02879 : sou2o: Could not gain access to protected memory
  • ora-32834 : Messaging Gateway agent user has not been set
  • ora-30968 : invalid XPATH or NAMESPACE option for XML Index
  • ora-01220 : file based sort illegal before database is open
  • ora-27143 : OS system call failure
  • ora-38724 : Invalid option to the FLASHBACK DATABASE command.
  • ora-25279 : dequeue as select not supported before 8.2
  • ora-38488 : attribute set already assigned to the column storing expressions
  • ora-31437 : duplicate change set string
  • ora-31002 : Path name string is not a container
  • ora-30772 : opaque types do not have default constructors
  • ora-25211 : invalid DELAY specified when using sequence deviation
  • ora-09204 : sfotf: error opening temporary file
  • 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.