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 : 28-07-2017

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

  • ora-33014 : (XSAGDNGL06) In AGGMAP workspace object, variable operator workspace object cannot be dimensioned by rollup dimension workspace object.
  • ora-07685 : sou2os: supervisor stack set error
  • ora-26061 : Concurrent direct unloads is not allowed.
  • ora-19901 : database needs more recovery to create new incarnation
  • ora-22812 : cannot reference nested table column's storage table
  • ora-25532 : MTTR specified is too large: string
  • ora-22922 : nonexistent LOB value
  • ora-38604 : FI including & excluding cursor item-id type must match input cursor item-id type
  • ora-39040 : Schema expression "string" must identify exactly one schema.
  • ora-31414 : error(s) occurred during change table advance
  • ora-16625 : cannot reach the database
  • ora-13195 : failed to generate maximum tile value
  • ora-08465 : input mask contains more than 32 characters
  • ora-31220 : DBMS_LDAP: PL/SQL - Invalid LDAP SSL wallet location.
  • ora-16814 : incorrect redo transport setting for AlternateLocation for standby database
  • ora-09843 : soacon: Archmon unable to create named pipe.
  • ora-27452 : %s is an invalid name for a database object.
  • ora-06119 : NETTCP: spurious client request
  • ora-16132 : An error occurred during activation of the standby.
  • ora-19584 : file string already in use
  • ora-27432 : step string does not exist for chain string.string
  • ora-16110 : user procedure processing of logical standby apply DDL
  • ora-00383 : DEFAULT cache for blocksize string cannot be reduced to zero
  • ora-14628 : specification of bounds is inconsistent with LIST method
  • ora-10561 : block type 'string', data object# string
  • ora-02039 : bind by value is not allowed for array type
  • ora-01783 : only one RECOVERABLE or UNRECOVERABLE clause may be specified
  • ora-22973 : size of object identifier exceeds maximum size allowed
  • ora-38420 : invalid stored attribute sub-expression: string
  • ora-13125 : partition key is already set
  • 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.