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 : 25-04-2017

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

  • ora-39092 : unable to set SCN metadata for object "string.string" of type string
  • ora-28102 : policy does not exist
  • ora-09201 : sfcopy: error copying file
  • ora-02174 : Missing required thread number
  • ora-32821 : subscriber queue and exception queue must have same payload type
  • ora-40252 : no target values were found
  • ora-26673 : duplicate column name string
  • ora-32501 : Writing SGA to file failed
  • ora-36761 : (XSLANGDM01) Analytic workspace string already contains a dimension (%J) with the string property.
  • ora-12318 : database (link name string) is already mounted
  • ora-10941 : trace name context forever
  • ora-02091 : transaction rolled back
  • ora-12825 : explicit degree of parallelism must be specified here
  • ora-33022 : (XSAGDNGL10) The measure dimension workspace object must be a TEXT or ID base dimension that does not dimension AGGMAP workspace object, but is in the same analytic workspace.
  • ora-02251 : subquery not allowed here
  • ora-14032 : partition bound of partition number string is too high
  • ora-13124 : unable to determine column id for column string
  • ora-24412 : Cannot reinitialize non-existent pool
  • ora-10580 : Can not modify datafile header during test recovery
  • ora-08313 : sllfop: could not allocate buffers
  • ora-09793 : szguns: length of user name is greater than buffer.
  • ora-12014 : table 'string' does not contain a primary key constraint
  • ora-23369 : value of "string" argument cannot be null
  • ora-00302 : limit of string logs exceeded
  • ora-36258 : (XSAGINFO00) When the AGGMAPINFO function is called, workspace object must be an AGGMAP.
  • ora-16621 : database name for ADD DATABASE must be unique
  • ora-01540 : tablespace 'string' is not offline
  • ora-00489 : ARB* process terminated with error
  • ora-27250 : OS system call failure
  • ora-07584 : spdcr: invalid value for ORA_sid_(proc_)PQL$_item
  • 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.