Skip to main content

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 Right arrow icon to move to Session History.

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

    Session History

    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.

SQL details

  • 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 see the values ​​of 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. If the number of cases is too large, it displays up to 100.

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 AI Tuning Guide Icon (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 AI Tuning Guide Icon at the bottom right to start the AI analysis.

  3. Review the AI analysis results.

    Result ItemDescription
    Query Plan and SummaryProvides 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 AnalysisProvides 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 FoundSummarizes detected major issues.
    Optimization RecommendationsSuggests 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.

  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

Setting the table columns​

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

Note

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

  • In the number 3 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 Number 1 list, select the items to add as table header columns. To select all items, select Select All.

Deleting columns​

From the number 1 list, unselect the columns to delete. Alternatively, select Delete icon on the right of the item to delete from the number 2 list.

Changing the column order​

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

Initializing the configuration​

To cancel all changes and reset them, select Reset icon Initialized.

Last updated on