RE: Anyone experience any problems with JDBC Oracle drivers and JDK 1.3.1 with connection pooling?

[Eduardo Estefano]

There is a limit for writing to a blob field of 4000 characters. If anyone knows a solution, please let  me know.   -----Original Message----- From: HyungKee Hwang [mailto:[EMAIL PROTECTED]] Sent: Thursday, July 26, 2001 5:45 PM To: Orion-Interest Subject: RE: Anyone experience any problems with JDBC Oracle drivers and JDK 1.3.1 with connection pooling?   I’m using Oracle 8.1.7’s JDBC driver (classes12) with JDK 1.3.0. And it seems to have some problems to handle CLOB. But there has not been any problem except CLOB problem up to now.   I heard from Oracle technical support that Oracle doesn’t support JDK1.3.x officially.   -HK   -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Duffey, Kevin Sent: Friday, July 27, 2001 6:30 AM To: Orion-Interest Subject: Anyone experience any problems with JDBC Oracle drivers and JDK 1.3.1 with connection pooling?   I have been trying to figure out why I can't connect to our Oracle database. We are running JDK 1.3.1 with Orion 1.5.2. We are using the jdbc.zip (I assume classes12.zip). I am reading on Oracle that Oracle 8.1.7 (and 8.1.5) only have JDBC drivers that support JDK 1.2.x. Does this mean running JDK 1.3.1 is a BAD move when using JDBC drivers from Oracle? Should I go back to JDK 1.2.2 for Orion? There are problems with JDK 1.2.2, such as the NT-LOGOFF and what not when running Orion as a service that I am trying to avoid. Please advise me if running Orion with JDK 1.3.1 (on Win2K Server or Solaris) is OK while using Oracle 8.1.5 and/or Oracle 8.1.7 databases and jdbc drivers.   Thanks.