Smart questions
Smart answers
Smart people
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Tek-Tips
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

LINK TO THIS FORUM!

Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

Partner With Us!

"Best Of Breed" Forums Add Stickiness To Your Site
Partner Button
(Download This Button Today!)

Feedback

"...This is easily the most helpful website I've ever used, and this is the best forum with the quickest response time bar none...."

Geography

Where in the world do Tek-Tips members come from?
jdemmi (MIS)
19 Mar 09 9:00
If this is not the proper place for this post please direct me to it.

Let me start by saying that I am not a Discoverer admin -- I am only the EULOWNER for several business areas.

Here's my problem.

Users connect to the Discoverer (web) viewer (hosted on a Linux server) via a browser. They run querys and reports as needed. Everything to here is OK. But then I have 2 possible paths that lead to the same problem.

PATH 1.

The user simply closes his/her browser and does not use the exit/logout option in the Discoverer viewer.

PATH 2.

The user exports a query to EXCEL WEB QUERY and exits the viewer. The user then runs this web query from their local Excel. When finished they close their local Excel.

Both of the above paths lead to the same
problem, INACTIVE sessions that will not be "removed" until the DB is bounced. I am watching this count grow on a daily basis and want to know:

1. Is there a session timeout paramater somewhere in the viewer config?
2. Is there any way to remove these sessions manually? Killing doesn't work because that just changes the status to killed -- they remain in v$session until the client attempts to use the session again -- which in this case will never happen.
3.Is there any way to prevent this from happening?

Let me know if you need more info to help me with this issue.

-- Jason
"It's Just Ones and Zeros"

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close