ORA-08230: smscre: failed to allocate SGA

Cause : The n_core system call failed, maybe due to insufficient memory.

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

Specify a smaller number of buffers. Check INIT.ORA parameters.

update : 23-09-2017
ORA-08230

ORA-08230 - smscre: failed to allocate SGA
ORA-08230 - smscre: failed to allocate SGA

  • ora-13851 : Tracing for client identifier string is already enabled
  • ora-30439 : refresh of 'string.string' failed because of string
  • ora-12997 : cannot drop primary key column from an index-organized table
  • ora-01334 : invalid or missing logminer dictionary processes context
  • ora-01862 : the numeric value does not match the length of the format item
  • ora-06903 : CMX: cannot read transport address of remote application
  • ora-13825 : missing SQL statement text for create SQL profile
  • ora-22318 : input type is not an array type
  • ora-30567 : name already used by an existing log group
  • ora-24170 : %s.string is created by AQ, cannot be dropped directly
  • ora-30516 : database role change triggers cannot have BEFORE type
  • ora-33449 : (ESDREAD17) Discarding compiled code for workspace object because the partition method or partition dimension of number has changed since it was compiled.
  • ora-12096 : error in materialized view log on "string"."string"
  • ora-26030 : index string.string had string partitions made unusable due to:
  • ora-12154 : TNS:could not resolve the connect identifier specified
  • ora-09262 : spdde: error terminating detached (background) process
  • ora-30374 : materialized view is already fresh
  • ora-29387 : no top-plans found in the pending area
  • ora-39304 : conflicting changes to object "string" : string
  • ora-19924 : there are no row with id string
  • ora-34346 : (MXDSS04) The string analytic workspace cannot be detached.
  • ora-13867 : Database-wide SQL tracing is already enabled
  • ora-38460 : filtering based on datatype "string" not supported for XML Tags
  • ora-16258 : marking index unusable due to a constraint violation
  • ora-15163 : cluster not in rolling downgrade
  • ora-01166 : file number string is larger than string (string)
  • ora-12537 : TNS:connection closed
  • ora-02286 : no options specified for ALTER SEQUENCE
  • ora-22612 : TDS does not describe a collection TDS
  • ora-29250 : Invalid index specifed in call to dbms_sql.bind_array
  • 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.