Verifying that library files are linked to data source client software

For best results, always verify that the library files are correctly linked to the data source client software before you use the CREATE WRAPPER command to register the wrapper. This task applies only when the federated server uses UNIX and the data source client is Informix®, Oracle, Sybase, or Teradata.

About this task

When you install federation, you can choose to configure wrappers automatically. If you install the data source client software on the federated server before you install federation on the server and choose to configure the wrapper automatically during the installation program, the wrapper library files are linked to the corresponding data source client software. Linking the wrapper library files depends on the data source.
  • Informix, Sybase, and Teradata data sources:

    If you install the data source client software after you install federation, for example to update to a new version of the client, you must manually link the wrapper library files to the data source client software.

  • Oracle data source:

    The wrapper library files are linked dynamically. Dynamic linking will load the Oracle client library at runtime and automatically resolve the Oracle Call Interface (OCI) function address.

These are the common causes of link failure:
  • A required environment variable is not available during installation.
  • The data source client is not installed on the federated server.
  • The data source client that is installed on the federated server is not at a supported level.

Procedure

To verify that library files are correctly linked:

Procedure

  1. Open the message file for the data source. The message file is in the directory where the federated server is installed, in the lib32 or lib64 subdirectory. This table lists the data sources, message files, and library files.
    Table 1. Data sources, message files, and library files
    Data source Message file Library files
    Informix djxlinkInformix.out

    AIX - libdb2informix.a
    HP-UX - libdb2informix.so
    Linux - libdb2informix.so
    Solaris - libdb2informix.so
    Sybase djxlinkSybase.out

    AIX - libdb2ctlib.a
    HP-UX - libdb2ctlib.so
    Linux - libdb2ctlib.so
    Solaris - libdb2ctlib.so
    Teradata djxlinkTeradata.out

    AIX - libdb2teradata.a
    HP-UX - libdb2teradata.so
    Linux - libdb2teradata.so
    Solaris - libdb2teradata.so
  2. Evaluate the contents of the message file:
    • If linking succeeded, the library file displays in the directory where federation is installed, and the message file displays a success message.
    • If linking failed, the message file displays an error message. If neither the library file nor the message file display in the directory where federation is installed, you must manually link the library file to the data source client software.