Kbase 19819: JDK and JRE JDBC Requirements
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/30/2008 |
|
Status: Verified
SYMPTOM(s):
Problem running a JDBC application
Merant ODBC driver
Progress Java Database Connectivity (JDBC).
Java SQL.SQL exception {jdbc progress driver: 6013}
CAUSE:
For some operating systems such as IBM/AIX, Progress does not include the JDK in the installation media because of licensing issues. If the JDK is not included in the Progress media, the customer must contact their vendor.
It has become apparent that the Progress MERANT driver appears to be in some way dependent on the exact version/patch of JDK that is shipped with the Progress product. Everything works fine in the environment as long as you stick to the Progress provided scripts because the scripts point you at all of the appropriate variables and executables. It is when you try to develop your own JDBC application that you run into problems.
You would see the above error when you try to run a java program. The java program would compile but you cannot run it successfully.
FIX:
This solution supplies information about Java Development Kit (JDK) and Java Run-Time Environemt (JRE) version requirements for Progress Java Database Connectivity (JDBC).
First check that these environment variables are set:
PROGRESS Version 9.1A05 as of Fri Mar 24 18:57:47 EST 2000
DLC=<dlc directory>
JDKHOME=<your jdk directory>
PATH=$DLC/bin:$DLC/jre/bin:$JDKHOME/bin:$PATH
LIBPATH=$DLC/lib:$DLC/jre/lib/aix
ative_threads:$LIBPATH
CLASSPATH=$DLC/jre/lib/classes.zip:$DLC/java/progress.zip
Progress expects customers to run with JDK 1.1.8_19991126. You can tell what JDK level is being run by checking the $JDKHOME/README file. The JDK version is specified on the "full version" line of the file.
If the "full version" specified in the $JDKHOME/README file is different from the version specified in the $DLC/jre/README, the following workaround must be followed when developing new JDBC applications:
1) Compile new JDBC applications by running $JDKHOME/bin/javac.
2) Run new JDBC applications with $DLC/jre/bin/jre and NOT $JDKHOME/bin/java
Development is working on determining what can be done to eliminate this issue.