CRS2008 on RedHAt 5.6 64 bit

Question

I have the following implementation:
RedHat 5.6 64 bit Server
Has Oracle's commercial MySQL 5.5.13 64 bit database running on it with about 2TB of data.
I have unixODBC 32 bit installed and Oracle's 32 bit MySQL client and the 32 bit ODBC drivers installed.
[root@creport ~]# rpm -qa --queryformat="%-%\n" | grep MySQL
MySQL-shared-compat-advanced-x86_64
MySQL-shared-compat-i386
MySQL-server-advanced-x86_64
MySQL-shared-advanced-i386
MySQL-shared-advanced-x86_64
MySQL-client-advanced-i386
[root@creport ~]# ldd /usr/lib/libmysqlclient.so
        linux-gate.so.1 =>  (0xffffe000)
        libpthread.so.0 => /lib/libpthread.so.0 (0xf7bea000)
        libdl.so.2 => /lib/libdl.so.2 (0xf7be5000)
        libm.so.6 => /lib/libm.so.6 (0xf7bbc000)
        librt.so.1 => /lib/librt.so.1 (0xf7bb3000)
        libc.so.6 => /lib/libc.so.6 (0xf7a59000)
        /lib/ld-linux.so.2 (0x00963000)
[creport@creport creport]$ ldd /usr/bin/isql
        linux-gate.so.1 =>  (0xffffe000)
        libodbc.so.1 => /usr/lib/libodbc.so.1 (0x0029b000)
        libodbcinst.so.1 => /usr/lib/libodbcinst.so.1 (0x00286000)
        libdl.so.2 => /lib/libdl.so.2 (0x00af8000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x00add000)
        libc.so.6 => /lib/libc.so.6 (0x00982000)
        /lib/ld-linux.so.2 (0x00963000)
[creport@creport creport]$ ldd /usr/bin/mysql
        linux-gate.so.1 =>  (0xffffe000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x00add000)
        libm.so.6 => /lib/libm.so.6 (0x00b0a000)
        librt.so.1 => /lib/librt.so.1 (0x00aff000)
        libdl.so.2 => /lib/libdl.so.2 (0x00af8000)
        libncurses.so.5 => /usr/lib/libncurses.so.5 (0x00833000)
        libc.so.6 => /lib/libc.so.6 (0x00982000)
        /lib/ld-linux.so.2 (0x00963000)
[creport@creport creport]$
[root@creport ~]# isql [someDSN] user password
returns:
Connected!
sql-statement
help [tablename]
quit
So I can run isql fine to obtain a connection to and from the server using the ODBC DSN and the 32 bit drivers/client.
I can connect to CMC fine on a separate host and can upload Crystal Reports to the server with IDENTICAL DSN names and drivers from another Windows workstation where the CR2008 client is installed.
However whenever I try to view the data on the CRS2008 server i the CMC console I get an error... "Failed to open the connection".
I get a vague feeling there is something missing in the install but not sure what as the installation document is a tad vague on prerequisite specifics.
Anyone got any hints or clues?
Is there a CRS2008 log file can read that might throw any light on the error? I might be able to at least tail that as the report is attempted to be viewed and see the error that way (if it says anything helpful that is).
Yes aware of CRYSTAL REPORTS SERVER 2008 V1 SP3 FOR LINUX u2013 SUPPORTED PLATFORMS doc and it states:
Note 1: Crystal Reports Server 2008 V1 software is supported running on 32-bit versions of Linux running on x86 (32-bit) and x64 CPUs (64-bit) made by AMD and Intel. Crystal Reports Server 2008 V1 software is supported running on 64-bit versions of Linux running on x64 CPUs made by AMD and Intel if it can reference the 32-bit operating system libraries as well as the 32-bit database and application client libraries.
Dom
Edited by: DomBaines on Jun 16, 2011 11:24 AM

Answer 1

Yes.. as I posted. HOWEVER makes sure command line isql works FIRST, I mean standard out of the box unixodbc!
For some reason that  isn't sensitive to the whitepsace or comments in odbc.ini file.
The keys are:
no white space after or before the = in the ini file.
use the WHOLE path to the driver file not the alias or the odbcinst.ini alias. (but it sometimes works which doesn't help either)
I got it to work using BOTH 5.1.8 and 3.51 drivers but apparently (you;d have to check with SAP) the 5 versions are not 'supported' wierd but that's what they told me.
For some reason on the desktop client Windows boxes I also had to add the ip to hostname into the hosts file so that the crafted reports DSN settings worked. Of course you can through CMC change the database connection.
BTW I could not get it to work on CentOS or Fedora even though are based on the same RedHat core and SAp doesn't suppoprt installs on them anyway.
Dom