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 : 30-04-2017

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

  • ora-00724 : ALTER DATABASE CONVERT command has been de-supported
  • ora-30436 : unable to open named pipe 'string'
  • ora-28605 : bitmap indexes cannot be reversed
  • ora-10388 : parallel query server interrupt (failure)
  • ora-13347 : the coordinates defining an arc are not distinct
  • ora-06011 : NETASY: dialogue too long
  • ora-27014 : skgfqpini: translation error while expanding SS_UDMPDIR
  • ora-14165 : MODIFY DEFAULT ATTRIBUTES FOR PARTITION may not be combined with other operations
  • ora-30037 : Cannot perform parallel DML after a prior DML on the object
  • ora-26668 : STREAMS process string exists
  • ora-12521 : TNS:listener does not currently know of instance requested in connect descriptor
  • ora-13192 : failed to read number of element rows
  • ora-32163 : Method called on Invalid Environment type
  • ora-33262 : (DBERR01) Analytic workspace string does not exist.
  • ora-10566 : Test recovery has used all the memory it can use
  • ora-24152 : cannot drop evaluation context string.string with dependents
  • ora-28265 : NameSpace beginning with 'sys_' is not allowed
  • ora-01319 : Invalid Logminer session attribute
  • ora-09708 : soacon: failed to bind socket to port.
  • ora-38454 : attribute set not defined for the column being indexed
  • ora-06044 : NETDNT: connect failed, byte count quota exceeded
  • ora-01373 : insufficient memory for staging persistent LogMiner session
  • ora-02448 : constraint does not exist
  • ora-40216 : feature not supported
  • ora-30939 : Order violation: Element 'string' may not follow element 'string'
  • ora-30054 : invalid upper limit snapshot expression
  • ora-23484 : internal internet Application Server error: string
  • ora-32611 : incorrect use of MODEL CV operator
  • ora-00083 : warning: possibly corrupt SGA mapped
  • ora-19631 : archivelog record contains no file name
  • 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.