Bug 12691067: UNDEFINED SYMBOL "SQLGETPRIVATEPROFILESTRINGW" – WITH UNIXODBC DM 2.2.11

Show Bug Attributes Bug Attributes
Type B - Defect Fixed in Product Version -
Severity 2 - Severe Loss of Service Product Version 2.2.11
Status 11 - Code Bug (Response/Resolution) Platform 226 - Linux x86-64
Created 24-Jun-2011 Platform Version RED HAT ENTERPRISE LINUX 5
Updated 16-Oct-2011 Base Bug -
Database Version N/A
Affects Platforms Port-Specific
Product Source Oracle

Show Related Products Related Products
Line Oracle Database Products Family Oracle Database
Area Platform specific utilities Product 579 - Oracle ODBC Driver

Hdr: 12691067 N/A DM-UNIX 2.2.11 PRODID-579 PORTID-226
Abstract: UNDEFINED SYMBOL "SQLGETPRIVATEPROFILESTRINGW" – WITH UNIXODBC DM 2.2.11

    *
          o
                + 06/24/11 03:15 am ***

PROBLEM DESCRIPTION:
====================

While using ODBC connection on RH Linux 5 resulted in the following error:

isql -v MyDsn
isql: symbol lookup error:
/usr/lib/oracle/10.2.0.4/client/lib/libsqora.so.10.1: undefined symbol:
SQLGetPrivateProfileStringW

As per the Note: 762206.1, customer tried to upgrade the unixODBC version
from 2.2.11 to 2.2.12 but this version of unixODBC is not supported on RH
Linux 5.5
They approached RH support who gave the below explanation for their inability
to rebuild unixODBC-2.2.12 and ship that with RHEL 5:

=========================================================
I have reviewed the case and see that you are requesting that we can rebase
our unixODBC package to version 2.2.12. The case owner, Raghu, has already
filed a request for feature enhancement (RFE) with our Product Management
team and it is being considered.

In order to set your expectations appropriately on this request, we have had
ongoing talks with Oracle about this specific issue and unfortunately for our
customers, we have not gotten very far in getting this issue resolved. To
provide some level of transparency, Oracle started to ship a new driver,
which they build against unixODBC-2.2.12, instead of the original version
that RHEL 5 ships with. We have requested Oracle, as their software is being
certified against RHEL 5, to rebuild against our version of unixODBC. Oracle
to date has not complied with our request.

On the other hand, we cannot simply rebuild unixODBC-2.2.12 and ship that
with RHEL 5 as it would break the Application Binary Compatibility (ABI)
guarantee that we give our customers. Versions 2.2.11 and 2.2.12 are not
binary compatible, therefore, our customers already relying on 2.2.11 would
be left with a broken system if we simply upgraded to 2.2.12.

So in short, this request to rebase will not be filled in the short-term. My
recommendation would be to join our request to Oracle for a build of the
driver against the version of unixODBC that is being shipped with RHEL 5.
This is the proper way to fix this issue without impacting the entire set of
both Red Hat and Oracle customers.

=========================================================

This bug is raised to sort out this problem or atleast provide a workaround
for the issue.

    *
          o
                + 06/24/11 03:16 am ***
                + 06/24/11 03:16 am *** (CHG: Comp. Ver-> 11.2.0.2 -> 2.2.11)
                + 06/26/11 08:58 pm *** (CHG: Sta->16)
                + 06/27/11 01:04 am ***
                + 06/27/11 01:04 am *** (CHG: Sta->15)
                + 06/27/11 01:04 am RESPONSE ***
                + 07/12/11 09:40 pm RESPONSE ***
                + 07/13/11 05:16 am *** (CHG: Sta->20)
                + 07/13/11 05:16 am RESPONSE ***
                + 07/13/11 09:53 pm RESPONSE ***
                  1) The version used by customer is unixODBC 2.2.11 and Oracle ODBC driver
                  11.2.
                  The OS is RHEL 5.5.

With this setup, when they try to use Oracle ODBC driver 11.2 with the
unixODBC 2.2.11, they get the below error

undefined symbol:
SQLGetPrivateProfileStringW

2) Yes that is right "SQLGetPrivateProfileStringW" is defined in
libodbcinst.so . But its available only from 2.2.12 on-wards only.
Due to which they are forced to upgrade their unixODBC from 2.2.11 to 2.2.12
but 2.2.12 is not supported by the OS RHEL 5.5 due to the above said reasons.

Now they are in a deadlock situation. They cannot use the existing unixODBC
2.2.11 nor they can upgrade to 2.2.12

3) There is no mix up. This is a known bug filed with us:
Bug 6676290: ORACLE ODBC DRIVER DEPENDENT ON UNIXODBC 2.2.12
which is closed as document bug.

The purpose of this bug is to get development views on this issue and if it
is feasible to give a new build compatible with unixODBC 2.2.11.

    *
          o
                + 07/13/11 09:53 pm *** (CHG: Sta->15)
                + 08/12/11 10:35 am ***
                + 08/12/11 10:35 am RESPONSE ***
                + 08/24/11 06:53 am RESPONSE ***
                + 08/25/11 05:56 am RESPONSE ***
                + 08/26/11 01:32 am RESPONSE ***
                + 08/26/11 01:33 am *** (CHG: Sta->20)
                + 09/12/11 08:58 pm *** (CHG: Sta->11 Asg->NEW OWNER)
                + 09/12/11 08:58 pm ***
                + 09/13/11 04:19 am ***
                + 09/13/11 04:19 am ***
                + 09/13/11 05:01 am ***
                + 09/13/11 05:01 am ***
                + 09/14/11 09:23 pm ***
                + 10/11/11 10:55 pm *** (CHG: Sta->30)
                + 10/11/11 10:55 pm ***
                + 10/16/11 11:00 pm *** (CHG: Sta->11)
                + 10/16/11 11:00 pm ***