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-06-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-33010 : (XSAGDNGL04) Relation workspace object is duplicated in the AGGMAP workspace object.
  • ora-02337 : not an object type column
  • ora-09719 : osncui: invalid handle.
  • ora-16543 : invalid request made to broker
  • ora-39079 : unable to enqueue message string
  • ora-25448 : rule string.string has errors
  • ora-00301 : error in adding log file 'string' - file cannot be created
  • ora-09301 : osncon: local kernel only supported in standard mode
  • ora-07230 : slemcr: fopen error, unable to open error file.
  • ora-16606 : unable to find property "string"
  • ora-00444 : background process "string" failed while starting
  • ora-12825 : explicit degree of parallelism must be specified here
  • ora-06921 : CMX: getdatmsg illegal datatype
  • ora-00325 : archived log for thread string, wrong thread # string in header
  • ora-25298 : Only immediage visibility mode supported for buffered message enqueue or dequeue
  • ora-01102 : cannot mount database in EXCLUSIVE mode
  • ora-12899 : value too large for column string (actual: string, maximum: string)
  • ora-12342 : open mounts exceeds limit set on the OPEN_MOUNTS parameter
  • ora-22347 : No changes to type specified for ALTER TYPE
  • ora-24407 : connection pool already exists
  • ora-02222 : invalid PCTINCREASE storage option value
  • ora-02243 : invalid ALTER INDEX or ALTER MATERIALIZED VIEW option
  • ora-21602 : operation does not support the specified typecode
  • ora-09292 : sksabln: unable to build archive file name
  • ora-12833 : Coordinator's instance not a member of parallel_instance_group
  • ora-19923 : the session for row with id string is not active
  • ora-08001 : maximum number of sequences per session exceeded
  • ora-13371 : invalid position of measure dimension
  • ora-39163 : A sample size of string is invalid.
  • ora-12216 : TNS:poorly formed PREFERRED_CMANAGERS addresses in TNSNAV.ORA
  • 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.