Re: Thick vs thin client - 11g R2
- From: Michael Elkin <melkin4u@xxxxxxxxx>
- To: sbecker6925@xxxxxxxxx
- Date: Sun, 26 Sep 2010 07:00:04 +0200
Hi Sandra,
Regarding lib32 we have experienced a similar problem with Oracle 11gR2.
On a Linux 64 bit platforms all Oracle 64 bit client installations included
both lib32 and lib (with 64 bit libs) directories.
Since 11gR2, lib32 directory has been taken out from a Oracle 64 bit
installation on Linux 64 bit.
The workaround that i got from Oracle support is to install 32 bit client on
64 bit Linux platform. This is possible only on Linux.
Please notice that 32 bit Oracle client does not have lib32 either but only
a lib directory.
All this is applicable of course if you need to run 32 bit application on 64
bit Linux platform. This can happen with some kind of a legacy application
that none wants to change or test .
Michael
On Fri, Sep 24, 2010 at 4:28 PM, Sandra Becker <sbecker6925@xxxxxxxxx>wrote:
> I've checked the ORACLE_HOME for the 11g client install and there is no
> lib32 directory.
>
> There seems to be a misunderstanding about the connectivity issue. We CAN
> connect with JDBC thin client. We CANNOT connect with the OCI thick
> client. We are using java 1.6,
>
> Using the JDBC thin client causes unprintable characters to be inserted
> into the database that our application does not handle correctly. This
> usually happens when someone does a cut & paste. There is no problem if the
> customer just types the data. Our database characterset is US7ASCII.
>
> I finally got them to give me the error they receive when trying to start
> the application with the OCI thick client:
>
> 9/24/10 7:51 AM Error in bean tz.trader.ejb.CCSessionbean.CCSessionHome
> java.lang.UnsatisfiedLinkError: no ocijdbc9 in java.library.path
> at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1734)
> at java.lang.Runtime.loadLibrary0(Runtime.java:823)
> at java.lang.System.loadLibrary(System.java:1028)
> at oracle.jdbc.oci8.OCIDBAccess.logon(OCIDBAccess.java:267)
> at
> oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:365)
> at
> oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:547)
> at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:347)
>
> We have a developer working on the issue now.
>
> Sandy
>>> Transzap, Inc.
>>>
>>
--
Best Regards
Michael Elkin
Other related posts:
