Profiling Information

This article explains how to retrieve profiling information from your Exasol system.

In some scenarios you may be asked by Support to provide profiling information for a problematic query. To get this information you must first run a test of the problematic statement with profiling enabled, and then retrieve the log files for that session.

Prerequisites

You must have enough free disk space for the logs. For more information, see EXAsupport.

Procedure

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

  1. Open a new database connection using your preferred SQL client.
  2. Copy the problematic SQL query into the following statement and execute it:
    Copy
    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';

    commit;

    flush statistics;

    commit;

    export (
        select *
        from EXA_STATISTICS.EXA_USER_PROFILE_LAST_DAY
        where session_id = current_session
    )
    into LOCAL CSV
    FILE 'profile_output.csv';
  3. Attach the generated CSV file profile_output.csv 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 that you have enough free disk space for the logs. For more information, see EXAsupport.

This procedure uses the c4 and confd_client command-line tools in a Linux terminal. For more information about these tools, see Exasol Deployment Tool (c4) and ConfD.

  1. Connect to the cluster operating system (COS) using c4 connect -i PLAY_ID -s cos.

    Example:
    Copy 
    ./c4 connect -i c3275f84 -s cos

    For more information about how to use c4 connect, see How to use c4.

  2. To find the database name when you are connected to COS, use the ConfD job db_list.

    Example:
    Copy 
    confd_client db_list
    - MY_DATABASE

  3. To collect information about a specific SQL session, use the EXAsupport tool and provide the relevant session ID. Specify the start date (-s) and end date (-t) using the format YYYY-MM-DD.

    In Exasol versions prior to 8.25.0, you can only collect SQL logs for a specific session on the day that the session occurred. Later versions do not have this limitation.

    For example:

    Copy 
    exasupport -s 2022-08-11 -t 2022-08-11 -e MY_DATABASE -i SESSION_ID

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

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

  4. Use Control+D or type exit to disconnect from COS.

  5. Copy the log file to your local computer by connecting to COS and using the cat command:

    Copy 
    ./c4 connect -t <DEPLOYMENT>.<NODE>/cos -- "cat /exa/tmp/support/$FILENAME" > $FILENAME
    Example:
    Copy 
    ./c4 connect -t 1.11/cos -- "cat /exa/tmp/support/my_log" > my_log

    Verification

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

    Example:
    Copy 
    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