General Troubleshooting Procedures
If you have problems using the DATABridge Client, complete the following steps:
- Check to see that your system meets the minimum hardware and software requirements. For details, see the DATABridge Installation Guide.
- Check that you've selected the correct configuration options for connecting to the relational database server:
- Relational database name
- Your user ID to log in to the relational database server
- Your password to log in to the relational database server
- Does your user ID to the relational database server have the correct privileges?
- If you are using configuration file parameters or environment variables to supply the database signon parameters, did you enter them correctly?
- If you are using command line options, did you enter them in their correct uppercase or lowercase? Did you enter them with each dbutility command? See dbutility Command-Line Options.
- If you are running a UNIX Client, make sure that the ORACLE_HOME, SHLIB_PATH, and LD_LIBRARY_PATH variables point to the correct directory, (for example, ORACLE_HOME = opt/oracle/lib).
- Check that you've selected the correct configuration options for connecting to the host.
- Is the DATABridge Server Accessory running on the host?
- Did you use the data source name as it is defined in the DBServer control file? For more information, refer to the DATABridge Host Administrator’s Guide.
- Did you enter the correct host name or IP address?
- Did you enter the TCP/IP port number as it is defined in the DBServer control file?
- If there is a password defined in the Server Accessory parameter file, did you enter the correct password?
- Make sure that the PATH environment variable contains the DATABridge Client’s directory and the appropriate relational database bin directory (named bin for Oracle and binn for Microsoft SQL Server).
If you do not include these directories in the PATH, errors will occur when you run the bulk loader.
- Check your cable connections to make sure that they are securely attached.
- Check the following:
- Is the DBServer (on the mainframe) running?
- Is the network operational?
- Is the relational database service running?
- Determine whether the problem is caused by the host and DMSII (versus DBServer and DATABridge Client) by using the DATABridge Span Accessory on the host to clone a data set from the DMSII database in question.
- If you cannot clone the data set, the problem is most likely on the host.
- If you can clone the data, the problem is most likely occurring between the DBServer and DATABridge Client.
- Resolve any errors. If you receive error messages or status messages that you don’t understand, see Appendix A.
- If you cannot identify and solve the problem without assistance, contact your product distributor or Attachmate Technical Support (http://support.attachmate.com/contact/) from a location where you have the ability to run dbutility.