Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

web interface not disconnecting

Status
Not open for further replies.

nontrad

MIS
Jan 10, 2001
83
US
I'm working with a Db in development that is going to be accessed via a web interface.

The problem is that after the people exit the system, the connection is not severed. The BIG problem with this is that I cannot shut down the Db using normal or immediate because it is waiting for these connections to end. I have to use shutdown abort.

Any ideas what would be causing this and how to solve the problem before the Db goes online for real?

Thanks
E.
 
Can you create a profile for your web ids that has an idle_time limit? Then they would automatically get logged off after exceeding their idle time.

Also, I don't see why shutdown immediate isn't working for you. Isn't it supposed to automatically disconnect everyone?
 
I'll try thr idle_time idea. The problem would be when a lot of users start interfacing with the server. The only way I could shut it down would be to prevent any new connections then wait until the max idle time had passed. Not ideal either.

You would think that everything would disconnect w/ immediate but it wouldn't. The abort temporary measure was on the advice of an Oracle rep.

Luckily it's not in production yet.
 
What you could alternatively do is get a list of idle processes into a cursor using something like a

SELECT sid,serial#,status,server FROM v$session WHERE status = 'xxx' (i.e. whatever statuses you wish to terminate);

Then, when you know the sid and serial# then you can loop through and kill them if you have sufficient privileges by passing the values of sid and serial#:

ALTER SYSTEM KILL SESSION (sid),(serial#);

 
Well, I'll se about working on the different alternatives beginning Friday. The problem would be if I am "killing" it at one end and new people are connecting elsewhere - sort of like bailing a sinking boat. I think one problem with this would be that I could accidently kill system processes also since thay are listed as a connection. selecting for the username also helps prevent this.

E,
 
You can avoid killing your system processes since these all have a serial# of 1... just extend your where clause...
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top