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.
Tracing
Tracing is not enabled by default. You can enable tracing, set the level of tracing detail that is logged, and set the location of the debug files. To do so, include the -DDEBUG_LEVEL and -DDEBUG_FILE options with the installation command.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 tracing during
installation.
- Installation and deployment log file
- The installation and deployment log file, iad_act.log,
is created by the installation application when you install products
in the HCL
OneDB™ software
bundle.
- UNIX™, Linux™: /tmp/iad_act.log
- Windows™: \tmp\iad_act.log
- Standard output and standard error log files
- The stdout and stderr log files contain important information
that you can use to debug 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 that is generated
by the InstallAnywhere framework.
- UNIX, Linux: $ONEDB_HOME/IBM_Informix_version_Install_date.log
- Windows: %ONEDB_HOME%\IBM_Informix_version_Install_date.log
If the installation application fails, the InstallAnywhere log files are placed in the following directories:
- UNIX, Linux: home directory
- Windows: Desktop
InstallAnywhere return code (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 this command after
the installation application finishes:
echo $?