Last updated on OCTOBER 04, 2016
Applies to:Oracle Applications Technology Stack - Version 184.108.40.206 to 220.127.116.11 [Release 11.5.10]
Information in this document applies to any platform.
This problem can occur on any platform.
Checked for relevance on 29-SEP-2016
Whilst monitoring the database connections, you observe that inactive JDBC Connections keeps on growing and are not getting dropped. You could use the SQL below to monitor these connections
REM SQL to check number of JDBC connections
set echo on
set feedback on
set pagesize 132
set linesize 80
col username format a10
col how_many format 9999
col machine format a25
select s.machine, s.username, s.module, count(*) how_many
from (select distinct PROGRAM, PADDR, machine, username, module from V$SESSION) s,
where s.paddr = p.addr and s.program = 'JDBC Thin Client'
group by s.machine,s.username, s.module;
REM end of SQL
This eventually results in your database running out of connections or other resources such as memory.
NOTE - it is quite normal for JDBC connections to show as INACTIVE status. This in itself does not mean there is a problem.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms