After Migrating From An Oracle Database To SQL Server, Unicode Characters (Which Were Stored In Oracle Varchar2 datatype and migrated to SQL Server Varchar datatype) Are Lost
(Doc ID 2410073.1)
Last updated on JULY 25, 2019
Applies to:Primavera P6 Enterprise Project Portfolio Management - Version 188.8.131.52 and later
Information in this document applies to any platform.
When attempting to migrate a P6 EPPM schema from Oracle Database to a SQL Server database, any unicode characters which are stored in an Oracle varchar2 datatype field will not migrate correctly to the associated SQL Server field causing a loss of all unicode symbols in the migration.
For example, if a project ID (project.proj_short_name) contains Chinese characters in an Oracle Database, and the schema is migrated to SQL Server, all the unicode characters in the project.proj_short_name field will be lost.
When migrating a P6 EPPM schema from Oracle Database which contains unicode characters in varchar2 datatype fields, to a SQL Server database, for the unicode characters to be retained in the migration.
STEPS TO REPRODUCE
- Create a P6 EPPM Oracle Database
- Connect to the database and change the project ID to Chinese characters
- Execute migrate.bat/.sh to move the Database from Oracle to SQL Server
- Connect to the migrated database and confirm the unicode characters are lost
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