Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
When using PHP PDO ODBC I found that UnixODBC reports the following in the ODBC trace log:
[[unixODBC][Driver Manager]Can't open cursor lib 'libodbccr' : file not found]
[ODBC][9797][1310038018.060407][SQLGetDiagRec.c][661]
I found that the way to 'fix' this was:
root@blunt:/usr/lib64/$ ln -s libodbccr.so.2.0.0 libodbccr.so.1
... so I presume UnixODBC is trying to link to libodbccr.so.1 instead of libodbccr.so.2 .
Version-Release number of selected component (if applicable):
x86_64
2.2.14
11.el6
How reproducible:
100%
Steps to Reproduce:
1. Create a PHP file which does this:
$odbc_pdo = new PDO("odbc:mydsn", "myuser", "mypassword");
Actual results:
The connection is created
Expected results:
PHP crashes out and Apache complains that the child process exited unexpectedly.
Additional info:
I presume this is applicable to more general usage of UnixODBC when cursors are being used.
Comment 2RHEL Program Management
2011-07-07 13:07:59 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
I can't reproduce this given what I understand the test case to be, namely create a file test.php containing
<?php
$odbc_pdo = new PDO("odbc:mydsn", "myuser", "mypassword");
?>
and run it with "php -f test.php". It appears to work fine for me,
Please provide a more concrete test case that assumes I know nothing at all about PHP (which is close enough to true).
I had a quite similar error message and solution on a 64-bit Debian:
Can't open cursor lib '/etc/libodbccr.so' : file not found
My solution was to execute "ln -s libodbccr.so.2 libodbccr.so" in the directory "/usr/lib/x86_64-linux-gnu".
My Debian is (according to uname -a) 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt9-3~deb8u1.
After this fix I could successfully connect to a MDB Access database using PHP. The error above was thrown by the 'new PDO' line below:
$sDriver = 'MDBTools';
$sConnection = "odbc:Driver=$sDriver; DBQ=$sFile;";
$db = new PDO($sConnection);
Description of problem: When using PHP PDO ODBC I found that UnixODBC reports the following in the ODBC trace log: [[unixODBC][Driver Manager]Can't open cursor lib 'libodbccr' : file not found] [ODBC][9797][1310038018.060407][SQLGetDiagRec.c][661] I found that the way to 'fix' this was: root@blunt:/usr/lib64/$ ln -s libodbccr.so.2.0.0 libodbccr.so.1 ... so I presume UnixODBC is trying to link to libodbccr.so.1 instead of libodbccr.so.2 . Version-Release number of selected component (if applicable): x86_64 2.2.14 11.el6 How reproducible: 100% Steps to Reproduce: 1. Create a PHP file which does this: $odbc_pdo = new PDO("odbc:mydsn", "myuser", "mypassword"); Actual results: The connection is created Expected results: PHP crashes out and Apache complains that the child process exited unexpectedly. Additional info: I presume this is applicable to more general usage of UnixODBC when cursors are being used.