Import a Client Configuration File

Use this procedure to create a binary configuration file from a text client configuration file.

  • Open a command session and run the following command:

    dbutility [options] import [filename]

    where [filename] is an optional parameter to specify a filename other than the default (dbridge.ini). When no option or filename is specified, the import command processes the text file dbridge.ini in the config directory and creates an equivalent binary configuration file, dbridge.cfg, in the same directory. If the file dbridge.ini does not exist in this location, the import command creates a binary configuration file with the default values. If the text file contains errors, the Client returns an error to help you identify the problem and no binary file is created.



    -f filename

    Use this option to specify a filename or path other than the default. If this option is omitted, the Client tries to read the file dbridge.cfg in the config directory of the data source's working directory.

    To indicate a different location, type a backslash (Windows) or forward slash (UNIX) followed by the full path, including filename. For example, /home/user/xyz/foo/myconfig.cfg


    This option is required to allow the existing configuration file to be overwritten with a new file with the same name. Otherwise, the Client will try to read (import) the configuration from a file named dbridge.ini.

    For example, the following command:

    dbutility -u -f dbridge.cfg import

    imports (reads) a file named dbridge.cfg and creates the binary configuration file dbridge.cfg regardless of whether the imported file is a text or binary file.