Sometimes people bring issues to me that exceed my knowledge and experience (or time to investigate). Business Objects is a complex tool now and there are always new nooks and crannies full of “features” that frustrate BO administrators and users. Alan Miles brought this latest one to my attention; I hope that we can collectively study this issue, try to replicate it, and comment on what is happening here.
Steps to Reproduce the Issue:
SELECT SI_LASTLOGONTIME FROM CI_SystemObjects WHERE SI_ID = xxxxx in Query Builder and refreshing it between a user’s logins.
The value for SI_LASTLOGONTIME only updates every other time a user logs in (to InfoView or CMC), so first login no date change, next login the date changes, next login no change and so on.
Is this generally the case with BO or am I seeing something peculiar to our setup? Thanks for any light you can shed on this. Please provide any inputs in the comments section and both Alan and Julian will do their best to respond to them.
This doesn’t appear to happen on my installation.
Here’s my findings for a test user we have
1st check – 18/04/12 10:19:18
2nd check – 20/04/12 08:48:42
3rd check – 20/04/12 08:49:26
4th check – 20/04/12 08:49:59
Looks like it is going to be peculiar to our site.
Hi Alan, have you tried doing a full restart?
Restart is not really feasible for out setup.
Hi Alan, I am not proposing a reboot of the server(s) hosting BO, but just a restart of the BO services (SIA in XI 3.1). You could even do this on a rolling basis (in a multi-server clustered environment).
I’ve also seen this behaviour on our XIr3.1 environment.
I reported it to SAP as a bug and got the response that it’s a known issue. SAP thought it was caused when Timeouts or Closing of the Browser Window occurred, but I’ve been able to show that this is not the case. A correct logout does not always update SI_LASTLOGONTIME.
In the end I went for a workaround such as the Max date of the last audit action captured for a user.