Lossy conversion in data dictionary
595071Apr 22 2008 — edited Sep 5 2008I am converting my database from UTF8 to AL32UTF8, so was very surpised to see a lossy conversion in my data dictionary.
User : MDSYS
Table : SDO_COORD_OP_PARAM_VALS
Column: PARAM_VALUE_FILE
Type : CLOB
Number of Exceptions : 94
Max Post Conversion Data Size: 3246228
[Database Scan Parameters]
Parameter Value
------------------------------ ------------------------------------------------
CSSCAN Version v2.1
Instance Name test
Database Version 10.2.0.3.0
Scan type Full database
Scan CHAR data? YES
Database character set UTF8
FROMCHAR UTF8
TOCHAR al32utf8
Scan NCHAR data? NO
Array fetch buffer size 10240
Number of processes 3
Capture convertible data? NO
------------------------------ ------------------------------------------------
[Scan Summary]
Some character type data in the data dictionary are not convertible to the new character set
All character type application data remain the same in the new character set
[Data Dictionary Conversion Summary]
Datatype Changeless Convertible Truncation Lossy
--------------------- ---------------- ---------------- ---------------- ----------------
VARCHAR2 4,234,290 0 0 0
CHAR 1,102 0 0 0
LONG 141,788 0 0 0
CLOB 37,160 0 0 149
VARRAY 20,831 0 0 0
--------------------- ---------------- ---------------- ---------------- ----------------
Total 4,435,171 0 0 149
Total in percentage 99.997% 0.000% 0.000% 0.003%
The data dictionary can not be safely migrated using the CSALTER script
Any suggesstions.