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.

Prerequisite

There are no prerequisites for this procedure.

Procedure

The ConfD examples are written in Bash on a Linux terminal running the Exasol tool confd_client, which is accessed by connecting to EXAClusterOS on the database nodes using Exasol Deployment Tool (c4). You can also interact with ConfD from an external tool using Python and XML-RPC. For more information, see ConfD.

Placeholder values are indicated with UPPERCASE characters. Replace the placeholders with your own values.

  1. Connect to EXAClusterOS (COS) using c4 connect -t<DEPLOYMENT>/cos. For example:

    c4 connect -t1/cos

    If you do not specify a node, you will normally 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 indicates which node you are currently connected to. 

    [root@n10 ~]#

    For more information about c4 commands, see Exasol Deployment Tool (c4).

  2. To find the name of the database, use the ConfD job db_list:

    confd_client -c db_list

  3. To collect information about SQL processes, use the EXAsupport command-line tool (exasupport). Specify the start date (-s) and end date (-t) using the format YYYY-MM-DD.

    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.

    Examples

    To collect information about all SQL processes: 

    exasupport -s 2022-08-11 -t 2022-08-11 -e DB_NAME -x2

    To collect information about a specific SQL session:

    exasupport -s 2022-08-11 -t 2022-08-11 -e DB_NAME -i SESSION_ID

    If the log file was created successfully, you will see the following message containing the file name:

    Successfully stored debug information into file /exa/tmp/support/exacluster_debuginfo_2022_08_11-23_27_20.tar.gz

  4. To disconnect from EXAClusterOS, use CTRL+D or type exit.

  5. Copy the log file to your local computer using the scp command (secure copy). 

    scp -P $COS_PORT -i ~/.ssh/$KEY root@$DATABASE_IP:/exa/tmp/support/$FILENAME $LOCAL_FOLDER
    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.
    $KEY

    The filename of the SSH private key.

    To find the filename in the configuration, use c4 config | grep CCC_AWS_KEY_PAIR_FILE.
    $DATABASE_IP

    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 c4 ps.

    $FILENAME The name of the log file that was generated by exasupport in the previous step.
    $LOCAL_FOLDER Path to a folder on your computer where the log file will be stored.

    Example

    Get the necessary info: 

    c4 config | grep CCC_AWS_KEY_PAIR_FILE
    CCC_AWS_KEY_PAIR_FILE=my_private_key.pem

    c4 config | grep CCC_PLAY_SSHD_PORT
    CCC_PLAY_SSHD_PORT=20002

    c4 ps 
          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:

    scp -P 2002 -i ~/.ssh/my_private_key.pem \
      root@203.0.113.10:/exa/tmp/support/exacluster_debuginfo_2022_08_11-23_27_20.tar.gz ~/my_logs/

Verification

To verify that the log was successfully copied, use the ls command in the target folder on your local machine.

Example

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