ORA-16181: SGA specified for Logical Standby is too large

Cause : MAX_SAG is lrager tahn thel argero f iniitalizaiton paarmeter sSHARE_DPOOL_ISZE an dSGA_TRAGET.

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

Speciyf the avlue o fMAX_SAG to b eless htan th emaximmu of SAHRED_POOL_SIZ Eand SAG_TARGTE. Likley onl y75% o rlower.

update : 21-08-2017

ORA-16181 - SGA specified for Logical Standby is too large
ORA-16181 - SGA specified for Logical Standby is too large

  • ora-10617 : Cannot create rollback segment in dictionary managed tablespace
  • ora-24347 : Warning of a NULL column in an aggregate function
  • ora-14158 : too many subpartition descriptions
  • ora-31512 : name cannot contain double quotation marks
  • ora-30938 : No prefix defined for namespace 'string' (particle string)
  • ora-38440 : attribute set string does not exist
  • ora-19505 : failed to identify file "string"
  • ora-00437 : ORACLE feature is not licensed. Contact Oracle Corp. for assistance
  • ora-00030 : User session ID does not exist.
  • ora-21527 : internal OMS driver error
  • ora-13485 : error occurred during compression or decompression: string
  • ora-40106 : positive target value not specified for computing Lift
  • ora-30101 : unknown parameter name 'string'
  • ora-23425 : invalid materialized view identifier string
  • ora-16030 : session specific change requires a LOG_ARCHIVE_DEST_n destination
  • ora-22917 : use VARRAY to define the storage clause for this column or attribute
  • ora-01191 : file string is already offline - cannot do a normal offline
  • ora-12557 : TNS:protocol adapter not loadable
  • ora-24950 : unregister failed, registeration not found
  • ora-16535 : CRS is preventing execution of a broker operation
  • ora-22281 : cannot perform operation with an updated locator
  • ora-02203 : INITIAL storage options not allowed
  • ora-09284 : sllfop: cannot allocate read buffer
  • ora-15205 : requested mirror side unavailable
  • ora-10645 : Recursive Extension in SYSTEM tablespace during migration
  • ora-06913 : CMX: error during redirection of connection
  • ora-26571 : %s.string.string: number of arguments (string) does not match replication catalog
  • ora-06804 : TLI Driver: could not bind an IPX address at initialization
  • ora-15100 : invalid or missing diskgroup name
  • ora-39952 : only numbers can be specified as range values
  • 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.