Skip to main content

Monitoring a Database Instance

Info

This document has been created based on the Oracle Monitoring V2. For the Oracle monitoring V1 document, see the following.

Home > Select Project > Dashboard > Monitoring a Database Instance

In Monitoring a Database Instance, you can monitor the key metrics of the database server, information details on active sessions, lock tree, PQ tree, and process information in real time. You can also see the alerts that could be problematic warnings. By default, the collected data for the last 10 minutes is retrieved in real time. Collected data is updated every 5 seconds.

Basic screen guide

Instance Monitoring

Selecting the lookup time and target

By default, the collected data for the last 10 minutes is retrieved in real time. If you select values in Time and Instance, the collected data is automatically applied to the number2 graph chart and number4 Active sessions table.

  • To view the past data, click the green button in Time and then select the desired lookup time. You can search data up to the last 3 weeks.

  • To query a random date and time, select the Pause icon button in Time. If you click the text range for date and time, the option appears to select the date and time. To search data in real time again, select Real-time icon.

  • To search data from other agents, click Instance and then select a desired agent name.

Graph chart section

number3 Default displays 16 metrics saved as presets as a graph chart widget. The horizontal axis of each widget is time, and the vertical axis is the metric number. To know the meaning of each metric, select Information next to the name or see the following.

  • To change the position with another widget, select and drag the upper part of the widget. However, the size of the widget cannot be changed.

    Moving a widget

  • When a specific time is selected in the widget, the real-time inquiry mode is stopped and the active sessions performed at the selected time zone appear in the number 4 Active sessions table. After that, a button that allows you to view the data every 5 seconds appears on the Active sessions table.

    Note
    • The selected time can be seen on the upper right of the Active sessions table.

    • In the Active sessions table list, the text colors are changed black → orangeRed, which means that the performance of the session is getting slower.

Active Sessions / Lock Tree / Process Info

You can search active sessions, lock trees, and processes information in real time. If you select a specific time of the chart in the widget, the real-time inquiry mode is stopped and the session performed at the selected time appears in the table. A time selection button appears above the table to search data in 5-second increments.

  • Active sessions: You can view active sessions and queries.

    • If you select a session running, the Session detail window appears. You can see the details for the selected session. For more information, see the following.

    • If you select an item in the rightmost query_text column in the table, the SQL details window appears. You can see the full text and plan information for the selected query. For more information, see the following.

  • Lock tree

    You can see the lock session information, and holder and waiter information in real time. For more information about the table columns, see the following.

  • Process Info

    You can query the resource usage of the database server in real time.

Tip

By adding a linked project, you can view information details about active transactions associated with active sessions in the Active sessions table in real-time. For more detailed information about adding and using a linked project, see [the following] (linked-projects).

Note
  • In the table list, the text colors are changed black → orangeRed, which means that the performance of the session is getting slower.

  • The Process Info can be checked only when the XOS agent has been installed. For more information, see the following.

Selecting metrics

To add or replace the metric graph to the widget, select Configuration icon on the upper right of the widget. The Metric Select window appears. After completing the desired settings, select Save.

Metric Selection

  • number 5 Preview: You can preview the graph for the selected metric.

  • number 6 Title: Enter the widget name.

  • number 8 Recommendation Metrics / All Metrics: If you select Recommendation Metrics, the list of frequently viewed metrics in Database Monitoring appears. The metrics displayed in the list can be changed or added in the widget.

  • In the number 9 area, you can see the trend of metrics in a graph and add or change any widget. By selecting a desired tab, you can narrow down the list of metrics according to the category.

Adding metrics

Multiple metrics can be added in a widget. You can add up to four metrics.

  1. Select Configuration icon on the upper right of the widget to add the metrics in.

  2. If the Metric Select window appears, in the number 8 metrics list or number 9 graph list, select Add icon on the right of the metric to add.

  3. To add more metrics, repeat the step 2.

  4. To easily identify the widget, change the number 6 Title.

  5. Select Save on the lower right of the screen.

Charts are generated as many times added to the widget to which metrics are added. If you select information icon next to the widget name, you can see the name and description of the added metric. You can also check the figure through a tooltip by hovering your mouse over the chart.

Note

The tooltip of the Information Icon button is not supported in multiple languages.

Changing a metric

You can change a metric in the widget to another.

  1. Select Configuration icon on the upper right of the widget to change the metrics.

  2. If the Metric Select window appears, select a metric to change in the number 7 area.

  3. In the number 8 metrics list or number 9 graph list, select a desired metric.

  4. In the number 7 area, check that the name of the selected metric has been changed.

  5. Select Save on the lower right of the screen.

Deleting a metric

You can delete unnecessary metrics while multiple metrics have been set in the widget.

  1. On the upper right of the widget to delete metrics from, select Configuration icon.

  2. If the Metric Select window appears, select Delete icon on the right of the metric to delete from the number 7 area.

  3. Select Save on the lower right of the screen.

Note

At least one metric must be selected for a widget. You cannot delete all metrics in a widget.

Preset

You can save and recall user-defined widget settings and active session table arrangements as presets. The following presets are provided by default, and the Default presets cannot be changed.

Preset

  • Default: It consists of major DB metrics.

  • Default(xos): It consists of key DB metrics and XOS metrics (CPU and memory utilization, memory SWAP usage, disk I/O, etc.).

  • Default(rds): It consists of key DB metrics and RDS CloudWatch metrics (CPU utilization, free memory space, free storage space, network, etc.).

Save Preset

  1. Add or modify the widget metrics.

  2. On the upper right of the screen, select Save icon.

  3. In Save preset, change the name and then select Save.

In the Preset list, select a saved item to fetch the settings.

Note
  • The Default preset cannot be modified.

  • You can create custom presets up to 5. Including the modified metric graph, the column order, column width, and filter application content of the active sessions are also applied.

Deleting presets

If you select Preset on the upper right of the screen, the preset list appears. Select Delete icon on the right of the preset to delete.

Using the active session section

Through Active sessions at the bottom of the screen, you can see the real-time active sessions. The following provides the guide for the button on the upper right of the table.

  • Filter icon: Using the column header entries in the table, the list can be filtered.
  • Refresh icon: The list of tables is refreshed.

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

  • Session Kill icon: The active session can be stopped.

    Note

    This feature is only available to the members with Edit role. For more information about member roles, see the following.

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

  • Popup icon: A new window appears to see the list on a wider screen.

Checking the SQL statistics

You can see the list of top SQLs for the time period along with the trend of key performance metrics that occurred during the specific time in the past.

SQL 통계 바로가기

  1. In Time, select 아이콘 to switch from real-time mode to non-real-time mode.

  2. In Time, set the time zone to view.

  3. On the upper right of the Active sessions area, select SQL statistics.

SQL statistics appears in a new window. In Instance monitoring, you can see the top SQL list executed for the set time. For more information about SQL statistics, see the following.

Checking the session information details

If you select a session in the Active sessions tab, the Session detail window appears. You can see the information details about the selected session.

Session detail

  • The session information is viewed in real time by default. If you select Pause icon in the time selector, you can stop a real-time view and see the data based on the paused time. To refresh data while pausing a real-time view, select Refresh icon.

  • Kill Session: You can stop the selected session. If the Session kill window appears, enter the password (Parameter Key) and then select Apply.

    Note

    This feature is only available in real-time viewing mode.

  • Session history: You can go to the Session History menu to see the records of the selected session.

    Note

    For more information about Session History, see the following.

  • Session Stat: It provides various performance metrics and statistical information for the selected session. It includes the type and number of tasks performed in the session, resource usage, and more.

  • Delta / Sigma: The change rate and statistical analysis information for the selected session appear. You can check the amount of change in session activities.

  • Session Info: You can see the basic information of the selected session and the information details including the status.

  • Wait Info: The waiting event and waiting time of the selected session are provided. You can also see information about the waiting events that occur when the database system is waiting to execute a specific task.

  • SQL Text / Plan: You can see the SQL query statements and plans of the selected session. For more information, see the following.

See query details

To check the SQL query information of the executing session, select the query (or sql_text) column in the Active sessions section. The SQL details window appears. You can check the SQL query statements and plan information.

SQL details

  • View SQL Statistics: You can go to the SQL statistics menu where you can check statistical information related to the SQL query statement.
  • 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.

Checking the linked projects

In Correlated Project Management, when another application project is added, the Correlations icon button is added to the active session entry.

Correlated project

Through the Correlation analysis window that appears when the Correlations icon button is selected, you can check active transactions of the applications linked to active sessions. You can check specific metrics such as transaction ID, thread ID, client IP, and CPU usage time, along with basic information such as transaction URL and database connection information, DB type, HTTP method, and execution time. Additionally, you can monitor the SQL query execution time, number of SQL calls, DB connection time, and such, which allows you to comprehensively analyze the system performance.

In particular, it provides the call stack information and SQL queries through stack traces, helping you trace and resolve detailed causes when problems occur. This allows you to perform in-depth analysis of interactions between applications and databases, and to quickly diagnose performance bottlenecks.

Note

For more detailed information about adding and using a linked project, see [the following] (linked-projects).

Stopping an active session

  1. Select Session Kill icon on the upper right of the table.

  2. Select the session to stop from the table list. You can select multiple items.

  3. Select Stop.

  4. If the Session kill window appears, enter the password (Parameter Key).

    Session Kill

  5. Select Apply.

The selected session is stopped.

Note
  • Through the paramkey.txt file in the DBX agent installation path, you can find the password.

  • This function can be used by only the members with the Edit role. For more information about the member roles, see the following.

Zooming in the graph chart section

Active session

If the current screen is small and difficult to check the widgets, you can see the graph chart widget on a wider screen. Select Down arrow icon at the bottom of the Active sessions section. The Active sessions section is collapsed and the graph chart widget section is expanded.

To zoom out the graph chart widget, select Up arrow icon at the bottom of the Active sessions section.

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.

Column Settings

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.

Filtering the table data

Filter

  1. Select Filter icon on the upper right of the table.

  2. Select a column header and a condition in the table.

  3. Enter a desired value in the Enter conditions field.

  4. Select Save.

Column information guide

For more information about columns, see the link.

ItemDescription
sidSession ID
cpu(xos)CPU utilization collected by the installed XOS
serial#Value to increment to determine if the same session ID has been used.
usernameDB user name.
commandSame as COMMAND_TYPE; SQL command number
statusSession status
schemanameSchema. Same as the username.
osuserUsername of the OS that accessed the session.
spidOS process ID.
processID of the client process that accessed the session.
logon_timeSession created time point.
last_call_etIf the session is active, it is the elapsed time (sec) since activation.
sql_textquery, running statement, SQL statement that separates literal strings
sql_paramLiteral value separated from query
prev_sql_textPreviously executed query
prev_sql_paramPreviously executed query param
programProgram information executed by client
typesession type - can be adjusted in user background recursive (whatap.conf).
seq#Number that uniquely identifies the current or last wait (incremented with each wait)
eventNumber of the resource or event if the session is waiting.
p1First waiting event parameter (decimal point)
p2Second waiting event parameter (decimal point)
p3Third waiting event parameter (decimal point)
wait_classClass name of the waiting event
wait_timeThe value is 0 if the session is waiting. It is the last waiting time (milliseconds) if the value is greater than 0.
seconds_in_waitTime spent waiting for the wait if the session is waiting. Otherwise, it is the time elapsed since the last waiting.
stateWaiting state: WAITING, WAITED UNKNOWN TIME, WAITED SHORT TIME, WAITED KNOWN TIME
machineName of the client server that accessed the session (hostname)
portClinet port number
terminalClient terminal name
moduleName of the module set by the user of the program executed on the client.
actionAction name set by the user of the running module.
client_infoClient information set by user
client_identifierClient ID set by user
session logical readsNumber of times data was read into the buffer cache
physical readsNumber of data reads from the physical disk
execute countSQL execution count
parse count (hard)Total number of syntax analysis calls (actual syntax analysis)
parse count (total)Total number of syntax analysis calls (hard, soft, describe)
opened cursors currentNumber of open cursors
db block changesChange count of all blocks in the database
session pga memorySession's current PGA size
undo_segidUndo information ID
undo_blkUndo block count
undo_recUndo record count
sql_addressSQL statement identification data
sql_hash_valueSQL statement identification data
sql_idSQL ID of the running SQL statement
sql_child_numberSub number of the running SQL statement
sql_exec_startStart time point of SQL running in the session
sql_exec_idSQL running ID
prev_sql_addrInformation that identifies the last run SQL statement
prev_child_numberSub number of the last SQL statement executed
prev_exec_startStart time point of the last SQL statement executed
prev_exec_idStart ID of the last SQL statement executed
plsql_entry_object_idObject ID of the top PL/SQL subprogram on the stack.
plsql_entry_subprogram_idID of the top PL/SQL subprogram on the stack.
plsql_object_idSubprogram ID of the running PL/SQL object
taddrTransaction address
lockwaitlock wait address (lock address where the session is waiting)
row_wait_objObject ID of the table containing the row specified in ROW_WAIT_ROW#
row_wait_fileID of the data file containing the row specified in ROW_WAIT_ROW#
row_wait_blockID of the block containing the row specified in ROW_WAIT_ROW#
row_wait_rowCurrently locked row
pdml_statusIf the value is ENABLED, the session is in PARALLEL DML activation mode. If the value is DISABLED, the session does not support the PARALLEL DML activation mode. If the value is DISABLED, the session does not support the PARALLEL DML activation mode.
pq_statusIf the value is ENABLED, the session is in PARALLEL QUERY activation mode. If the value is DISABLE, the session does not support the PARALLEL QUERY activation mode. If the value is FORCED, it indicates the session was changed to force the use of PARALLEL QUERY.
blocking_session_statusIt provides details about whether there is a blocking session.
blocking_instanceInstance ID for the blocking session
blocking_sessionSession ID for the blocking session
final_blocking_session_statusIt provides details about whether there is a last block session.
final_blocking_instanceInstance ID for the last blocking session
final_blocking_sessionSession ID for the last blocking session
service_nameService name of the session. It is similar to the DB name.
saddrSession address
con_idID of the container associated with the data (only for multi-database support)
rss(xos)OS metrics collected by the XOS agent
pss(xos)OS metrics collected by the XOS agent
ioread(xos)OS metrics collected by the XOS agent
iowrite(xos)OS metrics collected by the XOS agent
Note

WhaTap basically stores the client-related information.