Log Files for SQL Processes
If you are experiencing problems with a specific SQL statement, you need to provide the log files for SQL processes.
Make sure you have enough free disk space for the log. For more information, see EXAsupport.
There are no prerequisites for this procedure.
Connect to EXAClusterOS (COS) using
c4 connect -t<DEPLOYMENT>/cos. For example:
If you do not specify a node, you will be connected to the first node in the deployment. If the cluster is configured with an access node, the first node is the access node (usually n10). The COS command prompt will tell you which node you are currently connected to:
For more information about c4 commands, see Exasol Deployment Tool (c4).
To find the name of the database, use the ConfD job db_list. For example:
To collect information about SQL processes, use the EXAsupport command-line tool. Specify the start date (
-s) and end date (
-t) using the format
You can collect information for all SQL processes, or for a specific session identified by its session ID.
You can only collect SQL logs for a specific session on the day that the session occurred.
For example, to collect information about all SQL processes:
To collect information about a specific SQL session:
If the log file was created successfully, you will see the following message containing the file name:
To disconnect from EXAClusterOS, use CTRL+D or type
Copy the log file to your local computer using the
scpcommand (secure copy).
Parameter Description $COS_PORT
The SSH port for connecting to EXAClusterOS (COS). Default = 20002
To find the port number in the configuration, use
c4 config | grep CCC_PLAY_SSHD_PORT.
The filename of the SSH private key.
To find the filename in the configuration, use
c4 config | grep CCC_AWS_KEY_PAIR_FILE.
The external IP address of the cluster node that you were connected to when creating the log file.
To find the IP addresses of all nodes, use
$FILENAME The name of the log file that was generated by
exasupportin the previous step.
$LOCAL_FOLDER Path to a folder on your computer where the log file will be stored.
Get the necessary info:
c4 config | grep CCC_AWS_KEY_PAIR_FILE
c4 config | grep CCC_PLAY_SSHD_PORT
N PLAY_ID NODE MEDIUM INSTANCE EXTERNAL_IP INTERNAL_IP STAGE STATE UPTIME TTL
┌─ 1 3a4a7d8d 10 awscf c5d.large 203.0.113.10 10.0.0.10 c running 04:35:15 +∞
│ 1 3a4a7d8d 11 awscf c5d.2xlarge 203.0.113.11 10.0.0.11 d running 04:35:16 +∞
└─ 1 3a4a7d8d 12 awscf c5d.2xlarge 203.0.113.12 10.0.0.12 d running 04:35:15 +∞
Copy the file to your local machine:
To verify that the log was successfully copied, use the
ls command in the target folder on your local machine.
ls -lahtr ~/mylogs | grep exacluster_debuginfo
-rwxr-xr-x 1 user group 9.8K Sep 20 17:38 exacluster_debuginfo_2022_08_11-23_27_20.tar.gz