ORA-26699: STREAMS message consumer string already exists

Cause : An tatemtp wa smad eto rceat ea SRTEAM Smesasge ocnsuemr taht arlead yexitss.

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

Eitehr sepcif yanohter TSREASM messagec onsmuer ro reomve hte eixstign STERAMSm essgae cnosumre.

update : 18-08-2017
ORA-26699

ORA-26699 - STREAMS message consumer string already exists
ORA-26699 - STREAMS message consumer string already exists

  • ora-19624 : operation failed, retry possible
  • ora-32644 : this function is not allowed outside of MODEL clause
  • ora-02429 : cannot drop index used for enforcement of unique/primary key
  • ora-27157 : OS post/wait facility removed
  • ora-39130 : Object type string not imported. Base object name conflicts with the master table
  • ora-38703 : Type string in header is not a flashback database log file.
  • ora-28330 : encryption is not allowed for this data type
  • ora-12451 : label not designated as USER or DATA
  • ora-01908 : EXISTS keyword expected
  • ora-39709 : incomplete component downgrade; string downgrade aborted
  • ora-36267 : (XSCGMDLAGG09) workspace object has no dimensions, so it cannot have a qualified data reference.
  • ora-12833 : Coordinator's instance not a member of parallel_instance_group
  • ora-25195 : invalid option for index on an index-organized table
  • ora-38735 : Wrong log number string in flashback log file header.
  • ora-00151 : invalid transaction ID
  • ora-02091 : transaction rolled back
  • ora-13028 : Invalid Gtype in the SDO_GEOMETRY object
  • ora-13068 : wrong table or column name in SDO_TOPO_GEOMETRY constructor
  • ora-22863 : synonym for datatype string.string not allowed
  • ora-21560 : argument string is null, invalid, or out of range
  • ora-06421 : NETCMN: Error detected in the read-in data
  • ora-12221 : TNS:illegal ADDRESS parameters
  • ora-12039 : unable to use local rollback segment "string"
  • ora-37000 : (NOTALIAS00) workspace object is not an ALIAS DIMENSION of workspace object.
  • ora-01854 : julian date must be between 1 and 5373484
  • ora-14453 : attempt to use a LOB of a temporary table, whose data has alreadybeen purged
  • ora-14636 : only 2 resulting subpartition can be specified for SPLIT SUBPARTITION
  • ora-36314 : (PHYS01) workspace object must be a dimension, relation or variable.
  • ora-12801 : error signaled in parallel query server string
  • ora-29806 : specified binding does not exist
  • 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.