ORA-26671: maximum number of STREAMS processes exceeded

Cause : Cannot create additional STREAMS processes since the maximum number of STREAMS processes has been reached.

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

Remove existing STREAMS processes and retry the operation.

update : 23-07-2017
ORA-26671

ORA-26671 - maximum number of STREAMS processes exceeded
ORA-26671 - maximum number of STREAMS processes exceeded

  • ora-12569 : TNS:packet checksum failure
  • ora-00956 : missing or invalid auditing option
  • ora-02215 : duplicate tablespace name clause
  • ora-28155 : user 'string' specified as a proxy is actually a role
  • ora-12054 : cannot set the ON COMMIT refresh attribute for the materialized view
  • ora-26764 : invalid parameter "string" for local capture "string"
  • ora-39167 : Tablespace string was not found.
  • ora-40282 : invalid cost matrix
  • ora-29510 : name, string.string, already used by an existing object
  • ora-01876 : year must be at least -4713
  • ora-16513 : maximum requests exceeded
  • ora-13906 : The tablepace is not of the right type.
  • ora-01203 : wrong incarnation of this file - wrong creation SCN
  • ora-07497 : sdpri: cannot create trace file 'string'; errno = string.
  • ora-19686 : SPFILE not restored due to string
  • ora-02831 : Segment deallocation failed - empty segment list
  • ora-14634 : Subpartition descriptions cannot be specified during the SPLIT/MERGE of a partition of a Range-List partitioned table
  • ora-07597 : spguns: $GETJPIW failure
  • ora-19561 : %s requires a DISK channel
  • ora-00052 : maximum number of enqueue resources (string) exceeded
  • ora-02332 : cannot create index on attributes of this column
  • ora-16102 : remote information is not available on the specified primary
  • ora-14133 : ALTER TABLE MOVE cannot be combined with other operations
  • ora-02880 : smpini: Could not register PGA for protection
  • ora-36714 : (XSMXALLOC03) TARGETLOG variable workspace object must have the same data type as TARGET variable workspace object.
  • ora-01531 : a database already open by the instance
  • ora-25202 : invalid value NULL, string should be non-NULL
  • ora-13123 : invalid name specified
  • ora-36639 : (XSDUNION18) UNIQUE cannot be applied to this concat dimension because leaves workspace object and workspace object share the value number.
  • ora-24758 : not attached to the requested transaction
  • 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.