Skip to main content

Count trend and comparison

Counts Trend

Home > Select Project > Analysis > Counts Trend

You can check the operation trend of the key metrics of the database over time and trace the performance. You can check the current active session data and distinguish the long-running sessions.

카운트 추이

Home > Select Project > Analysis > Counts Trend Comparison

Counts Trend

You can compare the count trends for different dates.

  1. Select the desired instances from the Instance area. You can also select different instances.

  2. Set values for Reference Date and Comparison Date.

  3. Select Search icon.

Using the chart and active session area

Select Layout icon on the screen. In the Layout setting window, set it to 1 x 3 and then select Save. Time must be set to Last 24 hours. You can see the database key metrics in detail for the day, as follows:

Counts Trend

  • In number1 Time, set a desired time interval.

    • Click the green icon to select a search time.
    • With the lookup period selected, select Left arrow icon or Right arrow icon. Then you can change the lookup time at the set time intervals.
    • If you select the date and time, you can set the desired time in detail. After configuration, select Confirm.
  • number2 Instance: You can select an instance that is connected with the project.

  • If you click a specific time point of the metrics chart, the (number3) area appears with red lines and the collected active sessions can be also displayed.

  • To change the metrics in the chart, select Configuration icon on the upper right.

  • The active session data is collected every 5 seconds. You can search the data by selecting the number4 5-second cells at the bottom of the screen.

  • To move the time by 1 minute, select number5 Previous time icon or Next time icon.

  • number5 Column icon: The column header entries in the table can be displayed or hidden.

  • number5 Filter icon: You can filter the list based on the column header entries in the table. After selecting the button, you can set the conditions in each header column such as Includes, Excludes, Equal, and Unequal.

  • number5 Download icon: You can download the content of the table as a CSV file.

Column information guide

For more information about columns, see the link.

ItemDescription
actionName of the running job.
block_updatesNumber of block updates.
block_updates_sigmaTotal number of block updates.
client_identifierClient ID.
client_infoAdditional information of the client.
client_pidPID of the client process.
commandCommand running in the current session.
consumed_cpu_timeCPU time consumed by the session.
consumer_groupConsumer group to which the session belongs.
cpu(xos)CPU utilization
cpuusageCPU usage consumed by the session.
event_nameName of the waiting event.
execute_countNumber of SQL executions.
execute_count_sigmaTotal number of executions.
id1First identifier value.
id2Second identifier value.
ioread(xos)Actual time spent reading the block (milliseconds).
iowrite(xos)Actual time spent writing the block (milliseconds)
ipaddrClient IP address.
logon_timeTime when the session logged in the database.
logical_readsNumber of logical read operations.
logical_reads_sigmaTotal number of logical read operations.
machineName of the machine on which the session is running.
moduleName of the running module.
os_thr_idThread ID of the operating system.
osuserUser of the operating system running the session.
parse_count_hardNumber of hard parses.
parse_count_hard_sigmaTotal number of hard parses.
parse_count_totalTotal number of parses.
parse_count_total_sigmaTotal number of parses.
pdml_enabledWhether parallel DML is enabled or not.
pdml_statusStatus of the parallel DML.
pddl_statusStatus of the parallel DDL.
pga_used_memAmount of memory being used in the process global area (PGA).
physical_readsNumber of physical read operations.
physical_reads_sigmaTotal number of physical read operations.
pidPID of the database process.
pq_statusStatus of the parallel query.
prev_sqlText of the previously executed SQL statement.
prev_sql_idUnique ID of the previously executed SQL statement.
prev_sql_paramParameter of the previously executed SQL.
prog_nameName of the program running the session.
pss(xos)Process specific memory usage + Percentage of shared memory occupied by one process.
row_wait_block_noBlock number of the waiting row.
row_wait_file_noFile number of the waiting row.
row_wait_obj_idObject ID of the waiting row.
row_wait_row_noRow number of the waiting row.
rss(xos)Resident Set Size (RSS) that is the number of physical pages associated with the process.
schemanameName of the schema the session is using.
seq#Value indicating the sequence number of the session.
sidSession ID that uniquely identifies the session.
sql_etSQL execution time.
sql_hashHash value of the SQL statement.
sql_idUnique ID of the SQL statement being executed.
sql_paramParameters used to execute SQL.
sql_textText of the SQL statement being executed.
sql_traceWhether to trace SQL.
stateCurrent state of the session.
statusStatus of the session.
terminalName of the terminal to which the session is connected.
typeType of the session.
usnUndo segment number.
used_blkNumber of used blocks.
used_recNumber of used records.
wait_eventEvent that the session is waiting for.
wait_timeWaiting time.
wlock_waitWhether the session is waiting for a lock or not.
wthr_idThread ID of the session's work.
Note

WhaTap basically stores the client-related information.