Manually Configure Sybase Lite Connectivity

  1. Edit the file bin/openlink.ini, and make sure the environment section for the driver contains the right entries. For the SQL Server Lite Driver, this section looks like this:

    [Environment SQLServer 2000] FREETDSCONF = /home/openlink/bin/freetds.conf DSQUERY = SQLSERVER ; Load this section from freetds.conf TDSHOST = host.domain ; Point this to your SQLServer machine TDSPORT = 1433 TDSVER = 7.0 SQLSERVER_CATALOG = Y CURSOR_SENSITIVITY = LOW ; Set to HIGH after loading oplrvc.sql

    These environment varable values are database specific and are described in detail later in this section. In the case of SQLServer Driver, you only need to set the TDSHOST variable correctly. The FREETDSCONF variable is automatically set by the installer. Under normal conditions you do not have to modify the freetds.conf file nor the DSQUERY variable.
  2. Edit the file bin/odbc.ini and change the sample DSN found there to match your environment:

    [sql_lite] Driver = /home/openlink/lib/ Description = Sample SQLServer 2000 Lite Connection ServerType = SQLServer 2000 Username = Password = Database = ReadOnly = no FetchBufferSize = 60 Options = -H -P 1433 -V 8.0

    For the SQL Server/Sybase Driver, you typically only need to modify Username, Password, Database, and Options. All modifications except the Driver keyword will be saved when reinstalling this or any other Lite Driver.
  3. For most Lite drivers the LD_LIBRARY_PATH (or SHLIB_PATH or LIBPATH) environment variables must be set before you can load the driver. Therefore you will not find any mention of them in the openlink.ini file, as the settings found here are set by the driver after it is loaded.
  4. If the installer finds the right environment variables, e.g. INFORMIXDIR, it will note the appropriate LD_LIBRARY_PATH settings, and add them automatically to the and openlink.csh scripts. This script appropriate to your shell must be run before you do anything with the Lite Drivers, e.g.:

    . ./ source ./openlink.csh

    If this script is not properly executed, then the system loader library will give an error message stating it cannot find some dependent shared libraries to load.

Referenced by...