I have installed Shib2.1 SP and facing issues while starting the shibd. Looks like the issue it’s an issue with ODBC drivers. I am using Oracle database with unixODBC 2.2.11 on Red Hat Enterprise Linux AS release 4 (Nahant Update 3)
Here is the error message “ODBC Error: 01000:1:0:[unixODBC][Driver Manager]Can't open lib '/opt/oracle/lin64-10.2.0.4i/lib/libsqora.so.10.1'”
I just want know if there is any recommended ODBC driver for oracle for Shib2.1?
Thanks,
Vijay
We use ojdbc14.jar on oru 2.1.2 IDP, which shipped with our Oracle 10g installation. I would recommend sticking with the driver provided by your flavor of Oracle. But looking at your error, I have to ask the obvious question…does /opt/oracle/lin64-10.2.0.4i/lib/libsqora.so.10.1 exist?
Good luck,
James
Note that the OP asked about the SP (ODBC), not the IdP (JDBC).
cheers,
-peter
Thanks for the note
I double checked it and the file is available at that location and it's
a 64-bit shared library.
Any suggestions?
Thanks,
Vijay
Nope.
-- Scott
Currently I am using Shib SP 1.3 on Solaris. SHAR Extensions Library is using oracle to store the session details. I believe OCI is used here to connect to the database.
Also I think we are not configuration any driver details in SP 1.3. Whereas in Shib 2.1 we are giving the driver/DB details in shibboleth.xml file.
I am trying to understand the difference in the way the database connection is made in Shib1.3 and Shib2.1. Currently I am facing driver issues while connecting to the database with Shib2.1. So I am wondering if there is any alternate approach for it
Please let me know if you need any specific details to understand the problem
Thanks,
Vijay
It's not a plugin from me, but yes, I believe that's true.
> Also I think we are not configuration any driver details in SP 1.3.
Whereas
> in Shib 2.1 we are giving the driver/DB details in shibboleth.xml file.
Somewhere your OCI code has to know how to connect, but I doubt if it would
be in the SP's configuration file, and it certainly isn't a driver
connection string, no.
> I am trying to understand the difference in the way the database
connection
> is made in Shib1.3 and Shib2.1.
OCI is an Oracle interface. ODBC is, well, ODBC. Are you not familiar with
it? The difference is a native library compared to a portable API with a
driver that handles the database details and talks to Oracle.
> Currently I am facing driver issues while
> connecting to the database with Shib2.1. So I am wondering if there is any
> alternate approach for it
You can write your own plugin, or get ODBC working, or switch databases. Or,
as I would actually suggest, reconsider your session design/needs such that
you can avoid clustering the SP at all where possible. Another option is to
share a shibd process between all the Apache servers. All of that is
discussed in the wiki at length.
Any specific ODBC issue with your database is not something I can address,
and I have no Oracle testing capability, so I haven't tried it. Others have
I think, though not recently.
-- Scott