Oracle at DESY - Sniped Sessions

Oracle sessions change into the status sniped when they encounter the idel timeout limit on the database. The idle timeout limit is set to 10 hours on the DESY instance. You can see if you have sniped sessions via running the command

SQL> select * from user_sessions;

From the application point of view you risk by long running and idle sessions

locking of database objects
data loss
security problems
freeing of capt account resources.

From the database service point of view your session(s)

capture database resources
as well as server machine resources

which can't be used by other applications.

How to solve this problem?

Sniped sessions will be detected at least once the day and a note by e-mail will be send to the concerned users. Inside the e-mail you will find a list of your hanging sessions and on which machines they are hanging.

Please login on these mentioned machine(s) and either reconnect within the running applications or close them.

If you can't find a running application on the first glance, you can find them on Windows machines in your Task Manager or on Unix machines via the command ps -ef | grep -i your_accoutn_name. You can then terminate your application from inside the Task Manger or on Unix machines via the kill -9 your_program_pid command.

If you need further support, please contact Oracle Support at DESY.