Db2 Big SQL log files
There are additional log files that are used for problem determination when using Datalake tables. These are referred to as the Db2 Big SQL log files.
In most configurations, the log files are located in the following locations:
- /var/ibm/bigsql/logs
- /mnt/logs/diaglogs/
- /var/log/bigsql/cli
Log files are located on each node that hosts an instance of the specified service.
- The scheduler log file is on the machine that hosts the scheduler.
- Db2® Big SQL and diagnostic log files are on all Db2 Big SQL nodes.
The following table lists the Db2 Big SQL log files and
their default locations.
Log description | Log location |
---|---|
Log directory for Db2 Big SQL java components | /var/ibm/bigsql/logs |
Log directory for Db2 Big SQL scripts | /var/log/bigsql/cli |
Log files for DDL and Java I/O activities |
/var/ibm/bigsql/logs/bigsql-node-$DB2NODE.%i.log where |
Logs for Hive metastore | /var/ibm/bigsql/logs/metastore.log |
Log messages for the standard input/output files for Db2 Big SQL components |
/var/ibm/bigsql/logs/bigsql-start.log /var/ibm/bigsql/logs/metastore.out |
Scheduler log files that exist only on the Db2 Big SQL head node and contains scheduler information | /var/ibm/bigsql/logs/bigsql-sched.log |
Stdout and stderr output from the scheduler | /var/ibm/bigsql/logs/bigsql-sched.out |
Logs related to Db2 Big SQL configuration changes | /var/log/bigsql/cli/bigsql-config.log |
Db2 Big SQL log error messages
Many Db2 Big SQL error messages contain a log entry
identifier, a three-part name that enables you to identify which file to refer to for a
particular error message. The identifier consists of three parts:
LLL-NNN-XXXYYYZZZ
, where:- LLL
- Identifies which type of log file that contains the error, for example:
- BSL
- The Db2 Big SQL log file, /var/ibm/bigsql/logs/bigsql-node-NNN.log, is where most of the diagnostic information for Db2 Big SQL runtime execution is written.
- SCL
- The scheduler log file, bigsql-sched.log, is where the diagnostic information related to the Db2 Big SQL scheduler is written. It exists only on the node on which the scheduler is running, which is normally the Db2 Big SQL head node (/var/ibm/bigsql/logs/bigsql-sched.log).
- NNN
- Identifies the node from which the error came (the DB2® node number).
- XXXYYYZZZ
- Identifies the unique message ID, such that you can search for and find this value in the log file on the particular node.