Issues Using Hyperion Planning after Applying EPM System Patch Set Update (PSU) 22.214.171.124.500
(Doc ID 1640411.1)
Last updated on JULY 09, 2019
Applies to:Hyperion Planning - Version 126.96.36.199.000 and later
Information in this document applies to any platform.
After applying the 188.8.131.52.500 EPM System Patch Set Update (PSU): 17529887 which is a combined EPM patch that includes Planning 184.108.40.206.500, the following issues have been observered:
- Planning cannot be accessed via Workspace and the following error is found in the Planning0.log file:
<Notice> <Diagnostics> <xxx> <Planning0> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <
> <> <> <1402564062723> <BEA-320068> <Watch 'UncheckedException' with severity 'Notice' on server 'Planning0' has triggered at 12-Jun-2014 10:07:42 o'clock BST. Notification details
WatchRule: (SEVERITY = 'Error') AND ((MSGID = 'WL-101020') OR (MSGID = 'WL-101017') OR (MSGID = 'WL-000802') OR (MSGID = 'BEA-101020') OR (MSGID = 'BEA-101017') OR (MSGID = 'BEA-000802'))
WatchData: DATE = 12-Jun-2014 10:07:42 o'clock BST SERVER = Planning0 MESSAGE = [ServletContext@824802702[app:PLANNING module:HyperionPlanning path:/HyperionPlanning spec-version:2.5 version:220.127.116.11]] Servlet failed with Exception
java.lang.RuntimeException: Your session has timed out or was terminated by the application owner or an administrator. Please log on again.
- No forms are visible in the Planning application.
- Attempting to export Planning applications using LCM results in the following error:
Source: D02CONS (Application) Destination: HP-D02CONS (File System)
EPMLCM-14000: Error reported from Hyperion Planning.
/Configuration/Adhoc Options:- Error loading objects from data source: java.sql.SQLException: [FMWGEN][SQLServer JDBC Driver][SQLServer]The multi-part identifier "o1.object_id" could not be bound.
/Relational Data/Tablet Access:- Error loading objects from data source: java.sql.SQLException: [FMWGEN][SQLServer JDBC Driver][SQLServer]The multi-part identifier "o1.object_id" could not be bound.
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