Oracle Database - Standard Edition - Version 184.108.40.206 to 220.127.116.11 [Release 8.1.7 to 11.2] Oracle Database - Enterprise Edition - Version 18.104.22.168 to 22.214.171.124 [Release 8.1.7 to 11.2] 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.
***Checked for relevance on 13-Sep-2016***
To install Csscan please see: <Note 458122.1> Installing and Configuring Csscan in 8i and 9i (Database Character Set Scanner) <Note 745809.1> Installing and configuring Csscan in 10g and 11g (Database Character Set Scanner)
For 8i and 9i please do install Csscan version 1.2 , do not use the old csscan versions included in 8i/9i .
The Csscan tool analyzes the code points in the database and verifies that they are known in the source the database characterset and known in the target database characterset. The output of the Csscan utility is vital to determining the health of the data in the database, and this becomes especially crucial when changing charactersets, as well as during import and export operations or database link transfers when source and target database differ in characterset. Knowing what the Csscan output shows, and what it means and it's limits helps you to ensure the integrity of the data.
Please note that this note documents csscan output. Csscan is used in the step by step guides on changing the NLS_CHARACTERSET like <note 260192.1> Changing the NLS_CHARACTERSET to AL32UTF8 / UTF8 (Unicode) , a list of other guides can be found in <note 225912.1> Changing the Database Character Set ( NLS_CHARACTERSET ) .
When using the new DMU (Database Migration Assistant for Unicode ) tool it is not needed to run csscan (but csscan might be used along side it , if required) and DMU does not use Csscan results or csalter. The 2 tools do the same (characterset conversion) but are not depending on each other. For more information on DMU please see <Note 1272374.1> The Database Migration Assistant for Unicode (DMU) Tool. From Oracle 12c onwards, the DMU will be the only tool available to migrate the NLS_CHARACTERSET.
For all DBAs performing a characterset conversion, import/export between databases with different charactersets, and those who wish to learn more about Csscan output. It covers the basic conventions of the output files, what they mean, and what can be done to resolve the different scenarios that can arise.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!