Csscan gives some incorrect lossy for BIG5 charactersets (ZHT16MSWIN950 , ZHT16HKSCS, ZHT16BIG5)
(Doc ID 1105724.1)
Last updated on JUNE 13, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 9.0.1.0 and laterOracle Database - Standard Edition - Version 9.0.1.0 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Information in this document applies to any platform.
Symptoms
NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data from the Oracle sample or bulit-in schema(s), Public Documentation delivered with an Oracle database product or other training material. Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner.
Csscan tags some rows as "Lossy" even if the actual codes are defined in the BIG5 (ZHT16MSWIN950 , ZHT16HKSCS, ZHT16HKSCS31, ZHT16BIG5) characterset.
Changes
Using Csscan before trying to change the ZHT16MSWIN950 , ZHT16HKSCS, ZHT16HKSCS31 or ZHT16BIG5 characterset to UTF8 or AL32UTF8 or doing a check ( FROMCHAR=TOCHAR ) on a BIG5 characterset database.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |