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 : 29-06-2017

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

  • ora-19258 : XQ0038 - unsupported or duplicate default collation specified
  • ora-39130 : Object type string not imported. Base object name conflicts with the master table
  • ora-14515 : only one aubpartition name can be specified
  • ora-31115 : XDB configuration error: string
  • ora-31505 : cannot alter or drop predefined change set
  • ora-02074 : cannot string in a distributed transaction
  • ora-02805 : Unable to set handler for SIGTPA
  • ora-26501 : RepAPI operation failure
  • ora-19233 : XQ0013 - invalid pragma
  • ora-10931 : trace name context forever
  • ora-23490 : extension request "string" with status "string" not allowed in this operation
  • ora-15024 : discovered duplicately numbered ASM disk string
  • ora-29341 : The transportable set is not self-contained
  • ora-39314 : call to DBMS_SCHEMA_COPY.SYNC_CODE is not legal
  • ora-19041 : Comment data cannot contain two consecutive '-'s
  • ora-12809 : cannot set string_INSTANCES when mounted in exclusive mode
  • ora-39206 : A parallel degree of string is invalid.
  • ora-32139 : Cannot write to the stream
  • ora-16766 : Redo Apply unexpectedly offline
  • ora-02460 : Inappropriate index operation on a hash cluster
  • ora-03247 : Invalid block number specified
  • ora-12425 : cannot apply policies or set authorizations for system schemas
  • ora-10918 : TABLESPACE GROUP name cannot be the same as tablespace name
  • ora-07700 : sksarch: interrupt received
  • ora-38737 : Expected sequence number string doesn't match string
  • ora-01614 : instance string (thread string) is busy - cannot enable
  • ora-32146 : Cannot perform operation on a null date
  • ora-01900 : LOGFILE keyword expected
  • ora-12027 : duplicate filter column
  • ora-24070 : cannot upgrade queue table string while it is being downgraded
  • 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.