ORA-26693: STREAMS string process dropped successfully, but error occurred while dropping rule set string

Cause : An attmept to rdop an nuused rlue set afiled atfer dropping th eSTREAM Sproccess successfully.

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

Check xeistenc eof rul eset an dmanualyl drop fi necesasry.

update : 26-04-2017

ORA-26693 - STREAMS string process dropped successfully, but error occurred while dropping rule set string
ORA-26693 - STREAMS string process dropped successfully, but error occurred while dropping rule set string

  • ora-12723 : regular expression too complex
  • ora-02479 : error while translating file name for parallel load
  • ora-32139 : Cannot write to the stream
  • ora-35020 : (QFCHECK02) The analytic workspace and EIF file definitions of workspace object have mismatched dimensioning.
  • ora-30151 : File already exists
  • ora-16068 : redo log file activation identifier mismatch
  • ora-00297 : must specify RECOVER DATAFILE LIST before RECOVER DATAFILE START
  • ora-25192 : invalid option for an index-organized table
  • ora-12202 : TNS:internal navigation error
  • ora-26053 : Row was not loaded due to conversion error.
  • ora-01906 : BACKUP keyword expected
  • ora-28521 : no heterogeneous capability information available
  • ora-36885 : (XSSRF04) Error rewriting OLAP DML expression. Column name too big
  • ora-02471 : SYSDATE, UID, USER, ROWNUM, or LEVEL incorrectly used in hash expression.
  • ora-01669 : standby database control file not consistent
  • ora-14020 : this physical attribute may not be specified for a table partition
  • ora-09290 : sksaalo: error allocating memory for archival
  • ora-19224 : XP0004 - XQuery static type mismatch: expected - string got - string
  • ora-19259 : XQ0039 - duplicate parameter name string in function declaration
  • ora-36170 : (XSMXAGGR12) The data type of the WEIGHT workspace object must be numeric or BOOLEAN, not string.
  • ora-22316 : input type is not a collection type
  • ora-02333 : cannot create constraints on attributes of this column
  • ora-19509 : failed to delete sequential file, handle="string", parms="string"
  • ora-23393 : the user is already the propagator
  • ora-38904 : DML error logging is not supported for LOB column "string"
  • ora-30488 : argument should be a function of expressions in PARTITION BY
  • ora-03211 : The segment does not exist or is not in a valid state
  • ora-19011 : Character string buffer too small
  • ora-30490 : Ambiguous expression in GROUP BY ROLLUP or CUBE list
  • ora-13263 : column string in table string is not of type SDO_GEOMETRY
  • 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.