ORA-26689: column datatype mismatch in LCR

Cause : The datatypes of columns in the LCR are not the same as the datatypes in the database object.

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

Alter the database object.

update : 28-04-2017

ORA-26689 - column datatype mismatch in LCR
ORA-26689 - column datatype mismatch in LCR

  • ora-24812 : character set conversion to or from UCS2 failed
  • ora-19509 : failed to delete sequential file, handle="string", parms="string"
  • ora-37157 : MDX syntax error was found in MDX query string but error text was missing
  • ora-38473 : cannot drop a type used for Expression Filter attribute set
  • ora-02361 : error while attempting to allocate number bytes of memory
  • ora-07718 : sksafre: error freeing memory
  • ora-38753 : Cannot flashback data file string; no flashback log data.
  • ora-36652 : (XSDUNION11) workspace object is not a string type dimension.
  • ora-25964 : column type incompatible with join column type
  • ora-19012 : Cannot convert XML fragment to the required datatype
  • ora-02289 : sequence does not exist
  • ora-02399 : exceeded maximum connect time, you are being logged off
  • ora-29507 : query derived from USING clause found zero or many rows
  • ora-00395 : online logs for the clone database must be renamed
  • ora-16762 : invalid database state
  • ora-30371 : column cannot define a level in more than one dimension
  • ora-13004 : the specified buffer size is invalid
  • ora-12921 : database is not in force logging mode
  • ora-26705 : cannot downgrade capture process after Streams data dictionary has been upgraded
  • ora-22063 : reading negative value [string] as unsigned
  • ora-39102 : Timeout before master process string finished initialization. Master error:
  • ora-00221 : error on write to control file
  • ora-30962 : inconsistent ODCI input arguments
  • ora-32109 : invalid column or parameter position
  • ora-06907 : CMX: error during connect confirmation
  • ora-13016 : specified topology [string] is invalid
  • ora-28663 : Logging/Nologging attribute can not be specified in the statement ALTER TABLE ADD OVERFLOW
  • ora-19320 : Host name not specified in HTTP URL
  • ora-27376 : event condition cannot be NULL
  • ora-13268 : error obtaining dimension from USER_SDO_GEOM_METADATA
  • 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.