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 : 25-06-2017
ORA-26699

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

  • ora-02065 : illegal option for ALTER SYSTEM
  • ora-38705 : Expected block size string does not match string in log header.
  • ora-36400 : (XSSPROP02) workspace object is not a valid variable name.
  • ora-25409 : failover happened during the network operation,cannot continue
  • ora-12537 : TNS:connection closed
  • ora-28671 : UPDATE BLOCK REFERENCES may not be used on a partitioned index as a whole
  • ora-32002 : cannot create SPFILE already being used by the instance
  • ora-28544 : connect to agent failed, probable Net8 administration error
  • ora-28335 : referenced or referencing FK constraint column cannot be encrypted
  • ora-26528 : local store callback proc phase failed for 'string.string'
  • ora-09291 : sksachk: invalid device specified for archive destination
  • ora-31108 : Action failed as resource string is locked
  • ora-13786 : missing SQL text of statement object "string" for tuning task "string"
  • ora-33074 : (XSAGDNGL36) In AGGMAP workspace object, the offset number is not a valid offset into dimension workspace object.
  • ora-01187 : cannot read from file string because it failed verification tests
  • ora-28535 : invalid Heterogeneous Services context
  • ora-15059 : invalid device type for ASM disk
  • ora-28267 : Invalid NameSpace Value
  • ora-40207 : duplicate or multiple function settings
  • ora-26099 : direct path context is already prepared
  • ora-25114 : invalid file number specified in the DUMP DATAFILE/TEMPFILE command
  • ora-04031 : unable to allocate string bytes of shared memory ("string","string","string","string")
  • ora-02330 : datatype specification not allowed
  • ora-24419 : Proxy sessions are not supported in this mode.
  • ora-19552 : device type string is invalid
  • ora-06815 : TLI Driver: could not link SPX and IPX streams
  • ora-16655 : specified target standby database invalid
  • ora-23348 : cannot replicate procedure string; only IN parameters supported
  • ora-24418 : Cannot open further sessions.
  • ora-30400 : identical JOIN KEY clauses
  • 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.