JDBC sessions timout - for inactive sessions

how can i define the timeout of inactive sessions (connections) on oracle database thru JDBC connetionPool technology - to de disconnected physically, is there a default timeout for the sessions to be disconnected.?
thanks for any help.

The following is the Data Source that I am using:
<?xml version = '1.0' encoding = 'windows-1252'?>
<!DOCTYPE data-sources PUBLIC "Orion data-sources" "http://xmlns.oracle.com/ias/dtds/data-sources.dtd">
<data-sources>
<data-source
name="jdev-connection-Teradata"
class="com.evermind.sql.DriverManagerDataSource"
location="jdbc/TeradataCoreDS"
xa-location="jdbc/xa/TeradataXADS"
ejb-location="jdbc/TeradataDS"
pooled-location="jdbc/TeradataPooledDS"
connection-driver="com.ncr.teradata.TeraDriver"
username="GavinLDCHBull"
password="xxxxxx"
url="jdbc:teradata://FONEBONE/DATABASE=HABWaiver"
inactivity-timeout="30">
</data-source>
</data-sources>
We are using the ADF framework (i.e. entities and simple views) for accessing all Teradata data. I do not explicitly issue any JDBC calls for accessing the data. When I update the data, I use JDBC calls to initiate stored procedures. However, the problem (not closing the statements) happens almost immediately after starting the application, and prior to issuing any stored procedures.
I have not tried to duplicate the problem using a simple java program because I am using ADF for data access (again, I don't explicitly issue any JDBC statements).

Similar Messages

How to see SQL TEXT for inactive sessions.

Hi,
I have SID where the session have been completed.I wanna know,what the session has done.
Is there any sessions which has SQL TEXT of inactive sessions.
Thanks.Plz help me.

Hi,
As others already suggested, try this SQL below:
select sess.sid,
       sess.serial#,
       sess.username,
       sql_text
from v$sqlarea sqlarea, v$session sess
where sess.prev_hash_value = sqlarea.hash_value
   and sess.prev_sql_addr = sqlarea.address
   and sess.username is not null
   and sess.status='INACTIVE';   Cheers
Legatti

JDBC THIN CLIENT in V$SESSION inactive

Hello DBA's
I have too many inactive session of JDBC thin client. Please suggest can we kill them?? or any other alternative
SID SERIAL# USERNAME PROGRAM STATUS Inactive_Hours
12 74 APPS JDBC Thin Client INACTIVE 1772.69806
13 31 APPLSYSPUB JDBC Thin Client INACTIVE 1772.69806
18 62 APPS JDBC Thin Client INACTIVE 1772.69806
20 1 APPLSYSPUB JDBC Thin Client INACTIVE 952.465556
22 9 APPS JDBC Thin Client INACTIVE 1772.69806
26 55 APPS JDBC Thin Client INACTIVE 92.1361111
30 2 APPLSYSPUB JDBC Thin Client INACTIVE 1772.61361
31 7 APPS JDBC Thin Client INACTIVE 1772.69667
53 29516 APPS JDBC Thin Client INACTIVE 521.344167
54 35 APPLSYSPUB JDBC Thin Client INACTIVE 1772.69278
69 7 APPLSYSPUB JDBC Thin Client INACTIVE 1772.69278
Can we kill them or any particular check before killing them??

I am not sure how you have computed the "Inactive Time".
You need to know if the middle-tier is configured to re-connect when necessary OR whether the middle-tier process will fail at the next SQL / operation it attempts to execute. So middle-tier processes can handle a kill gracefully, others cannot.
The usernames you list indicate that this is an Oracle EBusiness Suite install. You need to identify the services on the application server that correspond to these sessions and whether they can handle a kill gracefully.
Why do you need to kill sessions ?
Hemant K Chitale

Looking for a script to kill all inactive sessions

Does anyone have a script to kill all INACTIVE sessions (with EXECUTE IMMEDIATE)?

I suggest you to specify which OS you are talking about.
The inactive status on the V$SESSION doesn't mean the user is not doing any thing, it only means the oracle server process is not processing any thing by the time it was queried. On OLTP systems Oracle Server Processes remain INACTIVE for more than 95% of the time, so it is advisable to configure shared servers.
If you are really concerned about idle time, then I suggest you to configure profiles.
On the pool mechanism you should address the microsoft side, if this, as far as I understood and guessed, application server is IIS.
I suggest you further reading on the Killing sessions script and different session status (check the sniped status) here:
Re: session inactive ??
Re: make a job to delete the sniped sessions
Re: How do I put a timeout in my DataBase?
Re: Killing Session with Locks in Linux
~ Madrid

Inactive sessions in Database

Hi,
Lot inactive sessions are in database, Before we bounce database ----> max process got reached, For that we have changed max process and bounced the database but i can see still 75 inactive sessions in database,
SQL> show parameter process
NAME TYPE VALUE
aq_tm_processes integer 1
db_writer_processes integer 1
gcs_server_processes integer 0
job_queue_processes integer 2
log_archive_max_processes integer 2
processes integer 200
SQL> show parameter spfile
NAME TYPE VALUE
spfile string
Then i changed processes to 300
SQL> show parameter process
NAME TYPE VALUE
aq_tm_processes integer 1
db_writer_processes integer 1
gcs_server_processes integer 0
job_queue_processes integer 2
log_archive_max_processes integer 2
processes integer 300
even after bouncing still 75 inactive sessions in database

Hi,
What are the events/programs of those sessions?
Have you started the application or not yet?
Go through the following documents and see if it helps.
Note: 427759.1 - How To Prevent Inactive JDBC Connections In Oracle Applications
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=427759.1
Note: 261791.1 - 11i JDBC Thin client connections remain active, MAX PROCESSES REACHED
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=261791.1
Regards,
Hussein

OracleConnectionPoolDataSource creates inactive sessions

Hi,
My customer uses OracleConnectionPoolDataSource and finds that the pooled connection had created a huge number of inactive sessions on the database side.
Any idea why this happens?
Thanks in advance.
Regards,
Sindhiya V.

Hi Hamdy,
The inactivity timeout was configured through the Oracle Enterprise Manager.
We created a Data Source and specified the following attributes on the page.
JNDI Locations
Location: jdbc/USPSTFPDADefaultDS
XA Location: jdbc/xa/USPSTFPDAXADS
EJB Location: jdbc/USPSTFPDADS
Connection Attributes
Connection Retry Interval: 5
Max Connection Attempts: 3
Cached Connection Inactivity Timeout: 300
Maximum Open Connections: 10
Minimum Open Connections: 1
Wait For Free Connection Timeout: 5
Hope you could help me in resolving this issue.
Thanks & Regards,
Sindhiya V.

SOAINFRA inactive sessions

Hi,
When i query the v$session table i can see that there are some 300 odd inactive sessions in the DB for the SOA-INFRA schema. When i bring the manged servers down all the inactive sessions disappear. I have aborted all the running instances but the inactive session count still doesn't come down.
Please share your views on this.

Hi,
What are the events/programs of those sessions?
Have you started the application or not yet?
Go through the following documents and see if it helps.
Note: 427759.1 - How To Prevent Inactive JDBC Connections In Oracle Applications
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=427759.1
Note: 261791.1 - 11i JDBC Thin client connections remain active, MAX PROCESSES REACHED
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=261791.1
Regards,
Hussein

HIgh Inactive sessions

Hi,
We are facing a problem of lot of inactive sessions consuming huge resources. We have setup connection pooling from weblogic application and connection timout and resuse parameters have been setup from application side for connection pooling. And we still find high inactive sessions which are not getting released even after application user closes the session properly. What might be the work around for this as we facing this for last one week.
Oracle 10.2.0.3.0 on solaris box.
regards
Jaffy

Jaffy wrote:
Hi,
We are facing a problem of lot of inactive sessions consuming huge resources. We have setup connection pooling from weblogic application and connection timout and resuse parameters have been setup from application side for connection pooling. And we still find high inactive sessions which are not getting released even after application user closes the session properly. What might be the work around for this as we facing this for last one week.
Oracle 10.2.0.3.0 on solaris box.
regards
JaffyHi Jaffy,i suggest you have to configure profile for oracle users.For example if you user will inactive 10 minute then can oracle automatically kill this session.For this you can create profile as:
create profile test_prof limit idle_time 10;
alter user <user> profile test_prof;
/*but first you need change resource limit*/
alter system set resource_limit=true;

OC4J inactive sessions

I have OC4j server running on one box and the oracle database
is on different server. We connect through JDBC.
It looks like the application server does not close inactive sessions.
Because of this temporary tablespace on database server gets filled
up. I tried increasing it 4g but the problem looks like
of inactive sessions.
How do I specify timeout period for inactivity?
I am using Oracle 9iAS Containers for J2ee (1.0.2.2.1)
How do I clean up inactive sessions/processes.
Satish Juware

Yes,
I am talking about inactive data connections. My application does not
have any ejb module.It does have web module with servlets and JSPs.
We do not use JNDI or data-sources.xml file for specifying
username, SID, host:port to specify where database is.
Insted we code thise values iside a servlet called DBconnection.
IN that case should I still Specify inactivity timeout period
in data-sources.xml.
In the application code how do I make sure that connection is
closed.
Thanks !
Satish Juware
Hi Satish,
I assume the "session" you are referring to is what I refer to as
a database "connection".
If the OC4J debug messages are accurate and reliable, then OC4J does,
most definitely, close inactive database connections, after a certain
"timeout" period. You configure this in your "data-sources.xml" file.
Unfortunately I am not at work now, so I can't show you what mine
looks like, but I suggest you do a search for information regarding
the "data-sources.xml" file. I recommend searching the following URLs:
http://www.orionserver.com
http://www.orionsupport.com
http://www.atlassian.com
http://www.elephantwalker.com
Hope this helps you.
Good Luck,
Avi.

PL/SQL procedure to kill inactive session

Hi all ,
Please i am trying to write a procedure to kill inactive sessions of the shema 'TESTSCHEMA' .This is my first procedure , am not use to pl/sql but i went through many turtorial but have some errors at compliation .when i try to compile the procedure the errors are as below :
15:50:28 Start Find Objects [TESTSCHEMA@TESTDB_UNIX(2)] ...
15:50:28 End Find Objects [TESTSCHEMA@ TESTDB_UNIX(2)]
15:50:32 Start Compiling 1 object(s) ...
15:50:32 Executing ALTER PROCEDURE fib_dead_cnx_cleanup COMPILE ...
15:50:32 [13:2] PL/SQL: ORA-00933: SQL command not properly ended
15:50:32 [9:3] PL/SQL: SQL Statement ignored
15:50:32 [18:12] PLS-00103: Encountered the symbol "(" when expecting one of the following:
15:50:32 constant exception <an identifier>
15:50:32 <a double-quoted delimited-identifier> table LONG_ double ref
15:50:32 char time timestamp interval date binary national character
15:50:32 nchar
15:50:32 The symbol "<an identifier>" was substituted for "(" to continue.
15:50:32 [18:21] PLS-00103: Encountered the symbol "LOOP" when expecting one of the following:
15:50:32 := ; not null default character
15:50:32 The symbol "; was inserted before "LOOP" to continue.
15:50:32 [27:8] PLS-00103: Encountered the symbol "ALTER" when expecting one of the following:
15:50:32 begin case declare exit for goto if loop mod null pragma
15:50:32 raise return select update while with <an identifier>
15:50:32 <a double-quoted delimited-identifier> <a bind variable> <<
15:50:32 close current delete fetch lock insert open rollback
15:50:32 savepoint set sql execute commit forall merge pipe
15:50:32 Compilation complete - 5 error(s) found
15:50:32 End Compiling 1 object(s)
below is the procedure code :
CREATE OR REPLACE
PROCEDURE fib_dead_cnx_cleanup
AS
l_serial     CHAR(100);
l_sid CHAR (100);
l_sid_serial CHAR(100);
l_count      NUMBER(10,0);
CURSOR session_cur IS
          SELECT sid,serial#,sid||','||serial# as sid_serial
     FROM v$session
     WHERE username='EBBFCAT' and schemaname='TESTSCHEMA'
     and status='INACTIVE'
BEGIN
     BEGIN
     l_count := 0;
               OPEN session_cur;
                    WHILE ( 1 = 1) LOOP
                         BEGIN
                              FETCH session_cur INTO l_sid ,l_serial,l_sid_serial ;
                                   EXIT WHEN session_cur%NOTFOUND ;
                              BEGIN
                                   alter system kill session 'l_sid_serial' ;
                              END;
                         END;
                    END;
               CLOSE session_cur;
     END;
END FIB_DEAD_CNX_CLEANUP;
Thanks

Hi,
Never write, let alone post, unformatted code.
When posting any formatted text on this site, type these 6 characters:
{code}
(small letters only, inside curly brackets) before and after sections of formatted text, to preserve spacing.
Among the benefits of formatting: you can indent to show the extent of blocks, such as BEGIN-END.
Different types of blocks need modifiers after the end, such as "END *IF* " and " END *LOOP* ". If each opening statement (BEGIN, IF, LOOP) is directly above its corresponding END, then it's easy to check if you got the right modifier.
Here's what you code looks like with some formatting, and a couple of corrections added. Look for -- comments.
CREATE OR REPLACE
PROCEDURE fib_dead_cnx_cleanup
AS
     l_serial     CHAR(100);
     l_sid          CHAR (100);
     l_sid_serial     CHAR(100);
     l_count          NUMBER(10,0);
     CURSOR session_cur IS
            SELECT sid
            ,       serial#
            ,       sid     || ','
                                  || serial#     as sid_serial
            FROM     v$session
            WHERE      username     = 'EBBFCAT'
            and     schemaname     = 'TESTSCHEMA'
            and     status          = 'INACTIVE';          -- need semicolon here
BEGIN
     BEGIN                                   -- Why?
          l_count := 0;
          OPEN session_cur;
          WHILE ( 1 = 1)
          LOOP
                BEGIN                         -- Why?
                     FETCH session_cur
                     INTO   l_sid
                     ,          l_serial
                     ,          l_sid_serial ;
                           EXIT WHEN session_cur%NOTFOUND ;
                     BEGIN                    -- Why?
                         alter system kill session 'l_sid_serial' ;    -- Not a PL/SQL command
                           END;
                      END;
            END LOOP;                         -- LOOP ends with END LOOP
            CLOSE session_cur;
        END;
END      FIB_DEAD_CNX_CLEANUP;Take baby steps.
I've been wrtiing PL/SQL for 20 years, and I would never write that much code at once. If you're a beginner, all the more reason to start small. Write as little as possible, test, debug and test again (if necessary). When you have someting working, add 2 or 3 more lines and test again.
It looks like you have three BEGIN statements that don't serve any purpose. You should get rid of them (and their corresponding END statements, of course).
One error I did not fix: ALTER SYSTEM is not a PL/SQL statement. It's a SQL statement. You can run a SQL statement inside PL/SQL by using dynamic SQL, where you construct a string containing the SQL statement, and then use dbms_sql or EXECUTE IMMEDIATE to run it.
Edited by: Frank Kulash on Aug 18, 2009 12:37 PM

Inactive sessions

Iam in need of a script to kill all the inactive sessions in the database and the same script should kill all the pid related in the OS also.
can anyone send me a scripts or any input on this will be of great help ?
Kai

KaiS,
See both functions and wrap around in your unix script, this should magic for you I suppose :) and you should replace sqlplus "/as sysdba" by sqlplus '/as sysdba'
*function readSqlstmt {*
typeset stmt=$1
echo "
set feedback off
set verify off
set heading off
set pagesize 0
whenever sqlerror exit 1
whenever oserror exit 2
*$stmt;*
exit
*" | sqlplus -S "/as sysdba" >> test.log*
function killpid {
killpidsql=killpid.sql
sqlplus -s "/as sysdba" << ENDOFSQL >> test.log
whenever sqlerror exit 1
whenever oserror exit 2
SET pagesize 0
SET verify off
SET feedback off
SPOOL ${killpidsql}
SELECT 'ALTER system kill session ''' || s.sid || ',' || s.serial# || ''';'
FROM v\$session s, v\$process p
WHERE s.paddr = p.addr AND s.status = 'INACTIVE';
SPOOL OFF
@${killpidsql}
ENDOFSQL
Example: How to use above readSqlstmt function, to kill unix process id and call "killpid" to kill sessions from oracle.
*readSqlstmt "SELECT p.spid FROM v\$session s, v\$process p WHERE s.paddr = p.addr AND s.status = 'INACTIVE'" | while read u*
*do*
* #echo "kill -9" $u >> test.log*
* echo $u*
*done*
*Regards*
Edited by: OrionNet on Dec 10, 2008 10:52 PM
Edited by: OrionNet on Dec 10, 2008 10:54 PM

Logon_time in v$session gives old date for new session

Hi,
I have a unique issue whenever I run v$session for username='A' and status= active I see logon_time as old date in this its '12-MAY-2008'. Now there are total 150 sessions for username='A'. 2 are status= Active, 1 is status=Killed and 147 are status=INACTIVE.
So whenever a new session comes from application side it activates the INACTIVE session and date remains 12-May-2008 instead of current date.
Also when you logon directly to Oracle using user 'A' , again same logon_time in v$session, rather than current date in logon_time. We are using Oracle 9.2.0.6 on Unix.
Any way I can resolve this issue?
Regards,
Tushar Kathe

Hi,
select username,logon_time,machine,terminal from v$session where status='ACTIVE';
USERNAME LOGON_TIM MACHINE TERMINAL
04-MAY-08 prod1.test.com UNKNOWN
04-MAY-08 prod1.test.com UNKNOWN
04-MAY-08 prod1.test.com UNKNOWN
04-MAY-08 prod1.test.com UNKNOWN
04-MAY-08 prod1.test.com UNKNOWN
04-MAY-08 prod1.test.com UNKNOWN
04-MAY-08 prod1.test.com UNKNOWN
04-MAY-08 prod1.test.com UNKNOWN
04-MAY-08 prod1.test.com UNKNOWN
04-MAY-08 prod1.test.com UNKNOWN
04-MAY-08 prod1.test.com UNKNOWN
04-MAY-08 prod1.test.com UNKNOWN
04-MAY-08 prod1.test.com UNKNOWN
SYS 22-MAY-08 prod1.test.com
pts/4
TEST 12-MAY-08 app20.test.com
SYS 22-MAY-08
16 rows selected.
You can see the schema test shows logon_time as 12-May-08 but he has infact logon in the system today so should have today's date. The Toad time output I don't have.
Regards,
Tushar Kathe

Inactive sessions in v$session. True problem

Hi,
I am working in an Oracle 9i/Weblogic/J2EE platform. And when i look for session info in v$session view, i see that there are many sessions that have a status "Inactive". I already figured out what it means- the session is ACTIVE when it is doing an SQL query at the time and the session is INACTIVE when it is not doing an SQL query at that particular moment.
But i have questions:
1) If a client logs in to my webapplication and does a SQL query- then the sessions status is ACTIVE. After that, when the client just leaves (logs out just closes the browser) then Oracle marks that connection as 'INACTIVE'- Oracle does not KILL that session.
Ok let that be, but can another client then log in to my webapplication (from different computer) and get that same INACTIVE connection and start to use it?? If not, then these "abandoned" connection are truly useless, because they still use ORACLE resources (memory).
2)Another thing is that there are many INACTIVE sessions in v$session that have a name "plsqldev.exe" in PROGRAM column. That is a database client that i use to connect directly to my DB. But basicly i have only one PL/SQL program with one SQL query window open (this session is marked ACTIVE in v$session). So are these other 10 INACTIVE "plsqldev.exe" sessions meant for new plsql clients that may start to use the database or can only that particular user for whom the session was created at first place use that session?
And finally- sessions that are INACTIVE and have "plsqldev.exe" as a PROGRAM in v$session - is there any chance that a client logs in to webapplication and then gets that INACTIVE session?
If not, then these 10 INACTIVE plsqldev sessions (allthough the user has maybe shut down the program) are wasteless for webapplication users and they just starve the database.
Also a screenshot for illustration.
Waiting for your comments,
Thanks!

If connection pooling is in use then yes a different end-user can reuse the "inactive" session. Remember that ACTIVE and INACTIVE really only refers to if the session is executing SQL at the exact moment you query v$session.
In the case of a dedicated user connection using a product like Oracle Forms where the user spends much of the time reading and filling in screen fields the Oracle background session can show INACTIVE almost constantly because the queries being ran by the user are very fast.
Take a look at the last_call_et column. This is the time in seconds from when the last SQL statement was issued (not completed). If this value is resetting then the queries are being done.
If the time is large and the status is INACTIVE then you could have a 'dead' or 'runaway' background process which is a background process without a front-end process. Those can and should be terminated. For that matter sessions that are idle for long periods of time should probably also be killed. If nothing else runaway and idle sessions may make it appear you are using all your licensed connections even if you really are not.
Most connection pools wil automatically restart a terminated connection so if you clean-up process terminates an idle pooled connection it should not be a problem.
HTH -- Mark D Powell --

Active vs Inactive sessions

We are using Oracle 11 as a backend to PowerSchool (a student information system) with 6 application servers (dc-ps-01 thru -06). Using the following SQL, we are seeing numerous INACTIVE sessions vs ACTIVE.
select
count(b.machine) as mCount,
b.machine box,
b.status,
b.osuser os_user,
b.program program
from
v$session b, v$process a
where
b.paddr = a.addr and type='USER'
group by
b.machine,b.osuser,b.program,b.status
order by
b.status, mCount desc, box;
Sample output:
MCOUNT Box Status OS_USER Program
*2     DC-PS-01*     ACTIVE     powerschool     JDBC Thin Client
1     DC-PS-DB1     ACTIVE     DC-PS-DB1$     OMS
1     DC-PS-DB1     ACTIVE     SYSTEM     ORACLE.EXE (J001)
1     DC-PS-DB1     ACTIVE     SYSTEM     ORACLE.EXE (J000)
406     DC-PS-05     INACTIVE     powerschool     JDBC Thin Client
*44     DC-PS-01*     INACTIVE     powerschool     JDBC Thin Client
36     DC-PS-03     INACTIVE     powerschool     JDBC Thin Client
32     DC-PS-04     INACTIVE     powerschool     JDBC Thin Client
28     DC-PS-02     INACTIVE     powerschool     JDBC Thin Client
17     DC-PS-06     INACTIVE     powerschool     JDBC Thin Client
7     DC-PS-DB1     INACTIVE     DC-PS-DB1$     OMS
While the number of ACTIVE sessions fluctuate, the number of INACTIVE ones do not decrease. Would someone explain the internal working of this?
Thanks!

Note that the status column of v$session only shows ACTIVE while the Oracle session background process is busy performing a SQL statement on behalf of the front-end session. If the application spends most of its time with the user entering data onto or reading results off a screen then the session is going to appear INACTIVE most of the time in Oracle.
Also check the last_call_et to see how long it has been since the session issued a request to Oracle. This is how to tell if the session is truely INACTIVE.
If the front-end application uses connection pooling then depending on how many connections the application is set to grab and what kind of connection pool session management the front-end product provides you can have a lot of basically unneeded and truely inactive sessions.
HTH -- Mark D Powell --

DBA Reports large number of inactive sessions with 11.1.1.1

All,
We have installed System 11.1.1.1 on some 32 bit windows test machines running Windows Server 2003. Everything seems to be working fine, but recently the DBA is reporting that there are a large number of inactive sessions throwing alarms that we are reaching our Max Allowed Process on the Oracle Database server. We are running Oracle 10.2.0.4 on AIX.
We also have some System 9.3.1 Development servers that point at separate schemas in this environment and we don't see the same high number of inactive connections?
Most of the inactive connections are coming from Shared Services and Workspace. Anyone else see this or have any ideas?
Thanks for any responses.
Keith
Just a quick update. Originally I said this was only with 11.1.1.1 but we see the same high number of inactive sessions in 9.3. Anyone else see a large number of inactive sessions. They show up in Oracle as JDBC_Connect_Client. Does Shared Service, Planning Workspace etc utilize persistent connections or does it just abandon sessions when the windows service associated with an application is shutdown? Any information or thoughts are appreciated.
Edited by: Keith A on Oct 6, 2009 9:06 AM

Hi,
Not the answer you are looking for but have you logged it with Oracle as you might not get many answers to this question on here.
Cheers
John
http://john-goodwin.blogspot.com/

JDBC sessions timout - for inactive sessions

Similar Messages

Maybe you are looking for