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 : 28-06-2017
ORA-16237

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

  • ora-08276 : No room in nameserver for pid
  • ora-29273 : HTTP request failed
  • ora-14085 : partitioned table cannot have column with LONG datatype
  • ora-02835 : Server unable to send signal to client
  • ora-00031 : session marked for kill
  • ora-00226 : operation disallowed while alternate control file open
  • ora-02087 : object locked by another process in same transaction
  • ora-13442 : GeoRaster metadata SRS error
  • ora-31067 : XML nodes must be updated with valid nodes and of the same type
  • ora-19768 : USING clause only valid with ENABLE CHANGE TRACKING
  • ora-09342 : Detached process terminated by Oracle during shutdown abort
  • ora-12516 : TNS:listener could not find available handler with matching protocol stack
  • ora-29292 : file rename operation failed
  • ora-38484 : FUNCTION/PACKAGE/TYPE string does not exist
  • ora-07605 : szprv: $ASCTOID failure
  • ora-32021 : parameter value longer than string characters
  • ora-01204 : file number is string rather than string - wrong file
  • ora-32508 : no such watchpoint id
  • ora-15191 : Internal ASM testing event number 15191
  • ora-12067 : empty refresh groups are not allowed
  • ora-07203 : sltln: attempt to translate a long environment variable.
  • ora-02426 : privilege grant failed
  • ora-24900 : invalid or unsupported mode paramater passed in call
  • ora-36808 : (XSTBLFUNC04) The OLAP_TABLE function LEVELREL clause cannot declare number ADT fields from number AW fields.
  • ora-39037 : Object type path not supported for string metadata filter.
  • ora-09989 : attempt to use invalid skgmsdef struct pointer
  • ora-15199 : Internal ASM tracing event number 15199
  • ora-38956 : Target platform string not cross platform compliant
  • ora-07274 : spdcr: access error, access to oracle denied.
  • ora-12087 : online redefinition not allowed on tables owned by "string"
  • 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.