• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

exception while connecting to the database

 
santhoshkumar samala
Ranch Hand
Posts: 156
Eclipse IDE Hibernate Spring
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hi iam getting following exception while connecting to the database



please help me to resolve this
 
Paul Sturrock
Bartender
Posts: 10336
Eclipse IDE Hibernate Java
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Looks like you are trying to use more sessions than Oracle is cnfigured to allow. Do you close every Connection after you have finished with it in a finally block?
 
santhoshkumar samala
Ranch Hand
Posts: 156
Eclipse IDE Hibernate Spring
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
yes.. i have closed all the connections in finally
 
Muhammad Saifuddin
Ranch Hand
Posts: 1324
Android Java Windows
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by santhoshkumar samala:






I have no major experience in Oracle but I google and found some related with your query.

hope it helps

ORA Tips
 
Paul Sturrock
Bartender
Posts: 10336
Eclipse IDE Hibernate Java
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by santhoshkumar samala:
yes.. i have closed all the connections in finally


Hmm. Just noticed ORA-00604 happens first. So it looks like something is using up the available sessions as a result of your application connecting. What are you doing when this error occurs? Does it happen as soon as you connect? Does your schema have a trigger associated with it?
 
Chris Hendy
Ranch Hand
Posts: 98
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
First find out the maximum number of sessions the database is configured to allow:

select * from v$parameter vp where lower(vp.NAME) = 'sessions';

Then look at what sessions are curently connected:

select vs.username, vs.program, vs.module,
to_char(vs.logon_time,'DD-MON-YYYY HH24:MI:SS') lt
from v$session vs
where vs.audsid <> 0

Only then can you decide if it is an application error or a misconfigured database.
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic