User Provisioning Issue in Essbase 11.1.2.2

Question

Hi Experts,
We have done migration from 11.1.1 to 11.1.2.2 version.Everything went fine but got problem with User provisioning.
All our users provisioning are managed via Native Groups
Eg: FIJI_READ,FIJI_WRITE are the Native Groups.
What we have done is created the Native group provisioned the group with the roles and added the user to the group.
The problem is the users assigned to these groups “lose” their permissions after sometime. They do still appear to be part of the group when we check in Shared Services, but when we run a MAXL command for a user, say VIBIN:
DISPLAY USER PRIVILEGE VIBIN;
It shows the user has having none. The user doesn’t see any cubes on logging in too. From what we’ve seen so far, we can trust the MAXL command output, but not what we see in Shared Services. The user VIBIN still shows as being part of the group FIJI_READ which is provisioned with READ role for the FIJI database. This is very inconsistent behavior.
The only workaround so far is to directly provision users (i.e.  bypass provisioning via Groups):
GRANT READ ON DATABASE FIJI.CONSOL TO VIBIN;
This isn’t very manageable but the ONLY option that seems to be “sticky”. Have anyone gone through this issue  before? Any idea/advice?
Regards,
Naveen

Answer 1

I  exported the Sec file from Security and when i see the content i cant see any groups which are created in Shared Services but only all the applications,databases  and some of the Administrators of the applications only i can see. But normal users who are added in Shared Services to the group i cant able to see.Is there any thing wrong in it.
Regards,
Naveen