Using the Java IP with the Local ODBC Client
- Last Updated: April 5, 2026
- 1 minute read
- OpenAccess SDK
- Version 9.0
- Documentation
When using the Local ODBC Client with Java IPs, the location of the OpenAccess SDK IP shared libraries must be added to the dynamic library search path. The subdirectory ip/bin is added automatically when the shell script has been executed (see Running the Installation Script).
On some platforms, the location(s) of shared libraries of Java Runtime (JRE) must be added to the dynamic library search path. In this case, the installed shell script sets the location(s) of the JRE shared libraries in the environment variable named JRELIBPATH. Add the value of this environment variable to the dynamic library search path, or, uncomment the placeholder in the oalocal[64].[c]sh shell script.
The following example adds the environment variable on 64-bit AIX:
$ cat oalocal.sh
AIX=/usr/oaodbclocal900/lib64${LIBPATH:+":"}${LIBPATH:-""}
export LIBPATH
OALOCAL_ODBC_HOME=/usr/oaodbclocal900/lib64; export OALOCAL_ODBC_HOME
ODBCINI=/usr/oaodbclocal900/odbc.ini; export ODBCINI
# add OpenAccess SDK IP shared libraries to LIBPATH
LIBPATH=/usr/oaodbclocal900/ip/bin:$LIBPATH
# When Java IPs are used, add this also to LIBPATH
JRELIBPATH=/usr/java14/jre/bin/classic:/usr/java14/jre/bin;
export JRELIBPATH
# LIBPATH=$JRELIBPATH:$LIBPATH
$ . oalocal.sh
$ echo $JRELIBPATH
/usr/java14/jre/bin/classic:/usr/java14/jre/bin
$ LIBPATH=$JRELIBPATH:$LIBPATH
Do not use the ServiceEnvironmentVariable service attribute to set the environment variables for the Local ODBC Client. Instead, use the oalocal.sh or oalocal64.sh script to set the environment variables required for the services, the IP, the ODBC driver manager, and the ODBC driver, before launching the application.