Win a copy of Think Java: How to Think Like a Computer Scientist this week in the Java in General forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Problem: Unable to allocate a connection

 
Gabriel Tomoloju
Greenhorn
Posts: 20
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,
I was accessing ingres directly via a Java application, using jdbc-odbc.
But, i sometimes get this error:

failed to set isolation level: Unable to allocate a connection

NOTE: I am using the Caribou Lake driver

Any ideas?
Thanks.
 
Sutham Rojanusorn
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think you should consult with your jdbc driver document for this
to see .. whether you can set database transaction.
 
Manish M Malhotra M
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,
I was accessing ingres directly via a Java application, using jdbc-odbc.
But, i sometimes get this error:

failed to set isolation level: Unable to allocate a connection

NOTE: I am using the Caribou Lake driver

Any ideas?
Thanks.
--------------------------------------------------------------------------------
Posts: 11 | Registered: Feb 2004 | IP: Logged

Sutham Rojanusorn
greenhorn
Member # 76563
posted July 10, 2004 10:13 AM
--------------------------------------------------------------------------------
I think you should consult with your jdbc driver document for this
to see .. whether you can set database transaction
===========================================================================
***************************************************************************
From Manish:

I think Sutham is correct, refer the jdbc driver doc. May be you need to set the transaction level. And what is the default transaction level with this driver would be helpful for you.

regards,
Manish
SE, PCS
 
arnel nicolas
Ranch Hand
Posts: 149
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
i guess this happens when you try to create multiple SQL statement in the same instance of the connection. The JDBC-ODBC bridge does not support this. If you want, you can create another instance on your JDBC connection then create your other SQL statement to this connection(resource intensive activity). Other than that try using the JDBC driver that comes with your database, besides JDBC-ODBC bridge has limitted functionality.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic