Assigning Essbase Filter to a Recreated Group Fails with "Warning: <Groupname> already exists in the security file."
(Doc ID 1279712.1)
Last updated on MARCH 16, 2021
Applies to:Hyperion Essbase - Version 18.104.22.168.00 and later
Information in this document applies to any platform.
***Checked for relevance on 03-Jul-2012***
If a group has been provisioned for server and filter access to Essbase, deleted from Shared Services and then recreated with the same access, when using MaxL to assign the filter to the group it is failing with the following message:
"Warning: Group1 already exists in the security file. If this user/group was deleted from HSS, drop the user/group from ESSBASE by using the MAXL statement DROP [USER/GROUP] Native Directory FROM SECURITY_FILE"
In the Shared Services Console:
1. Create New NATIVE Group named Group1.
2. Add a user from your external provider (such as MSAD) to Group1.
3. Provision Group1 with server access for Essbase as well as a filter for Demo.Basic.
In the EAS Console MaxL Script Editor:
4. Assign filter1 to Group1 using this syntax:
You will get the warning message.
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