The Oracle ODBC driver story
in [Oracle]
|
From: Maxim Demenko on 11 Jun 2010 15:18 On 11.06.2010 15:59, Mladen Gogala wrote: > On Fri, 11 Jun 2010 06:19:27 -0700, John Hurley wrote: > product is described here: http://rlib.sicompos.com Thank you for sharing, that looks interesting. But back to odbc driver - if i understood it correctly from the Bugzilla, the problem should disappear with newer (compared to shipped with redhat) unixODBC version ? Then, why don't you try it this way? Best regards Maxim
From: Mladen Gogala on 11 Jun 2010 15:43 On Fri, 11 Jun 2010 09:56:56 -0700, joel garry wrote: > Why don't you ask Wim Coekaerts? I don't know the gentleman. I, of course, know of him but I don't want to pester people that I've never met with personal emails. > > I suppose you could have rlib talk to something else with native links > that then talks to Oracle... or have a 10g intermediary... I'm assuming > you are on some 11g? Actually, no, I am not. The database in question is 10.2.0.5. The same problem happens with every version after 10.2.0.3. Version 10.2.0.3 doesn't work because of some unresolved symbol on Red Hat 5. > > You mentioned compiling it from source? Isn't that the DIY way? Yes, it works that way, but I have to compile and configure the machine manually and my boss is reluctant to allow me to do that on the production box. -- http://mgogala.byethost5.com
From: joel garry on 11 Jun 2010 16:56 On Jun 11, 12:43 pm, Mladen Gogala <n...(a)email.here.invalid> wrote: > On Fri, 11 Jun 2010 09:56:56 -0700, joel garry wrote: > > Why don't you ask Wim Coekaerts? > > I don't know the gentleman. I, of course, know of him but I don't want to > pester people that I've never met with personal emails. > Fair enough. I imagine you aren't many degrees of freedom away from him, though - I see him publicly on linkedin, for example (I despise linkedin, but when I log in I see someone could introduce me to him, should I care, and he does say he shares expertise - I would go out on a limb and guess he wants to evangelize and make it work better). I imagine doing things through support adds degrees. > > > > I suppose you could have rlib talk to something else with native links > > that then talks to Oracle... or have a 10g intermediary... I'm assuming > > you are on some 11g? > > Actually, no, I am not. The database in question is 10.2.0.5. The same > problem happens with every version after 10.2.0.3. Version 10.2.0.3 > doesn't work because of some unresolved symbol on Red Hat 5. And here I've been complaining about stuff that doesn't work on hp-ux because it has linux syntax, lol! Oracle cross platform compatibility - makes all platforms red-headed stepchildren. > > > > > You mentioned compiling it from source? Isn't that the DIY way? > > Yes, it works that way, but I have to compile and configure the machine > manually and my boss is reluctant to allow me to do that on the > production box. Fair enough. Any manual operations are subject to non-repeatability. I often even script things I only intend to do once. jg -- @home.com is bogus. Data and death: http://www.msnbc.msn.com/id/37612199/ns/us_news-life/
From: Mladen Gogala on 11 Jun 2010 21:22 On Fri, 11 Jun 2010 13:56:44 -0700, joel garry wrote: >> Yes, it works that way, but I have to compile and configure the machine >> manually and my boss is reluctant to allow me to do that on the >> production box. > > Fair enough. Any manual operations are subject to non-repeatability. I > often even script things I only intend to do once. That's the problem. Getting it to work is not the problem: [mgogala(a)medo ~]$ isql ora11 scott tiger +---------------------------------------+ | Connected! | | | | sql-statement | | help [tablename] | | quit | | | +---------------------------------------+ SQL> select * from dept; +-------+---------------+--------------+ | DEPTNO| DNAME | LOC | +-------+---------------+--------------+ | 10 | ACCOUNTING | NEW YORK | | 20 | RESEARCH | DALLAS | | 30 | SALES | CHICAGO | | 40 | OPERATIONS | BOSTON | +-------+---------------+--------------+ SQLRowCount returns -1 4 rows fetched SQL> [mgogala(a)medo ~]$ isql --version unixODBC 2.3.0 [mgogala(a)medo ~]$ If you take a look at the version, you will see that unixODBC version is 2.3.0. Unfortunately, I had to link that myself, it wasn't in a repository package. I am not asking how to get it working, I did that a long time ago. The problem is the fact that Oracle is shipping the driver which doesn't work with the official OS packages. I can't ask my system administrator to install unixODBC-2.3.0-1-el5.386.rpm because there is no such thing in any repository. The version in the repository is 2.2.11: [mgogala(a)medo ~]$ rpm -qa|grep unixODBC unixODBC-devel-2.2.11-7.1 unixODBC-2.2.11-7.1 [mgogala(a)medo ~]$ Oracle ODBC drivers shipped with the RDBMS, as well as the ones shipped with the instant client(s) do not work with the version 2.2.11. Linking things by myself means no maintenance, no automatic updates, no platform specific configuration manuals and a lot of dependency upon the DBA. This is what happens with unixODBC-2.2.11: [mgogala(a)medo tmp]$ isql ora11 scott tiger isql: symbol lookup error: /usr/lib/oracle/11.2/client/lib/ libsqora.so.11.1: undefined symbol: SQLGetPrivateProfileStringW [mgogala(a)medo tmp]$ isql --version unixODBC 2.2.11 This has been going on for more than a year. It is really, really, really annoying. Even funnier thing is that Oracle does the same thing with OEL. That doesn't work either. That, in particular, means that Oracle Corp. is shipping a non-functional product. I wonder what will happen with Solaris? If the QA remains the same as for Linux, the SUN might turn into a black hole, and soon. -- http://mgogala.byethost5.com
From: Tim X on 13 Jun 2010 21:44
Mladen Gogala <gogala.mladen(a)gmail.com> writes: > On Fri, 11 Jun 2010 13:56:44 -0700, joel garry wrote: > > >>> Yes, it works that way, but I have to compile and configure the machine >>> manually and my boss is reluctant to allow me to do that on the >>> production box. >> >> Fair enough. Any manual operations are subject to non-repeatability. I >> often even script things I only intend to do once. > > That's the problem. Getting it to work is not the problem: > > > [mgogala(a)medo ~]$ isql ora11 scott tiger > +---------------------------------------+ > | Connected! | > | | > | sql-statement | > | help [tablename] | > | quit | > | | > +---------------------------------------+ > SQL> select * from dept; > +-------+---------------+--------------+ > | DEPTNO| DNAME | LOC | > +-------+---------------+--------------+ > | 10 | ACCOUNTING | NEW YORK | > | 20 | RESEARCH | DALLAS | > | 30 | SALES | CHICAGO | > | 40 | OPERATIONS | BOSTON | > +-------+---------------+--------------+ > SQLRowCount returns -1 > 4 rows fetched > SQL> > [mgogala(a)medo ~]$ isql --version > unixODBC 2.3.0 > [mgogala(a)medo ~]$ > > > If you take a look at the version, you will see that unixODBC version is > 2.3.0. Unfortunately, I had to link that myself, it wasn't in a > repository package. I am not asking how to get it working, I did that a > long time ago. The problem is the fact that Oracle is shipping the driver > which doesn't work with the official OS packages. I can't ask my system > administrator to install unixODBC-2.3.0-1-el5.386.rpm because there is no > such thing in any repository. The version in the repository is 2.2.11: > > [mgogala(a)medo ~]$ rpm -qa|grep unixODBC > unixODBC-devel-2.2.11-7.1 > unixODBC-2.2.11-7.1 > [mgogala(a)medo ~]$ > > Oracle ODBC drivers shipped with the RDBMS, as well as the ones shipped > with the instant client(s) do not work with the version 2.2.11. Linking > things by myself means no maintenance, no automatic updates, no platform > specific configuration manuals and a lot of dependency upon the DBA. This > is what happens with unixODBC-2.2.11: > > [mgogala(a)medo tmp]$ isql ora11 scott tiger > isql: symbol lookup error: /usr/lib/oracle/11.2/client/lib/ > libsqora.so.11.1: undefined symbol: SQLGetPrivateProfileStringW > [mgogala(a)medo tmp]$ isql --version > unixODBC 2.2.11 > > This has been going on for more than a year. It is really, really, really > annoying. Even funnier thing is that Oracle does the same thing with OEL. > That doesn't work either. That, in particular, means that Oracle Corp. is > shipping a non-functional product. I wonder what will happen with > Solaris? If the QA remains the same as for Linux, the SUN might turn into > a black hole, and soon. Although not a great solution, something I've used in the past which addresses some of your concerns is to create your own rpm package. It has been a while since I've worked with RPMs, so I can't remember the exact details, but it goes something like 1. Download the src rpm for the existing odbc ersion 2. Unpack the rpm and replace the source tree with the new version. 3. Update the version number in the spec file 4. Re-build the rpm and test If it works, you can then use this rpm to install the updated driver on all the systems where you need it. The advantage of doing this is you get standard installs on all systems and because it is an rpm update, you will be alerted to updates/new versions that come form your vendor. The downside is that your still going to be responsible for monitoring for security issues and updating your rpm and re-installing when any occur. However, I don't think there is any fix for this. Creating new rpms from existing ones is at least quite easy. Tim -- tcross (at) rapttech dot com dot au |