UTF-8 Support for P6 EPPM Web and P6 Professional When Using the Migrate Utlity and MS SQL Server (Doc ID 2982261.1)

Last updated on DECEMBER 27, 2023

Applies to:

Symptoms

ACTUAL BEHAVIOR

After migrating an Oracle database to a SQL Server database, using the migrate utility, P6 Professional is still attempting to import text into the WBS Memo or Task Memo fields as UTF-8 as it is supported using the client.

The issue occurs when a user attempts to add NEW P6 Memo fields with UTF-8 Code.
This works with Oracle DB, but, not with a MS SQL server DB.
The MS SQL server collation (SQL_Latin1_General_CP1_CI_AS) is not a UTF-8 compatible collation.
The column types for the memo fields (table: wbsmemo, column: wbs_memo) or (table: taskmemo, column: task_memo) is set to "text", which according to MS documentation, does not support UTF-8 either.

When viewed on the web or in reports, it looks garbled. Additionally, if using web to modify the text, it permanently garbles the text. For example:
你好 P6!
olá P6!

In P6 Web it appears as:
 ¿ ä½ å¥½
P6!
olá P6!

When adding a new line ("Hi P6") in P6 Web and save it and re-read it in P6 Professional it shows:
 ¿ ä½ å¥½
P6!

olá P6!
Hi P6

EXPECTED BEHAVIOR

Fix the utility to convert a MS SQL Database to use UTF-8.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.