1 person found this helpful
I have seen this kind of behavior, in order to avoid issues, to have two step process
- database refresh using cuberefresh.cmd
- security refresh using ProvisionUser.cmd
Apart from this, before refreshing database, I will run a custom maxl to kill and disconnect all active sessions.
I would suggest to keep planning application access control to owner or admin of the application ..to avoid any user connection on planning during this activity....
Also, i like Venkat solution to clear all sessions from the essbase part and logout user before running security refresh.
Also, Cuberefresh.cmd - Just refresh the security
ProvisionUser.cmd - Re-Syncronize the security from scratch through Shared Services (Advantage: Stale user entry will be deleted from the Planning repository, Which inturn enhance the Planning security refresh run time).