1. User/ TIP Settings - This section explains how to configure the users and TIP settings for the monitoring database.

2. TPM Agent installation - This section explains how to install the TPM Agent.

1. - This section explains the system requirements that must be verified before installation.

2. - This section explains the environment configuration required before installing SysMaster DB 8.3.

3. - This section explains the components of the distribution files required for installation.

This section explains how to install SysMasterDB 8.3 in and . The installation process is divided into the following steps for each environment.

1. Installation and Parameter Configuration - This section explains how to install SysMasterDB 8.3 and configure its parameters.

2. Startup / Log Check / Shutdown / Initialization - This section explains how to start, check logs, shut down, and initialize the system.

1. - Explains how to log in and select a group.

2. - Explains groups and permissions.

3. - Explains how to create users.

To access SysMasterDB 8, the users must first log in via a web browser.

On the login screen, enter the usersr user ID and password, then click the [SIGN IN] button. Upon successful login, the users will be redirected to the group selection screen.

When installing SysMaster DB 8, an account with administrator privileges is created by default. The default administrator account ID and password are both "admin."

If login fails, a "Login Failed" dialog box will appear, prompting the users to verify the usersr ID and password. If login fails five times in a row, a message will appear instructing the users to try again after 10 minutes.

On the group selection screen, users select the group they want to join. If the user is not affiliated with any group, they can log in as Undefined (No Group).

After selecting the desired group, click the "Sign In to Group" button to proceed to the dashboard screen.

The Admin account has the following permissions by default.

• Manage members of the assigned group (create, edit, delete users) via the Settings > User menu

• All Configurable Privileges for all instances managed by the assigned group

There can be 0 or more Admins in a group.

Common User is the basic permission available from SysmasterDB.

Users are assigned permissions (Configurable Privileges) by Super Admin or Admin.

If no group is currently assigned, login is possible as "Undefined," but after login, access to all pages except "My Account" is restricted.

The users can perform the following actions using the Profile feature.

• My Account Settings

• Change Theme (Light/Dark)

The users can download the manual in PDF format by clicking the button on the right side of the GNB.

In the All Session Flow screen, the users can view the total number of sessions for each DB user in a graph, excluding users from the same DB. At this time, the users can select the chart interval (Interval) and aggregation method (Aggregation) from the dropdown menu to view the data.

This section describes High Availability Monitoring, which enables real-time monitoring of TSC configuration, network status, and recovery status.

This section describes Main Monitoring, which allows the users to monitor DB session status, CPU and memory usage of DB machines, and various metrics of DB instances through charts.

This section describes Usage Monitoring, which allows the users to monitor the real-time usage status of Tablespace, File, Temp space, and Undo space.

1. SysMasterDB 8.3 File Configuration

The deployment files for SysMasterDB 8.3 are structured as follows depending on the installation environment.

Docker-compose environment

Kubernetes environment

2. TPM Agent File Configuration

The TPM Agent deployment files are structured as follows.

3. Java TPM Agent File Structure

The Java TPM Agent distribution files are structured as follows.

1. Start

1.1. Set SysMaster DB environment variables

export SYSMASTERDB_HOME={SysMasterDB_Home_Path}

1.2. Add SYSMASTERDB_HOME to PATH

export PATH=$PATH:$SYSMASTERDB_HOME

1.3. Execute

sysmaster-db up

After booting is complete, the users can log in and use the program. Boot completion can be confirmed via the SDM log with the following log:

The users can specify the path where logs will be stored by configuring the log-related parameters in the .env file. The default log path is ./logs, so a logs folder is automatically created in the directory where the docker-compose.yml file is located, and the users can view the log files there.

With the environment variables and PATH set for SysMaster DB 8.3 startup, executing the following command will remove all services and shut down SysMaster DB 8.3. Note that even after shutting down SysMaster DB 8.3, the files created in METADB_PATH and REPODB_PATH will be retained, so the users can use SysMaster DB 8.3 as before after restarting it.

After deleting the METADB_PATH and REPODB_PATH directories, restarting SysMaster DB 8 will restore it to its initial installation state. However, any previously saved data will not be available.

The following ports used by SysMaster DB 8 must be allowed for external access.

List of ports that must be allowed on the SysMaster DB server

List of ports that must be allowed on the control database server

All users can belong to one or more groups. When a user belongs to a group, they are assigned the roles of that group.

ex) admin, user

A user can have one role per group, and if they belong to multiple groups, they can have different roles for each group.

Groups are assigned instances. Group members can be assigned permissions (Configurable Privileges) for the instances assigned to their group.

Configurable Privileges

Configurable privileges refer to individual user permissions.

They exist by function and instance and can be directly modified by admins or super admins.

The default value is "no permissions."

Privileges explicitly specified for an instance can only be used in that instance, while privileges not explicitly specified for an instance can be used on all pages regardless of the instance.

When changes are made, the "Save" button becomes active, and the users must click "Save" to save the changes. Clicking "Cancel" will revert to the previous settings.

The following is a description of each privilege.

After logging in, click the import button on the Dashboard, which is the first screen, to register an instance.

The newly registered instance will not be reflected on the screen immediately. After assigning the instance to a group, monitoring is possible from the Dashboard.

Click the icon in the upper-right corner of GNB to access settings.

In the Settings menu, click the All Groups menu in the top-left corner, then click the Create button at the bottom to create a new group. This will allow the users to create a group.

The "All Groups" menu is only available to super admins.

The required items when creating a group are as follows.

The users can view the status of the currently monitored instances and key monitoring data in a card view format.

The Card View refreshes every 3 seconds by default and displays cards sorted according to the Card Order By setting. (Refer to Card Sorting Criteria)

The users can switch between Compact / Detailed and Extended layout through the card layout button in the upper-left corner.

Common Features of Card View

• Sort the Card View by CPU Usage, Memory Usage, Lock Session Waiter Count, or Running Session Count.

• When Refresh is performed, Card View is sorted according to the specified criteria. If None is selected, the cards are sorted in the order of the Instance Overview.

• Click the pin button in the upper left corner to pin a card to the upper left corner.

• If multiple card views are pinned, they will be fixed in the order they were pinned.

• Displays the Updated Time of the Card View.

• Click Compact / Detailed / Expanded on the right side of Card layout to change the Card View layout.

• Card View selection feature

  • Click Card View to highlight a specific instance, similar to clicking an instance in Instance Overview.

  • When an instance is highlighted, the Custom Area at the bottom displays only the data of the highlighted instance instead of the metrics of all instances.

Connects to the Settings page.

Super Admin refers to the highest-level administrator who can perform all functions of SysmasterDB.

The Super Admin account has the following permissions by default.

• Register, modify, and delete instances in the Dashboard

• Create, modify, and delete groups via the Settings > All Groups menu

• Create, modify, and delete all users registered in SysMasterDB via the Settings > All Users menu

There can only be one Super Admin in SysmasterDB.

• Hover the mouse over the CPU/Memory pie chart to view detailed information.

• Lock Waiter: Displays the number of sessions waiting for a lock.

• Tablespace: Displays the number of tablespaces with usage exceeding 90%. When hovering over the mouse, displays the usage status of the top 10 tablespaces in descending order.

• Running Session: Displays the trend of Running Sessions over the past 5 minutes in an Area chart and shows the current number of Running Sessions in the upper-right corner.

If the monitored instance DB is in a down state, displays the time when it was last in a normal state.

When the Agent is disconnected, it is displayed as above and sorted at the end of the card view.

1. Main Monitoring - View real-time metrics such as DB session status, CPU and memory usage of DB machines, etc.

2. Usage Monitoring - Real-time status of tablespaces, files, UNDO, and TEMP spaces can be checked.

3. - The users can identify lock status between DB sessions and analyze issues.

4. - Monitor TSC configuration, network status, and recovery status in real time.

• Hover the mouse over the CPU/Memory pie chart to view detailed information.

• Lock Waiter: Displays the number of sessions waiting for a lock.

• Tablespace: Displays the number of tablespaces with usage exceeding 90%. A scrollable table at the bottom shows the current usage status of tablespaces.

• Running Session: Displays the trend of Running Sessions over the past 5 minutes in an Area chart and shows the current number of Running Sessions in the upper-right corner.

If the monitored instance DB is in a down state, displays the time when it was last in a normal state.

When the Agent is disconnected, it is displayed as above and sorted at the end of the card view.

The users can monitor detailed information such as the current SQL being executed and wait events for a specific session. Click the SID of the session the users want to view in detail in the session list to open the Session Details page.

Session Basic Information

These are the items displayed in a single row on the Session Monitoring page. Like the Session Monitoring screen, it provides refresh, auto refresh, and kill session functions.

The users can copy an existing layout using the Copy function provided when the users click the More button for a specific layout in the Layout list.

Clicking [Copy] creates a copy of the selected Layout, and the users can save the copy with a custom name.

Click the [Add Layout] button in [New Tab] to view the existing Layout list and select the desired Layout to apply.

The following are examples of the Layout list modal and the screen after applying the selected modal.

The Period Selector in the All Session Flow page includes the Chart Interval feature. While the Period Selector in the common functions dynamically determines the Chart Interval based on the query period, the All Session Flow page allows users to specify the Chart Interval.

Chart Interval consists of sec, min, hour, and day, and can be selected if the selected Period includes the time that can be expressed by Chart Interval.

The Instance Monitoring page allows users to set various metrics in the desired layout for real-time monitoring.

The Instance Monitoring page consists of the Instance Overview area provided in the left side panel and the Layout Tab area that makes up the entire page.

Changed Plan Analysis

Provides a comparison analysis function for SQL plans that have been changed during the specified period.

All Session Flow

Provides session connection trends for each monitoring DB and the current status of session connections at each point in time.

Search SQL Text

Lists SQL statements that generated hard parses during the specified period.

The users can view the history of alerts generated based on user-defined alerts and system alert rules.

The users can view the Invalid Objects Count data and detailed information about invalid objects.

The users can delete an existing Layout using the Delete function provided when the users click the More button for a specific Layout in the Layout list..

Click the [Analysis] > [History Analysis] > [Changed Plan Analysis] menu in the global navigation bar to open the Changed Plan Analysis screen.

The Changed Plan Analysis screen provides charts for comparing and analyzing SQL plans that have been changed during the specified period.

Click the [Analysis] > [History Analysis] > [All Session Flow] menu in the global navigation bar to open the All Session Flow screen.

The All Session Flow screen displays the number of sessions by DB user who accessed the system during the specified period in a graph. The users can check how many sessions a user had at a specific point in time and view which sessions were active at the selected time.

Click [Analysis] > [Performance Analysis] > [Heatmap Trend] in the global navigation bar to open the Heatmap Trend screen.

The Heatmap Trend screen displays an overview of resource usage for the selected instance. During the specified time period, resource usage is visualized by time and date, allowing the users to quickly grasp the overall usage trends. Additionally, a bar graph showing minute-by-minute usage for the selected time period provides a detailed view of the overall usage flow.

The New Plan List screen allows the users to view the history of new plans.

The following is a description of the items provided on the New Plan List screen.

The users can view the minute-by-minute chart for the selected hour in the Daily Hourly Chart. This chart is located below the Daily Hourly Chart.

Clicking the Minute Chart bar allows the users to navigate to the desired menu.

The descriptions for each button are as follows.

The Plan History Comparison screen allows the users to compare plans for the same SQL with different TimeStamps and Child Numbers. The comparison of plans can be viewed in both Plan Tree and Plan Text formats.

Click the [Edit Layout] button to modify the existing Layout settings.

For detailed explanations of each item on the Edit Layout page, refer to Add Layout.

Click the [Add Layout] button in the [New Tab] to create a new layout.

Layout creation proceeds as follows.

1. Layout Name

Enter the layout name. This name will be displayed on the Instance Monitoring page.

1. Chart Index

Select the metrics the users want to monitor in real time. Refer to the appendix for a list of monitoring metrics available in Instance Monitoring.

1. Selected Item

Review the list of selected metrics and configure the chart options for each metric.

1. Summary

The users can view a layout example reflecting the list of metrics selected by the user.

1. Add

Click the Add button to create a layout defined by the user and apply it to the Layout Tab.

About the Guide

Issued date: 2025.08.14 Software version: SysMasterDB 8.3 Guide version: v1.0

This manual describes the process of installing SysMasterDB 8.3 on a system. It is intended for system administrators and DBAs who want to install SysMasterDB 8.3.

• Database

This chapter describes the Dashboard, which allows the users to monitor all monitoring database instances within the selected group.

It provides real-time status information and metrics for each monitored instance.

The users can set the Auto Refresh interval and pause by clicking the gear icon in the upper-right corner.

The Dashboard consists of the following main sections.

The Alert Event section displays a list of alerts that have not yet been confirmed. Alerts are divided into two categories: User-created, which are generated based on criteria set by the user, and System, which are automatically set and occur across all instances.

To remove an Alert Event, the users must either confirm each Alert individually or click the Confirm All button in the upper-right corner.

• Group: The name of the group to which the Alert is registered

• Hover the mouse over the CPU/Memory pie chart to view detailed information.

• Lock Waiter: Displays the number of sessions waiting for a lock.

Super Admin and Admin can create users in .

After checking the long-term trend using the Overall menu, the users can use the Time Slice feature to view all indicator information at a specific point in time.

The users can set the viewing period for each submenu of Analysis. Click the Time Slice button at the top of the screen to move to the Time Slice creation window.

1. Select the time period for the Time Slice.

The Instance Overview area of the Instance Monitoring page displays a summary of the current selected group's instance list and status information.

The Instance Overview area is provided as a side panel on the left side of the Instance Monitoring page.

This area displays the list of instances registered in the currently selected group, along with summary information about the status of each instance.

Users can select and monitor up to 5 instances simultaneously in a single layout.

The instance status information available through the Instance Overview area is as follows.

Click [Realtime] > [Usage Monitoring] > [Temp Usage] in the global navigation bar to open the Temp Usage page.

The Temp Usage page displays session temporary usage information. The users can monitor sessions that are using excessive temporary tablespace due to inefficient execution plans or poorly written SQL statements.

The following is a description of the items provided on the Session Temp Usage page.

Provides a chart broken down by time units for the selected day. The users can use the [OS], [STAT], [WAIT(TIME)], [WAIT(COUNT)], and [SESSIONS] buttons at the top of the Heatmap Trend screen to view an overview of each metric's usage.

Displays a time-based chart showing the usage of OS-related items (e.g., 'CPU Idle', 'CPU Sys', 'Memory Usage', etc.).

The users can change the resource to view by using the combo box on the right side of the metric selection button area.

Click [Realtime] > [Usage Monitoring] > [Undo Usage] in the global navigation bar to open the Undo Usage screen.

The Undo Usage page displays Undo usage information. The users can view information about sessions that have not yet committed or rolled back the current transaction.

The following is a description of the items provided on the Session Undo Usage page.

Click [Analysis] > [History Analysis] > [Alert Event Analysis] in the global navigation bar to open the Alert Analysis page.

The Alert Event Analysis page displays the history of alerts triggered by notification and system notification rules set by users of the SysMaster DB 8 product. The users can also check whether the alerts have been acknowledged.

The users can view user-defined notification occurrence information in a chart by setting a time range.

The users can set a time range to view user-defined notification occurrence information in a chart.

When the users hover the mouse pointer over the info icon to the right of the metric name in the upper-left corner of the chart, the users can view the description for that metric.

Clicking the More icon in the upper-right corner of the chart displays a list of additional features supported for each chart.

Additional features vary depending on the , and descriptions of chart-specific additional features can be found in the chart-type documentation.

Click [Realtime] > [Usage Monitoring] > [File Usage] in the global navigation bar to open the File Usage page.

The File Usage page displays information about data file usage. File Usage is collected every hour to minimize the load on the monitoring database. Clicking the [Collect] button in the upper-right corner collects and displays the latest File Usage information.

The users can view the data file I/O usage information for the tablespace of the monitored database.

This area shows the current status of alerts for monitored instances. It displays the number of alerts for each alert level (Error, Warning, Info). Click the button to go to the alert event history for the corresponding instance.

Both User-Created Alerts and System Alerts can be viewed. The users can check the time the alert occurred, the alert name, the alert level, the instance where the alert occurred, whether it was confirmed, and the user comments made when the alert was reviewed.

The users can change the instance and filter conditions to view Alerts from other instances or specific time periods.

The Total Session Info screen displays information about the session selected in All Session Count.

The following is a description of the items provided on the Total Session Info screen.

The Total Session Count screen displays the total number of sessions selected in the All Session Count screen.

The following is a description of the items provided on the Total Session Count screen.

Click the [Analysis] > [History Analysis] > [Search SQL Text] menu in the global navigation bar to open the Search SQL Text screen. The Search SQL Text screen displays a list of SQL statements for the specified period.

Double-clicking a specific column in the SQL list on the Search SQL Text screen opens the screen, where the users can view detailed information about the corresponding SQL.

The users can view the amount of change in the size of each tablespace name during the specified period.

The users can view changes in the size of filesystems mounted on the server by filesystem name during the specified period.

The SQL Text screen displays the entire syntax for the SQL statement selected in the New Plan List.

1. Install Docker or Podman

1.1. Engine Selection

Install Docker or Podman depending on the engine the users wish to use.

• If using Docker engine

  • The users can run SysMasterDB using Docker-compose or Kubernetes.

• If using on RHEL

  • The users can run the SysMasterDB using the Podman-compose environment.

Refer to the Docker Engine installation guide at the following address and install the appropriate Docker Engine for the usersr operating system.

The installation method varies depending on whether the installation environment has an internet connection.

• If the installation environment has an internet connection

  • Follow the "Install using the repository" process.

  • At this point, we recommend installing the latest version without specifying a specific version.

During the Docker Engine installation process, the packages that must be installed are docker-ce, docker-ce-cli, containerd.io, and docker-compose-plugin.

Use the docker version command to verify that Docker/Podman is installed correctly.

Follow the installation instructions provided at the following link.

The packages that must be installed during the Podman engine installation process are podman, Slirp4netns, and podman-plugins.

Use the podman version command to verify that Docker/Podman is installed correctly.

Select and install one of the following: 'Docker-compose', 'Kubernetes', or 'Podman-compose'.

• • When installing Docker, the docker-compose-plugin package is installed automatically. If Docker is installed correctly, no additional installation is required for the docker-compose environment.

  • Use the docker compose version command to verify that Docker Compose is installed correctly.

• Podman-compose

  • Podman-compose is a tool that allows the users to use podman in the same way as docker-compose.

  • It is built on Python and can be installed using pip. sudo pip3 install podman-compose

• Kubernetes

  • Follow the instructions at the following link to install Kubernetes, then install the version appropriate for the usersr operating system.

  • Additionally, check the Kubectl installation instructions at the following address and install Kubectl appropriate for the usersr operating system.

Provides detailed information about the monitoring DB instance and equipment.

1. Start

Execute the following commands in the directory where the installation file is located to create Kubernetes objects.

1.1. Create Namespace, ConfigMap, PVC, and Service

kubectl apply -f kubernetes/init

1.2. Create RepoDB and MetaDB deployments (proceed after database creation is complete)

kubectl apply -f kubernetes/db

Before proceeding to the next step, ensure that RepoDB and MetaDB have booted successfully. This can be verified through the following logs.

First, verify that the following messages are displayed in the terminal output logs of each pod.

[ENTRYPOINT LOG]: INFO: Attempting to start PostgreSQL server...

Next, verify that the following message is output in the log file of each database.

LOG: database system is ready to accept connections

The method for checking each database's log file is described in "".

After booting is complete, login and program use are possible. Boot completion can be confirmed via the SDM log with the following log:

By default, the users can access the log files of each module by connecting to the containers within the pods. The SysMaster DB modules log files are stored in the following paths within each container.

Additionally, for user convenience, the users can create and use a dedicated container for log verification.

The sysmasterdb8-log-container, a dedicated log viewing container, is defined within the sysmasterdb8-client-pod specified in the client-deployment.yaml file included in the deployment file configuration. Users can view logs from all SysMaster DB modules by accessing the log directory path (/sysmaster/logs) within this container.

To terminate SysMaster DB, execute the following commands in the directory where the installation files are located. Note that even after terminating SysMaster DB, the data files in the Repository DB and Meta DB are retained, so the users can use the previously saved data by restarting SysMaster DB.

Running the following commands will delete all data and restore the system to its initial installation state. However, previously saved data will not be available.

This chapter describes the Analysis menu, which enables period analysis of accumulated data through real-time indicator collection.

1. Performance Analysis - Analyzes metrics related to performance.

2. History Analysis - Analyzes trends in changes over time, such as plan changes, connection session counts, alert occurrence rates, and the number of invalid objects.

3. - The users can monitor trends in the usage of Tablespace, Filesystem, Segment, Temp Tablespace, and Undo Tablespace.

This section describes the common features used in the submenus of the Analysis service.

This is a dropdown menu that appears when entering the Analysis submenu. The users can select the instance to monitor from this dropdown menu.

Analysis Click the dropdown menu in the upper-left corner of the Analysis menu screen.

Click the Instance dropdown menu.

When the drop-down menu appears, select the desired instance, and the monitoring information for that instance will appear on the screen.

The submenu of Analysis provides a Period Selector. Users can set the period for data analysis using the Period Selector. Set the period in the Period area and click the [VIEW] button on the right to view the data for the target period. By default, the period is set to 1 hour, but if a specific period is required, the users can select Custom to view data for the desired period.

Search range and chart data unit default rules

By default, the chart data units are supported in minutes, hours, and days, and the unit changes based on the number of data points (120).

• Example 1: Search range of 120 minutes (2 hours) or less is displayed as minute-unit data.

• Example 2: Search range exceeding 120 minutes (2 hours) but less than 120 hours (5 days) is displayed as hour-based data.

• Example 3: Search range exceeding 120 hours (5 days) is displayed as day-based data.

• Example 1: Minimum search unit [minutes], chart data follows the default rule Performance Trend Alert Analysis

• Example 2: Minimum search unit [hours], chart data is provided in time units Invalid Object Tablespace Usage Filesystem Usage Temp Usage Undo Usage

• Case 3: Minimum search unit [day], chart data is provided in time units Heatmap Trend

Displays the past execution history and statistics of SQL statements identical to those currently being executed in the current session.

Select the time period for the SQL execution history

To view the history of SQL statements that are identical to those currently being executed in the current session, the users can select the desired period and view the history.

SQL Full Text

Displays the full text of the SQL currently being executed in the current session.

Plan Tree

This screen allows the users to view the plan for the SQL currently being executed in the current session. The SQL plan is displayed in a tree structure.

Displays statistical information about the past history of SQL statements identical to the currently executing SQL. Displays Summary, execute count, physical reads, logical reads, plan history, and SQL trace items.

The Summary tab displays stat indicators and a list of wait events for the analysis period, as well as the wait time values for each wait event.

The Execute Count tab displays the Execute Count by time unit in a chart format.

On the Physical Reads tab screen, the users can view the Physical Reads by time unit in chart form.

On the Logical Reads tab screen, the users can view Logical Reads in chart form by minute.

The Plan History tab screen allows the users to compare plans for the same query.

The SQL Trace tab displays the SQL execution history (trace information) for the specified query period.

Click [Analysis] > [Performance Analysis] > [Top N Performance] in the global navigation bar to open the Top N Performance screen.

In the Top N Performance screen, the users can view the top SQL statements during the search period.

When the users set the Category and Item, the users can view the Value for the selected Item. Additionally, selecting a value in the Category and double-clicking it allows the users to view information about the SQL, and selecting an SQL and double-clicking it links to the SQL Detail screen.

The following is a description of each area in the tab screen.

Category

Data aggregation criteria include 'Machine', 'Module', 'Program', 'Username', and 'OS user'. When 'SQL' is selected, no aggregation criteria are set.

Aggregation items include 'Logical Reads', 'Physical Reads', 'Redo Entries', 'Execute Count', etc.

By selecting Category and Item, the users can view performance metrics for the monitoring period. At this time, the users can specify the number of items in the sort list (ALL / Top 20 / Top 30 / Top 50) for categories other than SQL Category using the combo box in the upper-right corner of the area.

The following is a description of the items provided in the Category / Module area.

Displays SQL statements from the Category / Module with the highest Item (Logical Reads) values in descending order. Double-clicking on a SQL statement takes the users to the SQL Detail screen.

The following is a description of the items provided in the MODULE / SQL area.

Click [Analysis] > [History Analysis] > [Invalid Object] in the global navigation bar to open the Invalid Object page.

The Invalid Object page displays the Invalid Objects Count data and detailed information about invalid objects.

Invalid Objects Count

The users can view the Invalid Objects Count information for the specified period.

Invalid Objects

When the users click on a specific data point in the Invalid Objects Count chart, it provides the complete Invalid Object information included in that data count. This allows users to view detailed information about Invalid Object data for each time period.

The following is a description of the items provided on the Invalid Objects screen.

Click the [Analysis] > [Usage Analysis] > [Tablespace Usage] menu in the global navigation bar to open the Tablespace Usage screen.

Tablespace Usage

This screen displays the changes in the size of each tablespace name over the specified period.

The following is a description of the items provided in the Tablespace Usage screen.

When the users click on a specific data in Tablespace Usage, the users can view detailed changes in the size of the corresponding tablespace over time. The graph on the right allows the users to quickly grasp the size changes at a glance.

The following is a description of the items provided in the Tablespace Info screen.

When registering the monitoring database in SysMaster DB, the users will be prompted to enter user information. The users can use an existing user or create a new one. The required permissions for the user are CONNECT, ALTER SYSTEM, and SELECT_CATALOG_ROLE. User creation and permission assignment are performed using the following DDL and DCL statements in the SYS account.

Additionally, to use the TPR Report and ASH Report features, the users must grant the relevant permissions using the following DCL statement:

To collect statistics generated when executing SQL in the monitoring database, add the 'SQL_STAT_HISTORY', 'SQL_STAT_HISTORY_THRESHOLD', and 'SQL_STAT_HISTORY_QSIZE' parameters to the tip file. The descriptions for each parameter are as follows.

After completing the application.yml file settings, configure the TPM Agent environment in the following order.

set.sh script content

The users can view various metrics of instances within the currently monitored group.

Through customization, the users can place all real-time charts, sessions, and lock monitoring tables supported by SysMaster in any desired location and size.

Clicking on a chart allows the users to navigate to the desired screen.

Click the [Realtime] > [Lock Monitoring] menu in the global navigation bar to open the Lock Monitoring screen.

The Lock Monitoring screen displays lock information between sessions in a tree format. Therefore, the users can monitor the Holder Session that is currently holding the lock and the Waiter Session that is waiting to acquire the lock. Additionally, the users can monitor the session holding the lock and terminate a specific session.

The following is a description of the items provided in the Lock Tree Table screen.

Click [Realtime] > [Main Monitoring] > [Server Monitoring] in the global navigation bar to open the Server Monitoring page.

The Server Monitoring page displays information about OS-level CPU and memory system resource usage, as well as CPU and memory usage for processes. It provides filtering functionality by conditions such as PID, User, CPU (%), and Memory (%), allowing the users to monitor the overall status of resource usage across all processes.

Clicking the [Refresh] button in the top-right corner of the Server Monitoring page allows the users to monitor CPU usage in real time.

The CPU screen in the top-left corner of the Server Monitoring page displays CPU usage by User and System areas, as well as the current total CPU usage in a chart.

For user convenience, the Instance Monitoring page provides a Default Layout.

The list of monitoring metrics included in the Default Layout is as follows.

• [System] CPU Usage

Click the [Analysis] > [Usage Analysis] > [Temp Usage] menu in the global navigation bar to open the Temp Usage screen.

This screen displays the change in Temp size over time for the specified period.

The users can view detailed information about the total Temp usage of the selected items in Temp Usage.

Click the [Analysis] > [Usage Analysis] > [Filesystem Usage] menu in the global navigation bar to open the Filesystem Usage screen.

This screen displays the changes in the size of files mounted on servers by filesystem name during the specified period.

The following is a description of the items provided in the Filesystem Usage screen.

An area that displays the status of DB instances included in the monitored group and the current status of alerts for each instance.

Each instance is assigned a color and, in the case of TAC/TSC clusters, is grouped together and deployed.

In Instance Overview, the users can see the status of each instance at a glance. \ If an Alert item appears in the right-hand Alert section, it indicates Normal status. If Agent Disconnected or DB Down occurs, the corresponding status is displayed on the right.

The users can hide or expand the Instance Overview menu by clicking the arrow button on the right.

Instance Status Description

The status of the monitored DB includes Normal, Agent Disconnected, and Down.

• Normal: The DB is running, connected to the TPM Agent, and collecting metrics.

• Agent Disconnected: The DB is running but is not connected to the Agent, so metrics are not being collected.

• Down: Indicates that the DB instance is down or unable to establish a connection.

Super Admins can register monitoring targets by clicking the 'Import button'.

The users can view the status of alerts generated for each instance on the right side of the instance item. Clicking the corresponding button allows the users to check the status of Error/Warning alerts.

The users can select a specific instance from the Instance Overview to display only data for that instance in the Card View and Custom Area.

When an instance is selected, Auto Refresh stops in all areas of the Dashboard, and all data in all areas is frozen to the point in time when the instance was selected.

Click each instance to quickly switch to the corresponding menu or view the instance's information via Instance Info.

The drop-down menu is divided into two sections.

• Recommend: Menus recommended by SysMasterDB

  • : Moves to the Performance Trend menu for the selected instance.

  • : Moves to the Instance Monitoring menu for the selected instance.

The users can access each menu in SysMaster and use its functions via the Global Navigation Bar.

The menus accessible via the GNB are Realtime, Analysis, Notifications, Manual Download, Settings, and Profile.

Session Monitoring - Monitor real-time session metrics such as logical reads, physical reads, and execution counts.

Server Monitoring - Monitor OS-level resource usage, such as CPU and memory usage, and resource consumption by process with filter options.

Instance Monitoring - Monitor selected instances in real time with customizable chart layout the users set.

- Monitor tablespace usage and status with hourly updates and real-time data collection.

- Automatically collect database file usage every hour, with real-time updates available when needed.

- Monitor temporary tablespace usage to detect inefficient queries or excessive resource usage.

- Monitors undo usage for sessions with uncommitted transactions.

Monitor session lock information with a tree view and terminate blocked sessions as needed.

- Visualize the TSC cluster topology and monitor database roles, status, and TSN details.

- Analyze long-term performance trends using graphs and time slice functions.

- Analyze the top SQL statements that are the main causes of high resource usage.

- Visualize resource usage by time period using heatmaps and drill-down analysis.

- Compare and analyze changes in SQL execution plans (SQL Plans) over a specified period.

- Monitor session connection trends and real-time session status.

- Tracks SQL statements that triggered Hard Parse events.

- Track system and user-defined alert history.

- Tracks the number and details of invalid database objects.

- Tracks changes in tablespace size over time.

- Tracks changes in the size of the server's filesystem.

- Tracks changes in segment size over a specified period.

- Monitors changes in the size of temporary tablespaces by time.

- Tracks changes in the size of the undo tablespace over time.

- Generate and analyze performance reports at the instance or cluster level.

- Generate and view ASH reports for active session analysis.

Click [Realtime] > [Usage Monitoring] > [Tablespace Usage] in the global navigation bar to open the Tablespace Usage page.

The Tablespace Usage page displays information about tablespace usage.

Current Tablespace Usage

The users can view the tablespace usage and status information for the monitored database. The default collection interval is 1 hour, but the users can use the [Collect] button in the upper-right corner to collect and display real-time information for the specified time.

In the Last 24 hours history, the users can view the usage information to date in grid format or check the trend of changes in chart format.

In Segment Size, the users can view the size of each segment type within the Log Time selected from the Last 24 hours history. The collection unit for this information is 1 hour.

Click the [Realtime] > [High Availability Monitoring] > [TSC Monitoring] menu in the global navigation bar to open the TSC Monitoring screen.

The TSC Monitoring screen displays the TSC list, network configuration for each TSC, recovery status charts via TSN, and real-time status of the Primary DB and Standby DB.

The users can set the automatic refresh interval. The users can refresh immediately by clicking the [Refresh] button.

TSC List

The users can view the TSC list.

The users can view the TSC network configuration.

Click the [Overview] button to view the TSN chart and monitor the recovery status.

The users can monitor the status of the Primary DB and Standby DB in a table format.

By clicking on each instance name in the Primary Database or Standby Database, the users can view the Instance info in the right-side panel.

The following is a description of the items provided on the Primary Database screen.

The following is a description of the items provided in the Standby Database screen.

Click the [Analysis] > [Usage Analysis] > [Undo Usage] menu in the global navigation bar to open the Undo Usage screen.

Undo Usage

This screen displays the changes in Undo size by time unit for the specified period.

Total Undo Usage

The users can view detailed information about the total Undo usage of the selected items in Undo Usage.

The users can view detailed information about sessions that used Undo for the selected item during the specified time period.

When the users click Sid in Session Undo Usage, the users will be taken to the Undo Detail page.

On this page, the users can view the usage and change in undo usage in minutes and seconds.

Additionally, session information can be viewed at the bottom of the page.

Click the [Analysis] > [Usage Analysis] > [Segment Usage] menu in the global navigation bar to open the Segment Usage screen.

The users can select the date the users want to view. The Segment Usage list for the selected period shows a simple overview of usage increases and decreases.

This screen shows the changes in size for each segment name during the specified period.

The following is a description of the items provided in the Segment Usage screen.

• The layout Settings feature is available to users with Super Admin and Admin permissions.

• Common users can only use this feature if they have been granted Custom permissions by an Admin user.