Hyperion Planning : Security Refresh Takes an Hour or Longer with Trace Level Logging set for Planning Web App
(Doc ID 2518170.1)
Last updated on SEPTEMBER 23, 2020
Applies to:Hyperion Planning - Version 18.104.22.168.000 and later
Information in this document applies to any platform.
The security filter refresh takes an hour or longer instead of couple of minutes previously with no major changes in security or number of users
The Hyperion Planning logging level was set to TRACE:32
NOTE: The Planning logging level are set in the following file, example from Windows enviroment below
The default level for epmhp-planning-handler is NOTIFICATION:1 as shown below.
<logger name='oracle.EPMHSP' level='NOTIFICATION:1' useParentHandlers='false'>
The loggin level was set to TRACE:32 as shown below
<logger name='oracle.EPMHSP' level='TRACE:32' useParentHandlers='false'>
NOTE: The epmhp-planning-handler sets the logging level for Planning_WebApp.log
The default location for Planning logs is. However if there multiple Planning servers the Planning JVM server names are Planning0, Planning1 etc
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