Deleting an Owner is Planning

Deleting an Owner is Planning

Joined: October 7th, 2008, 3:09 pm

October 7th, 2008, 3:11 pm #1

Recently our Senior Analyst left and we need to delete her from the system and reassign the owner status. Can someone help me with this, without having to retrieve her password?
Quote
Like
Share

Sini
Sini

October 7th, 2008, 6:00 pm #2

Its been a while doing this...but hope this works.

** First, make a backup copy of your planning repository DB.

---------------
On your Planning repository DB, Owner of an Planning App is identified as ROLE = "3" in HSP_USERS table.

SELECT *
FROM HSP_USERS
WHERE (ROLE = 3)

Running the above SQL, a single record "owner of the app" should show up which can be edited to say 0.

- Get the OBJECT_ID of the TO-BE new owner from:

SELECT *
FROM HSP_OBJECT
WHERE (OBJECT_NAME = 'TO_BE_OWNER')
** Note the OBJECT_ID

SELECT *
FROM HSP_USERS
WHERE (USER_ID = 'The object_id you got above')

Change the Role to 3

LOgin into that specific planning apps and confirm the change/...if looking good, do a refresh into Essbase.
Quote
Share

Anonymous
Anonymous

October 7th, 2008, 8:12 pm #3

Adding a string to original question that: When you do a security refresh it error's out saying that it cannot be succeed due to user ABC. The user ABC is no longer part of network but exist in the user list within planning.

How to overcome that
Quote
Share

Sini
Sini

October 7th, 2008, 11:18 pm #4

Steps involved in deleting the user from Hyperion Planning:

1. Locate the user in the shared service under the LDAP node.
Right click on the user-> Deprovision.
(This will take the access from the user after the refresh is done)

2. Do a security filter refresh from the planning.(Administration ->Manage database)

Note**: This will not delete the user from Essbase.

3. Go to EAS ->Essbase server-> Security -> Users
4. Delete the user from the users table in EAS.
5. Make sure all the user filters are deleted from specified applications
Application-> Database> Right Click ->Edit ->Filters

6. After deleting all the filters for the particular user from each application (if exists). The user needs to be deleted from each SQL Application database from the following tables:

HSP_OBJECT
HSP_USERS
HSP_ACCESS_CONTROL (if exists)

** This step will get rid off the problem while refreshing
com.hyperion.planning.HspRuntimeException: Failed to create Security Filters for the following users: rmadill, ccarlos, jwayland

7. The security filter for the user might still appear under the Administration -> Manage security filter list.
Once planning service is recycled the user filter will no longer appear under the security filter list.
Quote
Share

mark
mark

February 24th, 2011, 11:26 pm #5

that was very useful - much appreciated
Quote
Share

Uma Garg
Uma Garg

January 6th, 2012, 7:10 am #6

Steps involved in deleting the user from Hyperion Planning:

1. Locate the user in the shared service under the LDAP node.
Right click on the user-> Deprovision.
(This will take the access from the user after the refresh is done)

2. Do a security filter refresh from the planning.(Administration ->Manage database)

Note**: This will not delete the user from Essbase.

3. Go to EAS ->Essbase server-> Security -> Users
4. Delete the user from the users table in EAS.
5. Make sure all the user filters are deleted from specified applications
Application-> Database> Right Click ->Edit ->Filters

6. After deleting all the filters for the particular user from each application (if exists). The user needs to be deleted from each SQL Application database from the following tables:

HSP_OBJECT
HSP_USERS
HSP_ACCESS_CONTROL (if exists)

** This step will get rid off the problem while refreshing
com.hyperion.planning.HspRuntimeException: Failed to create Security Filters for the following users: rmadill, ccarlos, jwayland

7. The security filter for the user might still appear under the Administration -> Manage security filter list.
Once planning service is recycled the user filter will no longer appear under the security filter list.
Hi,

Thanks,These steps were really helpful,we did till EAS removal,however we were getting the error message.But after deleting from the sql scemas,we are not getting the error again.
Quote
Share


Confirmation of reply: