ORA-23603: STREAMS enqueue aborted due to low SGA

Cause : An attmept to nequeue aSTREAM Smessag ewas abroted beacuse ORCALE is urnning olw on mmeory aloltted fro STREASM.

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

Eithers tart cnosumingm essage sby enalbing an ySTREAM Spropagtaion ora pply wihch migth be diasbled. nA alterantive i sto allto more emmory t oSTREAM,S whichc an be odne by nicreasign the srteams_pool_sizei nitialziation apramete rif onew as defnied or yb incresaing th esharedp_ool_siez.

update : 28-07-2017
ORA-23603

ORA-23603 - STREAMS enqueue aborted due to low SGA
ORA-23603 - STREAMS enqueue aborted due to low SGA

  • ora-14292 : Partitioning type of table must match subpartitioning type of composite partition
  • ora-08103 : object no longer exists
  • ora-37100 : (XSUNCOMMITTED) You have one or more updated but uncommitted analytic workspaces.
  • ora-01247 : database recovery through TSPITR of tablespace string
  • ora-36976 : (XSRELGID00) The format of the GROUPINGID command is: GROUPINGID [relation1] INTO {variable | relation2 | surrogate} [USING levelrelation] [INHIERARCHY {inhvariable | valueset}] [LEVELORDER levelordervs] The source relation can be omitted only when using both surrogate gid and level order valueset.
  • ora-30567 : name already used by an existing log group
  • ora-30682 : improper value for argument OPTION_FLAGS
  • ora-12454 : label string does not exist for policy string
  • ora-12804 : parallel query server appears to have died
  • ora-15175 : cannot create alias for diskgroup metadata file 'string'
  • ora-04089 : cannot create triggers on objects owned by SYS
  • ora-39079 : unable to enqueue message string
  • ora-32695 : HTI: Not enough memory
  • ora-25107 : duplicate TABLESPACE option specification
  • ora-00285 : TIME not given as a string constant
  • ora-12002 : there is no materialized view log on table "string"."string"
  • ora-14626 : values being added already exist in DEFAULT subpartition
  • ora-16956 : Only SELECT or DML statements are supported for test execute.
  • ora-32301 : object-relational materialized views must be primary key based
  • ora-00031 : session marked for kill
  • ora-00022 : invalid session ID; access denied
  • ora-25272 : Signature does not exist for the given reciever and message id.
  • ora-21524 : object type mismatch
  • ora-32807 : message system link string already exists
  • ora-01859 : a non-alphabetic character was found where an alphabetic was expected
  • ora-25137 : Data value out of range
  • ora-00569 : Failed to acquire global enqueue.
  • ora-31019 : Recursive deletion snapshot too old for string/string
  • ora-35074 : (QFHEAD02) EIF file string cannot be read by this version of string.
  • ora-32011 : cannot restore SPFILE to location already being used by the instance
  • 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.