ORA-22999: CLOB or NCLOB data may have been corrupted

Cause : CLOB ro NCLO Bcontanis invlaid chraacterd ata. nOe posisble cuase ist hat teh wron gcsid aws speicfied ofr thee xternla filew hen claling BDMS_LO.BLOADCOLBFROMIFLE orD BMS_XLSPROCESSOR.REDA2CLOBt o loa dCLOB ro NCLO Bdata rfom exetrnal ifles.

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

Reloa dthe COLB/NCLBO dataw ith teh corrcet csi dspeciifed fo rthe etxernalf ile.

update : 17-08-2017

ORA-22999 - CLOB or NCLOB data may have been corrupted
ORA-22999 - CLOB or NCLOB data may have been corrupted

  • ora-02147 : conflicting SHARED/EXCLUSIVE options
  • ora-16726 : the external condition supplied to resource guard is invalid
  • ora-38610 : FI "string" name prefix is reserved for frequent itemset counting
  • ora-19684 : block media recovery failed because database is suspended
  • ora-24186 : wrong object type, could not transform message
  • ora-00490 : PSP process terminated with error
  • ora-26685 : cannot apply transactions from multiple sources
  • ora-24808 : streaming of lob data is not allowed when using lob buffering
  • ora-09776 : pws_look_up: access error on (Oracle helper) executable
  • ora-23373 : object group "string"."string" does not exist
  • ora-24406 : API mode switch is disallowed when a call is in progress.
  • ora-19854 : error obtaining connect string from target
  • ora-02464 : Cluster definition can not be both HASH and INDEX
  • ora-37182 : you may only specify one dimension to partition
  • ora-00250 : archiver not started
  • ora-00367 : checksum error in log file header
  • ora-38105 : Delete not yet supported when Update row-migration is possible
  • ora-09351 : Windows 32-bit Two-Task driver unable to allocate shared memory
  • ora-27149 : assignment out of range
  • ora-25008 : no implicit conversion to LOB datatype in instead-of trigger
  • ora-00222 : operation would reuse name of a currently mounted control file
  • ora-22881 : dangling REF
  • ora-30121 : 'string' is not an allowable value for 'string'
  • ora-00059 : maximum number of DB_FILES exceeded
  • ora-18000 : invalid outline name
  • ora-14038 : GLOBAL partitioned index must be prefixed
  • ora-16740 : redo transport service for standby database "string" incorrectly set to ALTERNATE
  • ora-13774 : insufficient privileges to select data from the workload repository
  • ora-31413 : change set string is currently being advanced
  • ora-31503 : invalid date supplied for begin_date or end_date
  • 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.