A Specific User Cannot Access Essbase Even After Deleting and Recreating the User
(Doc ID 1365000.1)
Last updated on SEPTEMBER 24, 2019
Applies to:Hyperion Planning - Version 184.108.40.206.00 to 220.127.116.11.000 [Release 11.1]
Information in this document applies to any platform.
A specific user cannot access Essbase despite having the correct provisioning and permissions. Other users with the same security settings are unaffected.
Deleting and recreating the affected user does not resolve the problem.
The exact symptoms vary according to how Essbase is being accessed. For instance, the user may see an error when using Ad Hoc grids in Smart View.
When a specific user "userX" logs into Smart View and tries to access the "App1" application they receive the following error in a popup window:
Cannot open cube view. Essbase Error(1054060): Essbase failed to select application App1, because userX@Native Directory is not completely provisioned by Planning.
After dismissing the error message, right-clicking on the application in the Smart View pane in Excel and choosing "Ad Hoc Analysis" throws the same error.
Provisioning a new user "userY" with the same roles and permissions works correctly. Only "userX" is affected.
Deprovisioning and/or deleting "userX" and reprovisioning/recreating them does not resolve the problem.
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