Client installation troubleshooting

Installation log files and return codes can provide helpful information about a completed installation or help you identify problems encountered during an installation attempt.

Log files

When you install the database server, the installation application generates log files in the same directory as the installation media. You can change the default location of your log files and enable debugging mode during installation.
Install and Deployment log file
The Install and Deployment log file iad_act is created for any installation by using the HCL OneDB™ software bundle.
  • UNIX™, Linux™: /tmp/iad_act
  • Windows™: \tmp\iad_act
Standard-Out and Standard-Error log files
The Standard-Out and Standard-Error log files contain important debug information for use during installation failures.
  • UNIX, Linux: /tmp/bundle_install.stdout and /tmp/bundle_install.stderr
  • Windows: \tmp\bundle_install.stdout and \tmp\bundle_install.stderr
InstallAnywhere log file
The InstallAnywhere log file contains information about the installation by using the InstallAnywhere framework.
  • UNIX, Linux:
    • Client SDK installation: $ONEDB_HOME/IBM_Informix_Client-SDK_version_Install_date.log
    • OneDB Connect installation: $ONEDB_HOME/IBM_Informix_Connect_version_Install_date.log
    • Client SDK installation that includes Global Language Support (GLS): $ONEDB_HOME/IBM_Informix_GLS_version_Install_date.log
  • Windows:
    • Client SDK installation: %ONEDB_HOME%\IBM_Informix_Client-SDK_version_Install_date.log
    • OneDB Connect installation: %ONEDB_HOME%\IBM_Informix_Connect_version_Install_date.log
    • Client SDK installation that includes Global Language Support (GLS): %ONEDB_HOME%\IBM_Informix_GLS_version_Install_date.log

If the installation application fails, the InstallAnywhere log files are placed in the following directories:

  • UNIX, Linux: in your home directory.
  • Windows: on the Windows Desktop.

Debug and tracing

You can set the level of tracing detail that is used and the location of the debug file by specifying the DDEBUG_LEVEL and DDEBUG_FILE options on the installation command. By default tracing is turned off. For more information, see Client products installation command syntax.

Return codes (UNIX, Linux)

You can check the InstallAnywhere return code, also known as the exit code, after running the installation application to learn more about the installation status and possible error conditions. To retrieve the return code, run the following command after the installation application finishes:

echo $?

For information about the meanings of the InstallAnywhere return codes, see the documentation at the Flexera Software website: http://www.flexerasoftware.com.