but here is my question i am trying to answer.
A session is a session.
When a user opens a session using SQL*plus or toas or whatever, and he runs the worst SQL on earth, it is still one SESSION. correct?
When someone calls a stored procedure from the web via mod_plsql that is one SESSION or CONECTION. it does not matter how bad the SQL is or how many SQL statements there are.
correct?
My point is that increasing number of sessions can not be due to bad code running. It is too many clients trying to connect simultaneously.
Main Topics
Browse All Topics





by: oleggoldPosted on 2009-11-04 at 13:37:29ID: 25744218
the best answer is in Oracle lit: c/oracle10 g/server.1 02/b14220/ process.ht m
http://www.youngcow.net/do
"Connections and Sessions
Connection and session are closely related to user process but are very different in meaning.
A connection is a communication pathway between a user process and an Oracle instance. A communication pathway is established using available interprocess communication mechanisms (on a computer that runs both the user process and Oracle) or network software (when different computers run the database application and Oracle, and communicate through a network).
A session is a specific connection of a user to an Oracle instance through a user process. For example, when a user starts SQL*Plus, the user must provide a valid user name and password, and then a session is established for that user. A session lasts from the time the user connects until the time the user disconnects or exits the database application.
Multiple sessions can be created and exist concurrently for a single Oracle user using the same user name. For example, a user with the user name/password of SCOTT/TIGER can connect to the same Oracle instance several times.
In configurations without the shared server, Oracle creates a server process on behalf of each user session. However, with the shared server, many user sessions can share a single server process.
"