STARTUP.DOC
资源名称:likoxglc.taz [点击查看]
上传用户:canger333
上传日期:2013-01-31
资源大小:454k
文件大小:5k
源码类别:
Oracle数据库
开发平台:
Unix_Linux
- Combined OpenLinkODBC / iODBC release
- OpenLink Software
- 1. Introduction
- Welcome to the combined release of OpenLink ODBC for Unix and Ke Lin's
- iODBC driver manager. This kit will provide you with everything you
- need in order to develop ODBC compliant applications under Unix
- without having to pay royalties to other parties.
- This kit consists of a number of parts:
- o Ke Lin's iODBC driver manager. This is a complete implementation of
- an ODBC driver manager, released under the GNU General Public
- License. We fully comply with the GPL by giving you this product in
- source form (as well as the binary form).
- o The OpenLink ODBC multi-tier driver. This high-performance driver
- cooperates with our range of server products in order to give you
- the ODBC performance you are used from us. The driver is shipped in
- the form of a shared library file, with a system-dependent name.
- o A simple example, odbctest.c, which gives you a command-line
- interface to SQL. You can fit this to your purposes, but at the
- very least this is useful for verification of your ODBC
- installation.
- You can use all parts stand-alone, if you wish. Our ODBC driver will
- correctly cooperate with other vendor's ODBC driver managers, if you
- wish to do so.
- 2. Installation of run-time distribution
- You probably already unpacked this distribution. The next step is to
- make sure that your applications can find all the dynamic link
- libraries. Depending on your system's implementation of dynamic link
- libraries, you have a number of options:
- o Install the libraries in a directory that is searched by your
- linker by default. Typical locations are /usr/lib and
- /usr/local/lib.
- o Install the libraries in some other place, and make sure that the
- environment variable your dynamic linker uses to find extra locations
- for dynamic link libraries. Most systems use the environment variable
- LD_LIBRARY_PATH to this end. Exeptions are AIX which uses LIBPATH
- and HP/UX which uses SHLIB_PATH.
- If your system has a C compiler, you can verify the installation by
- compiling the odbctest program. Otherwise, you may have ODBC
- applications installed on your system which you can use.
- 3. Configuration of run-time distribution
- The iODBC driver manager looks for a file ~/.odbc.ini, where the tilde
- stands for the user's home directory. This file only contains a default
- section where you can select which driver library to use. Copy the
- odbc.ini file from the examples directory to ~/.odbc.ini and make
- sure the right path and filename is used for your installation.
- Our driver looks for a file pointed to by the environment variable
- UDBCINI, or the file /etc/udbc.ini if the environment variable is not
- defined. This file is located in the openlink/bin directory.
- The configuration file format is very close to the Windows .INI file
- format. A data source is a section (enclosed in square parenthesis),
- and the attributes for a data source are given within this section.
- The most important attribute to iODBC for each datasource is the
- Driver attribute. This must point to the shared library for the ODBC
- driver associated with the data source.
- Our driver has a number of attributes which can be set for a data
- source. Here is a description (with ODBC connect string tags between
- parenthesis):
- Host
- The hostname where the database resides (HOST).
- ServerType
- The type of server (see oplrqb.ini on the server, SVT).
- ServerOptions
- Server-specific extra options. See OpenLink server documentation
- for agents which can use this.
- Database
- The database to use (DATABASE).
- Options
- Connect options for the database (OPTIONS).
- UserName
- The name of the user (a password cannot be specified in the
- UDBCINI file, UID/PWD).
- ReadOnly
- A Yes/No value in order to make the connection read-only
- (READONLY=Y/N).
- FetchBufferSize
- The number of records that are transferred in a single call to
- the server. Default is 5; maximum is 99, minimum is 1
- (FBS=value).
- Protocol
- The protocol to use. Leave set to ``TCP'' for this release.
- Apart from these data source-specific settings, you may add a section
- called [Communications], which you may use to tune our driver further:
- ReceiveTimeout
- The time the client application will wait for the database agent
- to finish the request (default is 60 seconds).
- BrokerTimeout
- The time the client application will wait for the request broker
- to accept of reject a database connection (default is 30
- seconds).
- SendSize
- RPC send buffer size. A value of 0 (the default) will cause the
- application to use system-dependent defaults.
- ReceiveSize
- RPC receive buffer size. A value of 0 (the default) will cause
- the application to use system-dependent defaults.
- DebugFile
- If set, the name of a file to which debugging output from the
- driver should be directed.