Starting with Banner® 8, the entire database character set must be converted to UTF8. While the procedure is not
difficult, it is somewhat of a pain. This document goes over the steps...
1. Before starting, you will need to create two empty databases in UTF8 format. You can do so using the Java-based "Database Creation Assistant" (dbca) or do so by manually. BE SURE to create ALL the tablespaces which you have in your Banner Database, otherwise you will have problems in your import.
In this document, the Banner Database will be named PROD. The Two empty databases will be named UTF8a and UTF8b, respectively.
2. Cleanly shutdown, and then take a full export of your Banner PROD database. This database will most likely be in US7ASCII or WE8ISO8859P1 character set. You can do so using the export command as shown below:
ORACLE_SID=PROD ; export ORACLE_SID exp 'system/3. If the UTF8a or UTF8b databases are on separate servers, move the export file to that server using ftp or sftp. Perform the following grant on the SYSTEM account in the UTF8a database. At this point you are done with the PROD database.
' full=y buffer=100000 file=ban8.dmp log=prod_export.log
grant EXEMPT ACCESS POLICY to system;4. Import the PROD export file into the UTF8a database with the following command:
ORACLE_SID=UTF8a ; export ORACLE_SID imp 'system/manager' full=y buffer=100000 file=ban8.dmp log=ban8_import.logIn general, an import process will take 5-6 times as long as the export, so please be patient. Inspect the log file for any errors:
ORACLE_SID=UTF8a ; export ORACLE_SID expdp 'system/manager' full=y dumpfile=utf8a_dp.dmp logfile=ban8_dp_export.logUsually, the export file will be in the $ORACLE_HOME/admin/
NLS_LENGTH_SEMANTICS=CHARYou will need to restart the UTF8b database after setting this parameter.
ORACLE_SID=UTF8b ; export ORACLE_SID impdp 'system/manager' full=y dumpfile=utf8a_dp.dmp logfile=ban8_dp_import.log8. At this point, you are done. The new database will be called UTF8b.