Profiling Information

For some issues, you might be required to provide profiling information for a problematic query. To get this information, you need to do the following:

  1. Run a test of the problematic statement with profiling switched on.
  2. Get the log files for this test session.

You must perform both step 1 and step 2 on the same day, after 04:00 (4:00 AM).

Step 1: Run a test of the problematic statement with profiling switched on

To run a test of the problematic statement with profiling switched on:

  1. Open a new database connection using your preferred SQL client.
  2. Copy the problematic SQL query into the following statement and execute it:
    set autocommit on;
      alter session set profile='on';
      <insert your query here>;
      alter session set profile='off';
      alter session set NLS_NUMERIC_CHARACTERS='.,';
      alter session set NLS_TIMESTAMP_FORMAT='YYYY-MM-DD HH:MI:SS.ff3';
      flush statistics;
      export (
        select *
        where session_id = current_session
      into LOCAL CSV
      FILE 'profile_output.csv';
  3. Attach the generated CSV file to your support ticket.

Step 2: Get the log files for the test session

In this step, you will request the logs for a specific session.

Make sure you have enough free disk space for the log. For more information, see EXAsupport.

  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 a specific SQL session, use the EXAsupport command-line tool (exasupport) and provide the relevant session ID. Specify the start date (-s) and end date (-t) using the format YYYY-MM-DD.

    You can only collect SQL logs for a specific session on the day that the session occurred.


    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

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


    Get the necessary info:

    c4 config | grep CCC_AWS_KEY_PAIR_FILE

    c4 config | grep CCC_PLAY_SSHD_PORT

    c4 ps 
      ┌─  1  3a4a7d8d  10    awscf   c5d.large    c      running    04:35:15  +∞
      │   1  3a4a7d8d  11    awscf   c5d.2xlarge    d      running    04:35:16  +∞
      └─  1  3a4a7d8d  12    awscf   c5d.2xlarge    d      running    04:35:15  +∞

    Copy the file to your local machine:

    scp -P 2002 -i ~/.ssh/my_private_key.pem \
      root@ ~/my_logs/


    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