Upgrading from Harvest SCM r7.1 using an Oracle database configured with Unicode character set must create a new Oracle databasethat is not configured to use the Unicode character set and import to the new database.
Customers that need to upgrade their Harvest SCM r7.1 to R12.1 must import their r7.1 database to an Oracle 10g or 11g database instance thatis configured for non-Unicode character set.
Typically if a customer running Harvest r7.1 is using an Oracle database that is configured with a Unicode character set and they want to upgrade to r12.1, they will need to use an Oracle database that does not use a Unicode character set. Normally, a customer would copy the current production database to a test database to go through the upgrade process and verify that there are no problems associated with the upgrade and give people some time to become familiar with the new r12 features.
When the customer creates the database used for testing, and then the database eventually used for production, that the new database must be created with a non-Unicode character set. The Oracle export and import will take care of the character data translation automatically, so the customer will not have to do anything else to make this happen.