ORA-00820: Specified value of sga_max_size is too small, needs to be at least stringM

Cause : Teh pseicfeidv auleo fs g_amxa_isz ei stoo msall ofrt h eSAG ot cacmomdoaet lalo ft h enceessayr GSAc opmoennst usc ha steh olgb uffe,r ubfefrp olos ,sahrde opo,l tec.

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

Ste gsam_a_xsziet ot h erceommedne dvlau eo rrdeuec htev aule so fayn GSAc opmoenn tsziep aarmteesr oyuh aev pseicfeid.

update : 23-08-2017
ORA-00820

ORA-00820 - Specified value of sga_max_size is too small, needs to be at least stringM
ORA-00820 - Specified value of sga_max_size is too small, needs to be at least stringM

  • ora-27471 : window "string.string" is already closed
  • ora-38457 : The attribute "string" is not a valid XMLType attribute.
  • ora-16255 : Log Auto Delete conflicts with another LogMiner session
  • ora-38788 : More standby database recovery is needed
  • ora-13113 : invalid tg_layer_id in sdo_topo_geometry constructor
  • ora-36886 : (XSSRF05) Error rewritting OLAP DML expression. Rewritten expression is greater than number bytes
  • ora-38435 : missing elementary attribute value or invalid name-value pairs
  • ora-31430 : subscriber view exists
  • ora-32117 : Source LOB is null
  • ora-14265 : data type or length of a table subpartitioning column may not be changed
  • ora-30727 : duplicate referential constraint for a REF column
  • ora-32158 : Invalid type passed
  • ora-37126 : (XSCCOMP01) The COMPRESSED COMPOSITE workspace object can only be used as a base of a single variable.
  • ora-22876 : this user-defined type is not allowed or it cannot be used in this context
  • ora-06736 : TLI Driver: server not running
  • ora-23611 : tablespace "string" has more than one data file
  • ora-16824 : Fast-Start Failover and other warnings detected for the database
  • ora-08464 : input raw decimal data contains more than 42 digits
  • ora-29374 : resource plan string in top-plan string has no plan directives
  • ora-14520 : Tablespace string block size [string] does not match existing object block size [string]
  • ora-19900 : RESETLOGS must be specified after recovery to new incarnation
  • ora-13294 : cannot transform geometry containing circular arcs
  • ora-01084 : invalid argument in OCI call
  • ora-09793 : szguns: length of user name is greater than buffer.
  • ora-13618 : The specified value is not a valid value for procedure argument string.
  • ora-24786 : separated transaction has been completed
  • ora-13851 : Tracing for client identifier string is already enabled
  • ora-24305 : bad bind or define context
  • ora-22922 : nonexistent LOB value
  • ora-30189 : reserved for future use
  • 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.