ORA-22999: CLOB or NCLOB data may have been corrupted
Answer / guest
Cause: CLOB or NCLOB contains invalid character data. One
possible cause is that the wrong csid was specified for the
external file when calling DBMS_LOB.LOADCLOBFROMFILE or
DBMS_XSLPROCESSOR.READ2CLOB to load CLOB or NCLOB data from
external files.
Action: Reload the CLOB/NCLOB data with the correct csid
specified for the external file.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
QSM-01017: aggregate argument cannot be converted to canonical form
ORA-39099: cannot create index for "string" on master table string
LSX-00011: internal error: ~s
ORA-28026: user with same external name already exists
RMAN-08582: channel string: starting archive copy
ORA-03234: unable to extend index string.string subpartition string by string in tablespace string
DRG-10847: catsearch requires prefix index for this type of queries
NID-00422: Change of database ID failed during validation - database is intact.
ORA-39060: table(s) dropped because of conflict with master table
ORA-36806: (XSTBLFUNC03) The OLAP_TABLE function refers to an invalid ADT attribute: string.
ORA-14085: partitioned table cannot have column with LONG datatype
ORA-28611: bitmap index is corrupted - see trace file for diagnostics