Session History

Home > Select Project > Analysis > Session History

In Session History, you can see what has been performed in a specific session during the query period. It provides information that allows you to check how much resource has been used for SQL for a long-running session and analyze the causes.

Basic usage guide

You must enter the session number (Process ID) to monitor as a required value, but it is more efficient to enter through the Monitoring a Database Instance menu.

1. Go to Dashboard > Monitoring a Database Instance.

2. In the Active Session tab, click a session from the ID column.

3. In Session detail, click Session history to move to Session History.

4. You can view the session history collected for the selected session's process ID (PID).

   

   Active session data collected every 5 seconds from the selected session is used to construct a chart and its list and provide information that can be used for analysis.

   • Wait: You can see the percentage of waiting events through a chart.

   • Cpu: You can see the change trend in CPU usage through the chart.

   • Memory: You can see the change trend in memory usage through the chart.

   • Disk I/O: You can see the change trend in disk usage through the chart.

   If you select the query column on the utmost right of the list, the SQL details window appears where you can see the SQL statement. It contains full texts and plan information for the selected query.

View SQL Details

Click the View SQL Statistics → button to move to SQL statistics,
where you can view statistical information related to the selected SQL query.

• Runtime Plan: It provides the execution plan and runtime information for a selected SQL query. It provides the information details such as execution count, average execution time, and average physical reads.

• Explain Plan: It displays the execution plan predicted by the optimizer. It provides information such as cost, job, object name, and cardinality.

• Plan History: You can check the history of the execution plans of the SQL queries executed in the database.

• Bind Capture: You can check the bind variables used in SQL queries executed in the database. This allows you to see actual content of query executions.

  Note

  This is a value captured in the database (v$sql_bind_capture), not a bind value executed in real time.

• Trend: You can check the trend of execution metrics for the selected SQL in a time-series chart and a table. It shows changes in execution time, average metrics per execution, and parse counts (total and hard) in chronological order.

  Note

  The set of metrics shown on the Trend tab differs between Oracle and Oracle Pro.

Checking Bind Capture values

The bind values on the Bind Capture tab are masked by default. They can contain actual customer data such as resident registration numbers or account numbers, so query permission alone is no longer enough to see them.

The list itself is queried without the parameter key, because the collection time, variable name, and data type are not sensitive information. Only the value column is masked with ******.

Column	Description
time	Collection time
last_captured	The time the database last captured the bind value
name	Bind variable name
value	Bind value. Shown as ****** before decryption
datatype	Bind variable data type
child_number	Child cursor number

To check the values, follow these steps.

1. Click the lock button at the top right of the Bind Capture tab.

2. When the Check decryption key window appears, enter the parameter key. You can find the parameter key in the paramkey.txt file in the agent installation path.

3. Click the Confirm button.

If the key is correct, the window closes and the value column is filled with the actual values. Some rows may still show a dash (-) after decryption; this means the agent could not capture the value of that variable. The notation differs so that it can be distinguished from the masked state (******).

Note

If the lock button is not visible

The lock button does not appear for accounts without the sensitive information query (SECURITY_READ) permission. Contact your project administrator about permissions.

Caution

If you enter the wrong key

The message "Invalid parameter key." appears below the input field along with guidance to check paramkey.txt, and the window does not close. The reason for failure is not shown in more detail so that the key value carried in the request is not exposed on screen.

If the parameter key was changed during the query period, only some rows are filled, along with the message "The parameter key was changed during the query period, so some values were not decrypted."

A decryption query returns up to 500 rows at a time. If the limit is reached, more values may have been truncated.

AI Tuning Guide

The AI Tuning Guide analyzes SQL queries, plans, and statistical information to diagnose performance issues and suggest optimization strategies.
It helps developers and DBAs quickly identify bottlenecks and improve performance through efficient SQL optimization.

Caution

Usage Conditions and Notes

For PostgreSQL, MySQL, and SQL Server, query plan retrieval is required.
If the plan is not retrieved, the AI Tuning Guide icon appears as (disabled), and the feature cannot be used.

• Please note that AI-generated results are based on automated analysis and may not be 100% accurate.

1. Click the SQL you want to analyze and diagnose to move to the SQL details screen.

2. On the SQL details screen, click the AI Tuning Guide icon at the bottom right to start the AI analysis.

3. Review the AI analysis results.

   Result Item	Description
   Query Plan and Summary	Provides the purpose and execution summary of the query. Analyzes execution count, cumulative execution time, and overall database load ratio to assess the query’s impact on system performance.
   Performance Analysis	Provides performance scores and diagnostic results based on overall analysis. Analyzes detailed resource usage such as CPU, disk, cache hit rate, and wait time to visually identify bottleneck areas during query execution.
   Key Issues Found	Summarizes detected major issues.
   Optimization Recommendations	Suggests optimized queries based on identified issues.

Viewing the default plan

When creating the default plan user file, you can configure the agent to automatically view the plan by using the predefined DB information. After checking the box for Default plan inquiry, search for the plan through the specified DB connection information as follows.

Linux

1. Add the plan_db option to the agent configuration (whatap.conf) file and then enter the DB name.

   whatap.conf

   plan_db=(dbname)

2. After configuring the DB, use the planuid.sh script to set the user and password.

   ./planuid.sh user pwd

   Note

   If the user (user) and password (pwd) include special characters, add backslashes (\) before each special character.

   e.g. user$example → user\$example

Windows

1. Add the plan_db option to the agent configuration (whatap.conf) file and then enter the DB name.

   whatap.conf

   plan_db=(dbname)

2. After configuring the DB, use the planuid.bat script to set the user and password.

   planuid.bat user pwd

Setting the table columns

You can hide the table header columns or add any of them. You can also change the column order. Select .

Note

• After configuration, select Confirm to apply the settings in the table.

• In the search bar, enter text to search the desired columns. Only the columns that meet the entered text are displayed.

• Images may differ depending on the product, project, or menu.

Adding columns

From the list, select the items to add as table header columns. To select all items, select Select All.

Deleting columns

From the list, unselect the columns to delete. Alternatively, select on the right of the item to delete from the list.

Changing the column order

Drag an item to reposition from the list, and then move it to the desired position.

Initializing the configuration

To cancel all changes and reset them, select Initialized.