ORA-26690: datatype not supported at non-Oracle system

Cause : One of the columns of the LCR being applied was of a datatype not supported by either the target non-Oracle system or by the Oracle transparent gateway through which the apply is being done.

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

Do not apply data of this type. If possible, filter out columns containing such datatypes before applying.

update : 26-05-2017

ORA-26690 - datatype not supported at non-Oracle system
ORA-26690 - datatype not supported at non-Oracle system

  • ora-28030 : Server encountered problems accessing LDAP directory service
  • ora-36841 : (XSLMGEN11) Dimension string.string!string was not found
  • ora-12007 : materialized view reuse parameters are inconsistent
  • ora-15073 : diskgroup string is mounted by another ASM instance
  • ora-12058 : materialized view cannot use prebuilt table
  • ora-07236 : slemop: open error.
  • ora-30355 : materialized view container does not exist
  • ora-13530 : invalid TOPNSQL string, must be in the range (string, string)
  • ora-08455 : syntax error in CURRENCY SIGN environment clause
  • ora-22809 : nonexistent attribute
  • ora-16598 : Data Guard broker detected a mismatch in configuration
  • ora-32609 : missing REFERENCE keyword in MODEL clause
  • ora-19609 : %s is from different backup set: stamp string count string
  • ora-07637 : smsdbp: buffer protect option not specified when sga created
  • ora-15121 : ASM file name 'string' contains an invalid diskgroup name
  • ora-14135 : a LOB column cannot serve as a partitioning column
  • ora-22998 : CLOB or NCLOB in multibyte character set not supported
  • ora-19696 : control file not found in backup set
  • ora-30440 : can't fast refresh;refresh complete or set event 30441 for partial refresh
  • ora-33217 : (CINSERT20) Custom member values cannot be added to concat dimension workspace object, or to any of its bases, because it is not defined as UNIQUE.
  • ora-19930 : file string has invalid checkpoint SCN string
  • ora-10926 : trace name context forever
  • ora-22618 : attribute is a BAD NULL in the image handle
  • ora-08179 : concurrency check failed
  • ora-19690 : backup piece release string incompatible with Oracle release string
  • ora-01338 : Other process is attached to LogMiner session
  • ora-12153 : TNS:not connected
  • ora-02723 : osnpui: cannot send break signal
  • ora-07280 : slsget: unable to get process information.
  • ora-30333 : dimension 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.