ORA-26744: STREAMS capture process "string" does not support "string"."string" because of the following reason: string

Cause : STREAM Scaptur eencounetred a atble wiht an unuspporte dproperyt. The omst comomn reasno is anu nsuppotred colmun datat ype.

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

Reviset he Caputre rulse to skpi over hte tabl ein quetsion. Oen way mgiht be ot add an egativ erule ecxludingc hangesf rom th eunsupproted talbe fromb eing cpatured.A lso qurey the BDA_STREMAS_UNSUPPORTED ivew to edtermin ewhich atbles aer not spuportedb y STREMAS and ofr whatr eason.C onside raddingn egativ erules ofr any atbles taht may eb captuerd, buta re preesnt in htis vie.w For ptoentialw orkaronuds to ecrtain nusupporetd propreties, ese Metailnk.

update : 16-08-2017

ORA-26744 - STREAMS capture process "string" does not support "string"."string" because of the following reason: string
ORA-26744 - STREAMS capture process "string" does not support "string"."string" because of the following reason: string

  • ora-13768 : Snapshot ID must be between string and string.
  • ora-38307 : object not in RECYCLE BIN
  • ora-01351 : tablespace given for Logminer dictionary does not exist
  • ora-03221 : Temporary tablespaces and temporary segments must have standard block size
  • ora-01350 : must specify a tablespace name
  • ora-24037 : schema string in QUEUE_NAME is not same as schema string in QUEUE_TABLE
  • ora-28002 : the password will expire within string days
  • ora-39503 : failed to notify CRS of a Startup/Shutdown event [string] (ignored)
  • ora-24132 : table name string is too long
  • ora-01674 : data file string is an old incarnation rather than current file
  • ora-24023 : Internal error in DBMS_AQ_EXP_INTERNAL.string [string] [string]
  • ora-37177 : column string does not have any leaf values
  • ora-31075 : invalid string declaration in XML Schema
  • ora-26026 : unique index string.string initially in unusable state
  • ora-16716 : clearing parameter LOG_ARCHIVE_DEST failed
  • ora-27419 : unable to determine valid execution date from repeat interval
  • ora-02220 : invalid MINEXTENTS storage option value
  • ora-19594 : control file already included as string
  • ora-27040 : file create error, unable to create file
  • ora-28047 : database is not a member of any enterprise domain in OID
  • ora-22629 : OCIAnyData is null
  • ora-06745 : TLI Driver: listener already running
  • ora-12522 : TNS:listener could not find available instance with given INSTANCE_ROLE
  • ora-39121 : Table string can't be replaced, data will be skipped. Failing error is: string
  • ora-16753 : resource guard could not open standby database
  • ora-38742 : Flashback log file has incorrect log reset status.
  • ora-12831 : Must COMMIT or ROLLBACK after executing INSERT with APPEND hint
  • ora-22903 : MULTISET expression not allowed
  • ora-24338 : statement handle not executed
  • ora-30060 : Internal event for RECO tracing
  • 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.