Filter
Top Products
WebSphere Application Server is the last service to stop when you shut
down Tivoli Intelligent Orchestrator, so this log file is useful for verifying
whether the shutdown completed. It is located in the %WAS_HOME%\logs\
server1 directory on Windows systems ($WAS_HOME/logs/server1 on UNIX
or Linux).
Look for Server <server-name> stop completed for a successful shutdown
of the WebSphere Application Server.
SystemErr.log
This is the log file that contains Java exceptions and stack traces caused by
the enterprise applications. It is located in the %WAS_HOME%\logs\server1
directory on Windows systems ($WAS_HOME/logs/server1 on UNIX or
Linux).
DB2 Universal Database
The DB2 Universal Database error logs are stored in the %DB2_HOME%\DB2 directory
on Windows
®
systems ($DB2_HOME/db2dump on UNIX or Linux), where %DB2_HOME%
is the default DB2 home directory.
Check the following log file for errors:
db2diag.log
When an error occurs, the db2diag.log is updated with information about
the error. This is the primary log to use when debugging DB2 Universal
Database problems.
db2alert.log
If an error is determined to be an alert, then an entry is made in the
db2alert.log file and to the operating system or native logging facility.
dump
files
For some error conditions, additional information is logged in external
binary dump files named after the failing process ID. These files are
intended for DB2 Universal Database Customer Support.
trap
files
The database manager generates a trap file if it cannot continue processing
because of a trap, segmentation violation, or exception. Trap files contain a
function flow of the last steps that were executed before a problem
occurred.
Other
useful DB2 Universal Databasecommands include:
db2trc This command gives you the ability to control tracing.
db2support
This command collects environment information and log files and places
them into a compressed archive file.
Directory Server
Trace logs for the LDAP server are stored in the <LDAP_Install_Directory>\
appsrv\logs
directory, where <LDAP_Install_Directory> is the installation
directory for the LDAP server.
Check the following log files for errors:
v ibmslapd.log
v audit.log
Chapter 6. Middleware prerequisite log files 53