Install the DATABridge Client on UNIX

Use this procedure for first-time installations and upgrades on all UNIX, Linux, and related systems. In this procedure, you'll install the Client, create a Client working directory, and specify a user ID for the daemon.

If you use a non-English Oracle database, you could run into problems with replicated data that uses decimals. See Running the Oracle Client on a Non-English Database.

Important: Commands, filenames, and often, passwords, are case-sensitive on UNIX systems. Type the commands as shown.

To install the Client on UNIX

  1. Log on using a userid that has root privileges.
  2. If a previous version of the DATABridge Client is running on your system, stop it.
  3. Create a new install directory for DATABridge 6.2 (for example, "/opt/dbridge62").
  4. Move the appropriate tar files (Client, Client Console) to the UNIX system using binary FTP. See Description of Files on the Installation Image.
  5. Change the directory to the install directory you created in step 3 and extract the tar file:

    tar -xvf filename

    where filename is the full tar filename, including location.

    The extract program creates a client subdirectory named after the database (for example, Oracle). Files are extracted to this subdirectory and to the directory you specified.

  6. Next, change the owner and group for the files in the install directory to the userid (and the group to which the userid belongs) designated to run the DATABridge Client (that is, the USERID specified in the file globalprofile.ini). To do this, type the following command:

    chown -R dbridge:users *

    where dbridge is the user ID and users is the corresponding group.

    CAUTION: To prevent the files in the install directory from being accidentally deleted, we recommend that you leave them set to read-only (the default). Before you update the software, to prevent the extraction from failing, either remove all of the files from the install directory or make them writeable until the update is successfully installed.

  7. In the editor, open the sample daemon script file (dbdaemon) located on the root of the install directory, update the necessary environment variables, and then save dbdaemon to the following location:
    • On Linux and Solaris: /etc/init.d
    • On HP-UX: sbin/init.d
  8. Create the directory /etc/Attachmate/DATABridge/6.2
  9. In the editor, open the globalprofile.smp file on the root of the install directory and make the following changes:

    Caution: This file is critical for client operations. If this file is missing or contains the wrong information, the client will not run.

    1. For INSTALLDIR, specify the install directory you created in step 3.
    2. For WORKINGDIR, specify the full name of the Client's working directory for 6.2. If you're upgrading, make sure that the working directory for 6.2 is different from your 6.0 or 6.1 working directory. You create the actual directory later in this procedure.
    3. For USERID, specify the user under which you'll run the daemon. When you start the daemon, you must log in as this user or as the root user. Clients can only be run under this userid.
    4. To enable file security for the Client working directory, specify a value for umask. The bits specified get removed from the default file security bits. A umask of 027 (the default) indicates that the owner bits are unchanged, but the group's w and x bits are reset and all 3 bits are reset for other users. For a stronger mask, specify a value such as 077.
  10. Save the file as globalprofile.ini to the directory /etc/Attachmate/DATABridge/6.2.
  11. Do one of the following:
    • (New installations) In the home directory, use the editor to update your profile (for example, ".profile" or ".bash_profile") and include the environment variable ORACLE_HOME. Consult the Oracle database administrator to determine what this variable should be set to (typically, it's "/opt/oracle..."). You must also include the directory $ORACLE_HOME/bin in the PATH to ensure that the bulk loader sqlldr can be located. You may want to also include the environment variable INSTALLDIR, which points to the directory created in step 3. You can then add the Client program directory $INSTALLDIR/Oracle to the PATH, making it a lot easier to run the Client from the command line.
    • (Upgrades - Optional) Update your profile so that the PATH points to the newly-installed Client.
  12. For the DATABridge Client to find the Oracle shared libraries, add the Oracle lib (or lib32) directory to the appropriate environment variable for your system, as shown in the following table. The line you add after the ORACLE_HOME definition can be used instead of typing the complete Oracle lib directory name.

    To update

    Add the following to your profile

    All 64-bit clients


    32-bit clients on Solaris or Linux


    32-bit clients on AIX


    32-bit clients on HP-UX


    Note: The UNIX shell you use may require that you add a line that exports the environment variable. For instructions, consult your UNIX documentation.

  13. Using the value you specified in step 9b, create a Client working directory for 6.2 that contains the three subdirectories config, locks and logs. (For upgrades, the Migrate program creates a new, secure working directory and subdirectories from this value. See Run the Migrate Program on UNIX.)
  14. When installation is complete, verify that the Client directory files are correctly installed. For a list of installed files, see Files Installed with the DATABridge Client and Client Console.
  15. If you run the Client from a command line, you must also update the environment variable PATH in your profile to include the directory that contains the DATABridge Client. If you installed the Client to the directory /opt/dbridge62, add “:/opt/dbridge62/Oracle” to the PATH. The PATH is defined as:

    PATH=$PATH: … $ORACLE_HOME/bin: …

    where each specified directory is terminated by a colon, except for the last one on the line.

    Individual clients use the database names as the directories names (for example, Oracle).

    Important: Make sure that the mknod utility’s directory (usually /usr/sbin) is included in the PATH. If the shell scripts used to clone data sets cannot find this utility, files will be used in place of named pipes resulting in bulk loader problems, such as broken pipes.

  16. Do one of the following: