Assigning Essbase Filter to a Recreated Group Fails with "Warning: {Groupname} already exists in the security file." (Doc ID 1279712.1)

Last updated on JULY 29, 2016

Applies to:

Hyperion Essbase - Version 11.1.2.0.00 and later
Information in this document applies to any platform.
***Checked for relevance on 03-Jul-2012***

Symptoms

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"

For example:

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:

grant filter Demo.basic.filter1 to Group1;


5. Verify that this filter has been applied by logging onto EAS Console or Smart View with the external user ID.

In the Shared Services Console:

6. Delete Group1.

7. Create a new Group using the same name Group1.

8. Add the same external user to Group1 and provision (see step 5).

In the EAS Console MaxL Script Editor:

9. Assign filter1 to Group1 using this syntax:

grant filter Demo.basic.filter1 to Group1;


You will get the warning message.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms