Hi,
Is there any way to track as to when the supervisor tried to access the supervisor and got locked. Is there any way to track using the IP address or so, as at my work place same supervisor id is used by three different supervisors and there is no way to find out who logged in as supervisor and locked the id. Is the IP address of the machine available in any of the repository tables. The businessobjects version used is 6.1b.
Thanks
Baazigar 
(BOB member since 2004-06-10)
Business Objects themselves probably won’t help you because it sounds like you’re contravening their licence agreement - you should have a separate supervisor licence for each named supervisor. BO itself won’t be able to tell you but the underlying database log file might.
The ip address will not be logged by BO, but you could create a trigger against the table that stores the users details in the repo (I dont have the name to hand but it could be OBJ_M_ACTOR or something like that).
When a user gets locked out a flag in this table is updated. To get the ipadress you will need to use the database functionality to see where the client connection has come from.
tomward (BOB member since 2006-12-15)
Hi,
This will do the job…
The M_ACTOR_C_NAME column contains the actual user id as seen within the Supervisor module. The primary
key for the table is M_ACTOR_N_ID. To completely reset a User Id, simply set the M_ACTOR_C_PASSWORD
column to NULL and the M_ACTOR_N_STATUS column to 1.
Sample SQL:
UPDATE
OBJ_M_ACTOR
SET
M_ACTOR_C_PASSWORD = NULL,
M_ACTOR_N_STATUS = 1
WHERE
M_ACTOR_N_ID = 2;
Of course, this could be expanded to reset all BusinessObjects Users which are currently locked out:
Sample SQL:
UPDATE
OBJ_M_ACTOR
SET
M_ACTOR_C_PASSWORD = NULL,
M_ACTOR_N_STATUS = 1
WHERE
M_ACTOR_N_STATUS = 2;
ID for the User ID you want to reset (contents of M_ACTOR_N_ID)
See note on previous page regarding the data values in this column See note on previous page regarding the data values in this column
smitha_shivan (BOB member since 2006-08-07)
Moved to the Supervisor forum 
Nick Daniels 
(BOB member since 2002-08-15)
The above note will unlock the supervisor id, which is useful but not quite what you asked.
I recomend this method is only used when absolutley necesary. You can avoid needding to do this by having multple general supervisors set up so that if one gets locked you always can use the other to unlock it. After all updating the repository is an unsupported action and if you get it wrong BOBJ may be less than sympathetic with helping you sort the problem out.
Regards
Tom
tomward (BOB member since 2006-12-15)
Hi,
Thanks for all your responses.
Adding to my question, I would like to know how can I use database trigger to insert the information into another temp table as to which user locked the id, the time he locked the id and the terminal name and ip address from where this was executed.
Thanks
Baazigar (BOB member since 2004-06-10)
You are going to need to read about triggers and what data you can get about the connection as this will be specific to your platform.
The principal is as follows. A trigger can watch the table OBJ_M_ACTOR for update statements. When an update happens the trigger can then execute some database code and also capture the sql being executed against the OBJ_M_ACTOR table.
From the update sql you wil be able to work out who the user was and when the update was being executed.
You can probably get the terminal ip address etc from the database itself as the supervisor client will have a direct conection with the repository.
Once you have these bits of information you will then be able to insert it into a database table of your choosing.
tomward (BOB member since 2006-12-15)
i couldnt open supervisor in bo 6.1, i’ve tried m-actor-n-status=1 and pasword=null in obj-m-actor table, is there any other solution
r i’ve to reset any of the rest values in the table
gayathrikrishna (BOB member since 2008-10-03)
What error at you getting?
joepeters 
(BOB member since 2002-08-29)
your login is not valid(USR003)
gayathrikrishna (BOB member since 2008-10-03)
That’s not a password or user disabled error. It means the username is not recognized. Remember, e6 user IDs are case-sensitive.
Joe
joepeters (BOB member since 2002-08-29)
mens the userid is not in the repository.
peacock (BOB member since 2002-11-07)