Shadow processes+Terminal IDs

Two questions for you all:

Has anyone found a solution for hanging shadow-processes? We have a system where Oracle is on UNIX, and clients connect via SQL*NET and Windows 3.1.

If a program hangs, or for that matter, if a query takes 'too long' the users tend to re-boot their computers. This gets messy, because if any rows in the database were locked, they remain that way. OSQL*Net never has the chance to drop the connection. Finally, someone manually goes through and kills off the hanging processes, thus forcing a rollback.

Question number 2: Terminal identification (PC's)

The SQL*Net manuals are very skimpy on the subject, but we're wondering: The DOS variable USERNAME gets picked up by SQL*Net as the pseudocolumn  userenv('USERNAME') , but I can't find a way to set the 'TERMINAL' variable. Is there a way to do this? Namely, we want something which will identify the user and his/her terminal (PC he/she's using) within the DBA monitor.

Can this be done?

        Thanks in advance,

        Kevin Fries Received on Sat Aug 07 1993 - 14:10:09 CEST