I know this is the sort of question we all hate, but we’re feeling really ignorant. Since we’re moving from FC to ZABO, a lot of our users are used to feeling like if they ‘kill’ BusObj locally, their sessions are ended. However, it’s looking to us like even though they Ctrl-Alt-Delete the application (ZABO), they still look like the sessions are active when I look in the BO Services Administrator. And, I’m thinking the sessions are therefore still active in the database too… So, are the webi sessions still active because the users haven’t actually gracefully exited the application? How does one clean up after this sort of thing (or does one just wait until the inactive timeout takes effect)?
We’re trying to figure out whether the webi processes are holding up the database, or whether a very busy database is causing the sessions to take longer, in which case the users get frustrated and kill the program, and so on – is it all a catch-22?
This probably makes little sense, except to show how little we know about web server administration, but any comments/advice would be much appreciated!
Yes this is true, and they are awaiting a timeout depending on the time you set in WIGenerator, I believe. Mine is set to 60 minutes.
If the user is running a query and abends BO, then the active process on the server will maintain the connection to your database. Your DBAs should be able to see this. I’m a DB2 shop and we have a Resource Facility Limit of 5 minutes of CPU time per thread before terminating that connection.
Instead of abending BO, your users should be trained to use the escape key to stop a running query (which may or may not work depending on so many things :? ) Or contact a DBA to kill the database process.
IMHO, ZABO is great, either that or I got lucky in my deployment
I think because this was a new deployment and we were able to start small and learn as we go, we had a big advantage over someone that is converting a bunch of longtime users with their set ways and processes.
Have you tested building a report using “other data files”?
DAO errors and uninstallable ISAM errors are common here.
Thanks. Another question I forgot to ask yesterday – what about when I, in the BO Services Administrator, choose to “End Users Sessions” from the list of logged on users. I’d been assuming that that killed the related database session, but given yesterday’s experience, am not really sure. Thoughts?
I do this routinely if I happen to see someone logged in multiple times.
Between this, the audit log, and the status report I run against Actor table in the repository, I can see who is having trouble and take intervention if needed.
In answer to your question, yes, ending user session will not stop a running process on your database - at least not on the database I have.
Sheesh - what a pain. Not only have we moved in to a world where we need more web server admin support, but are back depending on the DBAs to kill sessions.
(BOB member since 2002-06-07)
(BOB member since 2002-06-11)