System Requirements

1. Supported Platforms and Operating Systems

The officially supported platforms and operating systems for SysMaster DB 8.3 are as follows.

2. Hardware and software

The hardware and software requirements for installing SysMaster DB 8.3 are as follows.

3. Recommended patches for the monitoring database

The recommended patches for the monitoring database of SysMaster DB 8.3 are as follows.

Patch Number

Patch contents

240373

Improved missing OS user and machine information in sessions where the program is PE_SLAVE.

[Note] If this patch is not applied, OS user and machine information will be missing in sessions where the program is PE_SLAVE.

276404

Improved issue where a new physical plan was generated each time the internal query executed when querying Tibero's global view.

[Note] In SysMaster DB 8, global views are queried every second to collect lock information. If this patch is not applied, a physical plan is generated every second for a specific SQL statement, which may cause a no response issue when querying the SQL statement in [Analysis] > [Plan Analysis], etc.

279651f

libtpmstat library creation

[Note] If this patch is not applied, the libtpmstat library must be distributed along with the TPM Agent installation. TPM Agent 8.1.3 and later are not compatible with patches 279651e or earlier, so patch 279651f or later is required. Regardless of the 279651 patch version applied to Tibero, the 279651 patch version used during TPM Agent build must match the 279651 patch version of the library.

281081

V$TEMPSEG_USAGE view SESSION_NUMBER column value display issue improved

[Note] If the patch is not available, incorrect information may be displayed in the [Realtime] > [Usage Monitoring] > [Temp Usage], [Analysis] > [Usage Analysis] > [Temp Usage] menu.

304981b

[Note] If this patch is not applied, OS User and Machine information may be displayed incorrectly in SQL Trace information. 279651f Patch must be applied first, and is not compatible with patches below 279651e.

307175a

Fixed an issue where SQL Trace information was not collected for closed sessions.

[Note] If this patch is not applied, SQL Trace information may be significantly missing in environments where sessions are frequently opened and closed.

328607b

Fixed an issue where wait count and time were incorrectly adjusted for wait events when collecting wait count and wait time information.

[Note] Without this patch, wait time and wait count values may be displayed inaccurately.

304770a

TSC monitoring-specific patch [Note] If the patch is not installed, the information below will not be available in the V$DATABASE view, and TSC monitoring information will be displayed incorrectly, such as primary and standby not being distinguished.

1) OPEN_MODE에 value 추가
    - READ ONLY WITH APPLY

2) PROTECTION_MODE
   : Protection mode currently in effect for the database
    - UNPROTECTED
    - PROTECTION
    - AVAILABILITY
    - PERFORMANCE

3) DATABASE_ROLE
   : Current role of the database
    - PRIMARY
    - PHYSICAL STANDBY
    - LOGICAL STANDBY (TODO)
    - SNAPSHOT STANDBY
    - CASCADING STANDBY

4) STANDBY_BECAME_PRIMARY_TSN
   : TSN at which the physical standby database became primary

5) STANDBY_BECAME_PRIMARY_DATE
   : Time at which the physical standby database became primary

338513a

This patch is required for actual TPR integration. Only the package creation script needs to be executed without server patches.

338594a

This patch fixes a bug in the Tibero package that fails to delete TPR report files created on the Tibero server during TPR integration.

[Note] The TPR integration function works even without this patch, but the report files accumulate on the server and need to be deleted periodically.

Manual deletion of report files: Periodically delete report files starting with .tpr as follows.

rm -f .tpr*

149894l

This patch is required because TPR snapshot queries use a query not supported in Tibero 6 without this patch. Without this patch, queries will not work in Tibero 6.

250728f

Patch that enables viewing the V$INSTANCE view from the standby instance. Without this patch, the instance is not clustered.

PreviousPreparing for Installation NextInstallation Environment Setup

Last updated 11 days ago