Re: java.sql.SQLException: Bigger type length than Maximum

sandro.salari_at_gmail.com wrote:

> Hi,
> thanks for the assistance, I use the same instruction you talk about
> for obtain JDBC driver information. The application server is as
> production server out of my direct control and I don't know why the
> driver is not up to date, or if someone has replace it by another one.
> I read about someone that had the same problem and resolved it updating
> ojdbc14.jar file. I can't update directly this file, but I can alter
> the Weblogic CLASSPATH. The problem is that I'm not sure about the
> procedure to follow to done this modify ( I try to use the
> PRE_CLASSPATH procedure, but I don't see change in driver version).
> Can you explain me the step needed, and the file to modify for UNIX
> platform please? Can you confirm me that this problem is due to a bug
> present in early version of Oracle JDBC driver as I read in some forum?
>
> Regards,
> Sandro Salari.

Hi, yes, I can confirm it's an oracle driver issue, fixed in the later vesion of the driver. As I said, the only way to get WebLogic to use the driver is to get it into WebLogic's class path. WebLogic's class path is constructed by the script that starts WebLogic, and passed explicitly to the java call via a commandline argument. You must therefore explicitly add the driver so it's ahead of weblogic.jar in the constructed commandline argument, or you must replace the ojdbc14.jar in the server\lib directory. HTH,
Joe Weinstein at BEA Systems Received on Thu Mar 02 2006 - 19:22:48 CST