Using Sybase
These are some of the adventures I had when setting up our QE to run with the new Sybase Driver on Linux x86.
We download the EAServer developer edition 5.2. Installation of this was pretty standard, a java-based wizard with the usual Next->Next->Finish routine. Installed in /opt/sybase/EAServer
From the docs, the next thing to do was start the EAServer. I ran /opt/sybase/EAServer/bin/serverstart.sh, and the first thing I hit was
jagsrv: error while loading shared libraries: libstdc++.so.2.8: cannot open shared object file: No such file or directory
Blimely, that's an old one ... 2.8 !! I had to install the "compat" libraries on the Suse Linux 9.0, but on the newer openSuse 11.0, that wasn't even an option (the compat rpm only goes back as far as 2.9 ). So we won't be running this on openSuse then .....
After that, he seemed happy, and the server happily reports
8<
Starting services...
Done binding to all configured Name Servers.
Accepting connections.
>8
It seems that EAServer does come with a sample DB, but John O'M had recommend using SQLAnywhere from Sybase. So I got a development version from
http://www.sybase.com/products/database ... qlanywhere
Again, this install went through pretty painlessly, and the nice people at Sybase (or rather the nice robot mailer) sent me a development license key.
I used the following to start the sample DB (in the background)
>> . /opt/sqlanywhere11/bin32/sa_config.sh
>> dbspawn dbeng11 -n mydemo11 /opt/sqlanywhere11/demo.db
Next step was defining an ODBC DSN. I think that SQLAnywhere provide their own ODBC implementation, but ideally, I'd like to continue to use our existing unixODBC setup (it has worked fine for DB2, Mysql, Adabas-D and Postgres!)
The SQLAnywhere docs recommend that I set the ODBCINI env variable, so
export ODBCINI=/usr/local/etc/odbc.ini
and in my odbc.ini I have
[My_DSN]
Driver=/opt/sqlanywhere11/lib32/libdbodbc11.so
DatabaseFile=/opt/sqlanywhere11/demo.db
When I started the Portus and tried to run our QE, the My_DSN DSN was found OK, but it just seg faulted in the middle of nowhere. So, at guess, I sourced the sa_config file and everything seemed kosher.
E.g
if test -e "/opt/sqlanywhere11/bin32/sa_config.sh"; then
echo "Setting Sybase Environment : "
source /opt/sqlanywhere11/bin32/sa_config.sh
export ODBCINI=/usr/local/etc/odbc.ini
fi
/usr/local/portus/apache2/bin/apachectl start
We download the EAServer developer edition 5.2. Installation of this was pretty standard, a java-based wizard with the usual Next->Next->Finish routine. Installed in /opt/sybase/EAServer
From the docs, the next thing to do was start the EAServer. I ran /opt/sybase/EAServer/bin/serverstart.sh, and the first thing I hit was
jagsrv: error while loading shared libraries: libstdc++.so.2.8: cannot open shared object file: No such file or directory
Blimely, that's an old one ... 2.8 !! I had to install the "compat" libraries on the Suse Linux 9.0, but on the newer openSuse 11.0, that wasn't even an option (the compat rpm only goes back as far as 2.9 ). So we won't be running this on openSuse then .....
After that, he seemed happy, and the server happily reports
8<
Starting services...
Done binding to all configured Name Servers.
Accepting connections.
>8
It seems that EAServer does come with a sample DB, but John O'M had recommend using SQLAnywhere from Sybase. So I got a development version from
http://www.sybase.com/products/database ... qlanywhere
Again, this install went through pretty painlessly, and the nice people at Sybase (or rather the nice robot mailer) sent me a development license key.
I used the following to start the sample DB (in the background)
>> . /opt/sqlanywhere11/bin32/sa_config.sh
>> dbspawn dbeng11 -n mydemo11 /opt/sqlanywhere11/demo.db
Next step was defining an ODBC DSN. I think that SQLAnywhere provide their own ODBC implementation, but ideally, I'd like to continue to use our existing unixODBC setup (it has worked fine for DB2, Mysql, Adabas-D and Postgres!)
The SQLAnywhere docs recommend that I set the ODBCINI env variable, so
export ODBCINI=/usr/local/etc/odbc.ini
and in my odbc.ini I have
[My_DSN]
Driver=/opt/sqlanywhere11/lib32/libdbodbc11.so
DatabaseFile=/opt/sqlanywhere11/demo.db
When I started the Portus and tried to run our QE, the My_DSN DSN was found OK, but it just seg faulted in the middle of nowhere. So, at guess, I sourced the sa_config file and everything seemed kosher.
E.g
if test -e "/opt/sqlanywhere11/bin32/sa_config.sh"; then
echo "Setting Sybase Environment : "
source /opt/sqlanywhere11/bin32/sa_config.sh
export ODBCINI=/usr/local/etc/odbc.ini
fi
/usr/local/portus/apache2/bin/apachectl start