EXA_USER_PROFILE_RUNNING

This system table contains all profiling information of the running queries of current user. For more information on profiling, see Profiling. All users have access to the table.

Column Name Description
SESSION_ID ID of the session
STMT_ID Serially numbered ID of statement within a session
COMMAND_NAME Name of the statement (for example, SELECT, COMMIT, or MERGE.)
COMMAND_CLASS Class of statement (for example, DQL, TRANSACTION, or DML)
PART_ID Serially numbered ID of the execution part within the statement
PART_NAME Name of the execution part (see also Profiling)
PART_INFO Extended information of the execution part. For example:
  • GLOBAL: Global action (for example, global join)
  • EXPRESSION INDEX: Non-persistent join index which is built on an expression
  • NL JOIN: Nested loop join (cross product)
  • REPLICATED: Replicated object (for example, small tables)
  • TEMPORARY: Temporary object (for intermediate results)
PART_FINISHED Defines whether the execution part has already finished
OBJECT_SCHEMA Schema of the processed object
OBJECT_NAME Name of the processed object
OBJECT_ROWS Number of rows of the processed object
OUT_ROWS Number of result rows of the execution part
DURATION Duration of the execution part in seconds
CPU CPU utilization in percentage of the execution part (averaged over the duration)
TEMP_DB_RAM_PEAK Usage of temporary DB memory of the execution part in MiB (cluster wide, maximum over the duration)
PERSISTENT_DB_RAM_PEAK Usage of modified, persistent DB memory of the execution part in MiB (cluster wide, maximum over the duration)
HDD_READ Hard disk maximum read ratio in MiB per second (per node, averaged over the duration)

If this value is larger than 0, then data had to be loaded into the main memory.

HDD_WRITE Hard disk maximum write ratio in MiB per second (per node, averaged over the duration)

This column reflects only the data written during a COMMIT. For other statements its value is NULL.

NET Network traffic ratio in MiB per second (sum of send/receive, per node, averaged over the duration)
REMARKS

Any additional information such as, index type and columns, or index used for a join.

Some examples for the REMARKS column:

  • Join descriptions
  • Column which is read for a filter
SQL_TEXT Corresponding SQL text