Receiving Invalid Unicode Character Error in GRCM After Data Migration (Doc ID 1150416.1)

Last updated on NOVEMBER 03, 2014

Applies to:

Oracle Governance, Risk and Compliance Manager - Version 7.8 and later
Information in this document applies to any platform.
Checked for relevance on 03-Nov-2014

Symptoms

The following Exception is received when accessing risks in an MCL process container where the data was migrated in from another GRCM system:

Exception

OpenDocument Error encountered in "GetDocInfo" Error in "CheckStellentResponse": Invalid unicode character. in CMSDocument.OpenDocument: Login=user1 DocId=001015. in SoxDocument.Open

at SoxDocMgmt.SoxDocument.pOpen(String DocId, String& Document, OpenType Action, String MetaData, DocType DocumentType)
at SoxDocMgmt.SoxDocument.Open(String DocId, String& Document, OpenType Action, String MetaData, DocType DocumentType)
at SoxNav.Risk.Page_Load(Object sender, EventArgs e)



When running a Compare Report a similar error message was received:

Exception

OpenDocument Error encountered in "GetDocInfo" Error in "CheckStellentResponse": Invalid unicode character. in CMSDocument.OpenDocument: Login=user1 DocId=001015. in SoxDocument.Open

at SoxDocMgmt.SoxDocument.pOpen(String DocId, String& Document, OpenType Action, String MetaData, DocType DocumentType)
at SoxDocMgmt.SoxDocument.Open(String DocId, String& Document, OpenType Action, String MetaData, DocType DocumentType)
at SoxNav.ComparisonReport.CompareRisks(SoxDocument cur, SoxDocument prev)
at SoxNav.ComparisonReport.Page_Load(Object sender, EventArgs e)

Changes

A production system had all data migrated to a test system by Oracle Consulting Services.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms