Profiling Information
For some issues 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.
Step 1: Run a test of the problematic statement with profiling enabled
- Open a new database connection using your preferred SQL client.
- 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 *
from EXA_STATISTICS.EXA_USER_PROFILE_LAST_DAY
where session_id = current_session
)
into LOCAL CSV
FILE 'profile_output.csv'; - 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.
- Open EXAoperation and go to Services > Support.
- Set up the options on the Debug Information screen as follows:
- No Cluster Logs / Coredumps
- No Process Backtraces
- Select all nodes
- Select the impacted database
- Select Session and enter the identifier of the test session you ran in step 1 (use the SELECT CURRENT_SESSION statement to get this)
- Set the start and stop dates for the day the issue occurred
-
Click Download Debug Information to download the file locally, or Store Debug Information into Archive Volume to save the file to a remote server.
- Attach the log files to your support ticket.