In this scenario, we have a Smart Materials database with the standard character set WE8ISO8859P1. This database will be upgraded to AL32UTF8.
-
The first step is to check the characters in the source database to see if they are convertible. For this step, use the Oracle tool csscan.
Before running this utility, you must install a set of tables and procedures that the CSMIG user owns. The script, csminst.sql, is either in the rdbms/admin directory under the Oracle Home or in the downloadable distribution. You must run this script using a DBA account (logged in with SYSDBA).
To run the check, use the following command:
csscan 'sys/manager@jap as sysdba' FULL=YES FROMCHAR=WE8ISO8859P1 TOCHAR=AL32UTF8 LOG=TO_AL32UTF8 CAPTURE=Y ARRAY=1000000 PROCESS=1
You get three files as a result:
-
TO_AL32UTF8.err with all conversion problems listed
-
TO_AL32UTF8.log as a log file, where all scanned tables are listed
-
TO_AL32UTF8.txt as a summary for the scan.
-
In the err file, all items are listed with detailed information for the specific ROWIDs. There are three possible results listed for an item:
-
convertible items: These items can be converted automatically by the import operation.
-
exceed column size: These items are too large for the target character set. In an import operation, rows with these items are not inserted into the database.
-
lossy conversion: These items do not have convertible characters.
For the ‘convertible items’, you do not have to do anything. The ‘exceed column size’ table items must be changed, as long as the size matches. This must be done manually and with respect to the column.
The ‘lossy conversion’ table items must also be changed manually.
Repeat the scan until all table columns are scanned as ‘convertible items’.
-
-
Create a new database with the Oracle character set AL32UTF8.
-
Export the full source database.
-
Import the dump into the new database.
-
Change the registry settings for the Oracle home of the database to