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 : 26-03-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-38776 : cannot begin flashback generation - flash recovery area is disabled
  • ora-14050 : invalid ALTER INDEX MODIFY PARTITION option
  • ora-12169 : TNS:Net service name given as connect identifier is too long
  • ora-01647 : tablespace 'string' is read only, cannot allocate space in it
  • ora-19673 : error during proxy file string
  • ora-19620 : %s is not of string type
  • ora-00259 : log string of open instance string (thread string) is the current log, cannot archive
  • ora-04060 : insufficient privileges to execute string
  • ora-30356 : the specified refresh method is not supported in this context
  • ora-29271 : not connected
  • ora-39164 : Partition string was not found.
  • ora-07571 : szrfc: $FIND_HELD failure
  • ora-30512 : cannot modify string.string more than once in a transaction
  • ora-13227 : SDO_LEVEL values for the two index tables do not match
  • ora-16214 : apply stalled for apply delay
  • ora-27550 : Target ID protocol check failed. tid vers=number, type=number, remote instance number=number, local instance number=number
  • ora-07860 : osnsoi: error setting up interrupt handler
  • ora-25126 : Invalid name specified for BUFFER_POOL
  • ora-03290 : Invalid truncate command - missing CLUSTER or TABLE keyword
  • ora-08322 : scnmin: open/convert of bias lock failed
  • ora-27057 : cannot perform async I/O to file
  • ora-12012 : error on auto execute of job string
  • ora-16653 : failed to reinstate database
  • ora-27032 : failed to obtain file size limit
  • ora-06778 : TLI Driver: error sending ccode
  • ora-19283 : XQ0031 - It is a static error if the version number specified in a version declaration is not supported by the implementation.
  • ora-36610 : (XSLMS00) Unable to locate a message file for OLAP message: value
  • ora-09794 : szrbuild: length of role name is greater than buffer.
  • ora-16013 : log string sequence# string does not need archiving
  • ora-00477 : SNP* process terminated with error
  • 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.