not sure what a runaway query is?
do you have a SQL that can show me what the active session is doing? i do not think it is doing anything. most of these web pages should run in 5-15 seconds.
Main Topics
Browse All Topicsi have 2 databases A and B. They both use same oracle apache web server.
A has been locking up (ORA-00020) with some issues releasing HTTPD sessions. Some sessions stay there in ACTIVE mode for hours and some stay in INACTIVE status.
Some say it is the SQL and i think it has nothing to do with it.
1. Can i create a small procedure in B that would call "hello workd" in A every second to prove that SQL code is not part of the problem?
anyone has pl/sql for that?
2. We only have one DB acount. Would setting IDLE_TIME and CONNECT_TIME might solve the issue? Are not those set by default. I guess setting IDLE_TIME for web session (HTTPD) at 1 or 2 minutes would not hurt. Any ideas?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
ok i understand what a runaway query us. no i do not have any
A runaway query is a query whose execution time is taking longer than the execution time estimated by the optimizer. Runaway queries can lead to using up all of your processor cycles or other resources during its execution.
The problem i found now, i have INACTIVE session in this database since 6:00 AM this monring and they still there. AL of these have httpd@webserver program. If you can tell me why those sessions are not going away in 15 minutes (setting on MOD_PLSQL to clean up those) you will be a champ.
I believe database will not cleanup those unless i set a profile and IDLE_TIME.
Business Accounts
Answer for Membership
by: mrjoltcolaPosted on 2009-11-07 at 07:00:05ID: 25766519
I don't have time to go into a long answer to everything.
If you are having problems with "runaway" queries, you can set CPU_PER_CALL limit on a profile that will limit the total CPU consumed by an active query. When it is exceeded, the session is killed. It will have _no_ effect in idle (INACTIVE) queries.
But until you find out what those ACTIVE sesions are doing, you are just shooting in the dark. Find out what those ACTIVE sessions are doing (ie. what SQL is executing). A hello world procedure will prove nothing.