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 : 23-09-2017
ORA-26693

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-30117 : syntax error at 'string' at the start of input
  • ora-25300 : Cannot drop buffer for queue with buffered subscribers
  • ora-37136 : (XSCCOMP11) Cannot ROLLUP dimension workspace object which is a base of COMPRESSED COMPOSITE workspace object, use AGGREGATE instead.
  • ora-27413 : repeat interval is too long
  • ora-23321 : Pipename may not be null
  • ora-16243 : paging out string bytes of memory to disk
  • ora-09815 : File name buffer overflow
  • ora-01484 : arrays can only be bound to PL/SQL statements
  • ora-13356 : adjacent points in a geometry are redundant
  • ora-30347 : a table name is required to qualify the column specification
  • ora-31159 : XML DB is in an invalid state
  • ora-19031 : XML element or attribute string does not match any in type string.string
  • ora-32616 : missing DIMENSION BY keyword in MODEL clause
  • ora-26709 : Streams RFS restart
  • ora-06780 : TLI Driver: recv error code failed
  • ora-22625 : OCIAnyData is not well-formed
  • ora-00402 : database changes by release string cannot be used by release string
  • ora-29655 : USING clause is incompatible with its supertype
  • ora-02714 : osnpwr: message send failure
  • ora-01269 : Destination parameter string is too long
  • ora-14630 : subpartition resides in offlined tablespace
  • ora-22863 : synonym for datatype string.string not allowed
  • ora-12418 : user string not found
  • ora-38760 : This database instance failed to turn on flashback database
  • ora-08317 : sllfsk: Error seeking in file.
  • ora-04072 : invalid trigger type
  • ora-06907 : CMX: error during connect confirmation
  • ora-02465 : Inappropriate use of the HASH IS option
  • ora-10658 : Lob column to be shrunk is marked unused
  • ora-14277 : tables in EXCHANGE SUBPARTITION must have the same number of columns
  • 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.