My Oracle Support Banner

SAXParseException when Starting the Workspace after Migration (Doc ID 1286965.1)

Last updated on AUGUST 06, 2018

Applies to:

Oracle Business Process Management Suite - Version 10.3.2 and later
Information in this document applies to any platform.

Symptoms

After migrating a 5.7 or 6.0.x ALI environment to 10.3.x WCI environment, the workspace startup throws a SAXParseException with the following stack trace

Caused by: An invalid XML character (Unicode: 0x4) was found in the CDATA section.
fuego.papi.OperationRuntimeException: Runtime operation error.
at fuego.papi.impl.view.DirectoryViewLoader.buildView(DirectoryViewLoader.java:79)
at fuego.papi.impl.view.DirectoryViewLoader.loadOrganizationalViews(DirectoryViewLoader.java:126)
at fuego.view.mgmt.ViewManager.loadOrganizationalViews(ViewManager.java:142)
at fuego.papi.impl.view.ViewManager.loadOrganizationalViews(ViewManager.java:321)
at fuego.papi.impl.ProcessServiceImpl.startUpdater(ProcessServiceImpl.java:2174)
at fuego.papi.impl.ProcessServiceImpl.startUpdater(ProcessServiceImpl.java:2146)
at fuego.papi.impl.ProcessServiceImpl.startUpdater(ProcessServiceImpl.java:698)
at fuego.workspace.WorkspaceEnvironment.initPAPI(WorkspaceEnvironment.java:461)
at fuego.workspace.WorkspaceEnvironment.initialize(WorkspaceEnvironment.java:142)
at fuego.workspace.WorkspaceEnvironment.<init>(WorkspaceEnvironment.java:84)

Changes

Migration from a BPM 5.7 or 6.0.x ALI environment to 10.3 WCI environment using the Migration document

Cause

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
Symptoms
Changes
Cause
Solution
References


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.