Guide Information

Guide Title: OwlDB User Guide

Publication Date: 2026-09-30

Software Version: OwlDB v.2.0.0

Guide Version: v.2.0.0

Overview

This guide is written for all users who wish to conveniently operate and manage databases using the features provided by OwlDB.

Prerequisite Knowledge

• Understanding of Databases

• Understanding of RDBMS

​

This document consists of a total of 5 chapters.

OwlDB is a managed database service that installs databases in cloud and on-premises environments and registers, integrates, and manages them as DB Services. This page covers OwlDB's operating environments, key features, and supported engines and topologies.

Operating Environment

Cloud Environment Support

This is a method of dynamically creating and operating databases by utilizing cloud infrastructure resources. Based on IaC (Infrastructure as Code), it automates infrastructure provisioning and database configuration, allowing users to build and scale database environments with the desired specifications from the console.

On-Premises Environment Support

This is a method of operating databases based on physical infrastructure resources such as servers, networks, and storage that the customer owns. It is designed to efficiently utilize fixed infrastructure resources and supports closed network environments that are isolated from external networks. Through OwlDB, you can install new databases on hosts, or integrate and centrally control existing databases already in operation as OwlDB management targets.

Scope of Provision by License

OwlDB differs in the environments and features provided depending on the license.

Based on common management features universally used in both environments, OwlDB provides dedicated features optimized for the infrastructure characteristics of cloud and on-premises respectively.

The relational database (RDBMS) engine specifications supported by OwlDB and the architecture configurations for each environment are as follows.

This describes the components and functions of each area of the console screen.

On the Bootlog page, you can check status and error information related to the DB boot procedure and diagnose the cause of problems. You can view logs by boot/down event, and clicking each message shows the full detailed log in the right side panel.

Viewing the Bootlog

The Bootlog screen displays the boot/shutdown event history of the selected DB instance. After narrowing down the logs you want with event, mode, and status filters and message search, click a message link to view the full detailed log in the right side panel.

Query Period

Set the period to view at the top of the screen. Choose from the last 1 day, 3 days, 7 days, or 1 month, or specify a start date and end date by direct input.

1. Click Monitoring > Log Monitoring > Bootlog.

2. Select the period to view.

3. Set the event, mode, and status filters to narrow the scope of the query.

4. Click the message link of the log you want to check.

5. Check the details of the log in the right side panel of the screen.

To update the monitoring screen in real time, an auto refresh feature is supported.

1. Click the ⚙️ icon in the top left.

2. Set the refresh interval.

On the Syslog page, you view system logs such as events, warnings, and errors occurring in DB instances. Tibero lets you check the raw logs in the DB tab, while OpenSQL additionally supports, through the Component tab beyond the DB tab, viewing and downloading the log file lists of the OpenHA, OpenProxy, and OpenBackup components.

On the Monitoring > Log Monitoring > Syslog page, you check system logs such as events, warnings, and errors occurring in the system. When you enter the page, the DB tab is activated by default, and logs are displayed line by line. A row number is displayed on the left of each row, and the raw log appears as is in the body area.

1. Click Monitoring > Log Monitoring > Syslog.

2. Select the desired period from the query period dropdown.

Notifications are provided for various events that occur while using OwlDB. You can check notifications by clicking the 🔔 icon in the top right of the console screen.

• Click the ✔ icon to the right of a message to change its read status.

• Messages marked as read are automatically deleted after 30 days.

• Clicking the meatball menu icon in the top right > Mark All as Read marks all messages as read.

The Overview page lets you view a complete overview of the selected database at a glance. You can view detailed information such as database information, instance information, and version information, and you can perform various operations such as starting, stopping, and deleting the database.

On the Data Space page, you can query and manage the data storage units of the DB service.

The screen layout and available features vary depending on the engine type of the connected DB service.

Through license rebuilding and renewal, you maintain and replace the license configuration of a DB service operating in the BYOL method.

Rebuilding is a feature that restores the original configuration by creating additional missing instances when the license configuration falls short of the initial settings. License renewal is a feature that replaces the license by uploading a new license file starting from 90 days before expiration, and it applies only to BYOL licenses. Both features can be performed by users with Root and Member permissions on the Management > Overview > License tab.

License Rebuilding

Rebuilding can only be performed when an idle license exists.

1. In Management > Overview, click the License tab.

2. Click the Rebuild button.

3. In the confirmation modal, compare the number of currently operating instances with the final configuration after rebuilding.

4. Click the Confirm button.

When the expiration date of a BYOL license is within 90 days, an expiration notice banner is displayed on the Overview page, and you can renew by uploading a new license file. On the renewal screen, basic information such as the service name, DB engine, license option, topology, and number of nodes is displayed as read-only.

1. Click the Renew link in the banner or the License Renewal button.

2. Upload the license file by clicking the Upload button or by dragging and dropping the file.

3. Check the file to be validated.

4. Click the Validate button to verify the validity of the license file.

You can check the following information for the uploaded file in the list.

You can perform the following functions by selecting a DB Service in Management > Overview or Dashboard and then clicking the Actions button.

Stopping and Starting a DB Service

1. Click the Actions button.

2. Click the Stop or Start button.

Deleting a DB Service

1. Click the Actions button.

2. Click the Delete button.

3. Enter the DB Service Name in the input field.

4. Click the Confirm button.

1. Click the Actions button.

2. Click the Delete button.

3. Enter the DB Service Name in the input field.

4. Click the Confirm button.

This feature is enabled only when DR is configured.

1. Click the Actions button.

2. Click the Role Switch button.

3. Enter the password.

4. Click the Confirm button.

OwlDB continuously monitors the status of the Primary database configured with DR (or HA) to detect failures and automatically perform failover. This page explains the automatic failover behavior and the policy for each automation level.

Failure detection

The system performs a health check every second, and if the Primary (Tibero) or Leader (OpenSQL) DB remains in the Unavailable state for 30 seconds, failover is performed automatically. In a Tibero TAC configuration, a failure is determined when all Primary nodes are in the Unavailable state.

Step-by-step notification policy

In a Cloud environment, the automation level provided differs depending on the DB engine and license type (LI/BYOL).

Application : Tibero LI · BYOL, OpenSQL LI · BYOL

No automatic action is performed, and when a failure occurs, the user directly promotes the Standby/Replica to Primary/Leader using the Switch Role button. Configuration normalization after promotion is also performed manually by the user.

Application: Tibero LI (Tibero BYOL · OpenSQL not provided)

The Old Primary is terminated without restarting, and a new Standby is not created.

Applies to : Tibero LI · BYOL (OpenSQL not provided)

Automatically creates a new Standby to recover the high-availability configuration.

Application : Tibero LI · BYOL, OpenSQL LI · BYOL

Automatically handles the entire process from failover to Old Primary/Leader resynchronization and new Standby/Replica creation.

In Management > Backup/Restore > Backup, you can view the database backup list and perform creation, modification, deletion, and restoration.

A backup saves the state of the database at a specific point in time as an image. Backups can be created automatically through the scheduler or manually by the user, and you can restore to a desired point in time through Full Restore or Point-in-Time Recovery (PITR). Additional charges apply based on the backup storage usage.

The retention period can be set from 1 hour up to a maximum of 35 days.

Viewing the backup list

When you enter the Management > Backup/Restore > Backup menu, the backup list of the current DB Service appears. Each row represents a single backup image, and backups are displayed on a single-image basis without distinguishing between Full and Incremental.

The columns displayed in the list are as follows.

When you enter a name and retention period, a single backup image of the current point in time is created.

1. On the Backup page, click the Create button.

2. Enter a name.

3. Select the end date of the retention period in the calendar. The backup is retained until the selected date and expires at 00:00:00 the following day.

4. Click the Create button.

When you select one backup from the backup list and click the Restore button, the restore modal appears. Select a restore type to restore the database to a specific point in time.

Restoration can take up to several hours, and you can check the progress in Restoration history.

1. Select one backup to restore.

2. Click the Restore button.

3. Select a restore type.

4. If you select PITR, select the date and time to restore to. The selectable range is between the restorable point of that backup and the current time.

Edits the name and retention period of a backup.

1. Select one backup to edit.

2. Click the Edit button.

3. Change the name or retention period.

4. Click the Save button.

Permanently deletes the selected backup image.

1. Select one or more backups to delete.

2. Click the Delete button.

3. Confirm the deletion notice modal.

4. Click the Delete button.

Stores a specific backup in long-term archive storage. Archived backups are not automatically deleted even after the retention period expires, and can be recovered when needed.

1. Select one backup to archive.

2. Click the Archive button.

3. Enter a name.

4. Select the retention period.

Check the list of backups in long-term archive in the Archive section within the Backup/Archive page.

Archived backups with an expiration date within 30 days display a ⚠️ icon in front of the name. Hover over the icon to see the scheduled deletion date and time. If long-term archiving is needed, click Edit before expiration to extend the retention period.

1. Go to Management > Backup/Recovery > Backup.

2. Scroll down the page to the Archive section.

3. Find the desired archived backup using a filter or name search.

Edits the name and retention period of an archived backup.

1. Select one archived backup to edit.

2. Click the Edit button.

3. Change the name or retention period.

4. Click the Save button.

1. Select one archived backup to recover.

2. Click the Restore button.

3. Enter the recovery date and time.

4. Click the Restore button.

1. Select one or more archived backups to delete.

2. Click the Delete button.

On the Management > Parameters > Settings page, you can view and modify the parameter values required for database operation.

Each parameter displays its name, data format, default value, current value, Config value, and whether it is a dynamic parameter. Dynamic parameters can be applied immediately without restarting the database, while static parameters require a restart after modification. Tibero also supports temporary application, where changes are reflected without a restart but are restored upon restart.

The range of parameters that can be viewed and modified varies depending on the DB engine. Tibero provides only DB parameters, while OpenSQL provides DB parameters and OpenHA parameters separated into tabs.

When you enter the Management > Parameters > Settings menu, the parameter list appears.

Tibero displays the DB parameter list directly. OpenSQL (Azure) switches between the DB tab and the OpenHA tab to view each set of parameters.

When a new version of OwlDB is released, you can apply the latest version directly from the console.

1. A sky-blue update notification banner appears at the top of the dashboard.

2. When you click the Update button in the notification banner, the update proceeds.

Address

TmaxTower, 45 Jeongja-il-ro, Bundang-gu, Seongnam-si, Gyeonggi-do

Website

Technical Service Center

Tel : +82-1544-8629

E-Mail : docs@tibero.com

Restricted Rights Legend

The contents of this user guide and the program described herein may be used only under a license agreement with TmaxTibero Co., Ltd., and the user guide may be distributed or copied only within the scope of the license agreement.[^1] No part or all of this user guide may be transmitted, reproduced, distributed, or used to create derivative works by any means, electronic, mechanical, recording, or otherwise, without the prior written consent of TmaxTibero.

This software user guide and the program license agreement shall in no case be construed as transferring any intellectual property rights (whether registered or not) related to the user guide and program, and do not grant any right to use brands, logos, trademarks, etc. The user guide is intended solely for the provision of information, and assumes no direct or indirect contractual liability arising therefrom, and the contents of the user guide do not guarantee the satisfaction of any specific legal or commercial conditions. The contents of the user guide are subject to change without notice due to product upgrades or modifications, and are not guaranteed to be free of errors.

Users who do not have an OwlDB account can request account creation directly on the Login page.

1. On the Login page, click the Request Account Creation button.

2. Enter the information below. ID Name Password Confirm password Email

3. Click the Request button.

4. In the account creation request modal, click the Confirm button.

5. When you click the Confirm button, you are moved to the Login page.

When an administrator approves the account creation, an account approval completion email is sent to the registered email address.

The notification email includes the following information.

• ID

• OwlDB access URL

After receiving the approval email, you can log in with the corresponding account information.

Root first login

Once OwlDB deployment is complete, the Root account information is sent to the email address entered when creating the stack.

1. Go to the connection URL listed in the email.

2. Enter the Root account and temporary password received in the email.

3. Click the Login button.

4. On first login, you are automatically redirected to the Change Password page for security reasons.

On the Login page, enter your account information to connect to OwlDB.

1. On the Login page, enter your ID and password.

2. Click the Login button.

3. Once authentication is complete, you are redirected to the Dashboard page.

If you have forgotten your ID, you can check your ID through your registered email address.

1. On the Login page, click Find ID.

2. Enter your registered email address.

3. Click Send Email.

4. Once the entered email address is verified, an email with your ID is sent.

Once email verification is complete, an ID notification email is sent to the registered email address.

The email includes the following information.

• ID

• Shortcut to the OwlDB Login page

After receiving the email, click Go to OwlDB or move to the Login page and log in with the provided ID.

If the ID notification email has not arrived, you can resend it by clicking Resend Email.

If you have forgotten your password, you can verify your registered account information, receive a temporary password, and change it to a new password.

1. On the Login page, click Reset Password.

2. Enter your ID and registered email address.

3. Click Send Email.

4. Once the entered account information is verified, a temporary password is sent to the registered email address.

1. Check the temporary password in the email.

2. On the Login page, enter your ID and the temporary password.

3. Click Login.

4. You are automatically moved to the Reset Password page.

1. Enter a new password.

2. Re-enter the password to confirm it.

3. Click Change Password.

4. Once the password change is complete, you are moved to the Login page.

Role switching is a feature that manually swaps the roles of the Primary DB and Standby DB in an environment using a DR (Disaster Recovery) configuration. Administrators can perform role switching directly in various situations such as failure response or regular inspections, and the work is done on the Management > Overview page.

Role switching proceeds in one of two ways depending on the current state of the Primary DB. The system automatically determines which method to use after checking the state of the Primary DB.

Role Switch

The role switching modal consists of two steps: Security Authentication and Switch Settings. In the first step, you verify administrator privileges by entering the password of the currently logged-in account, and in the second step, you select the new Primary DB.

1. Go to the Management > Overview page.

2. Click the Actions button.

3. Click Role Switching in the dropdown list.

4. In the Security Authentication Before Role Switching step, enter the password of the currently logged-in account and click Confirm. If the password does not match, the error message "Password does not match." appears.

5. Select the Standby DB to promote from the Select New Primary DB dropdown.

6. Enter Remarks if necessary.

7. Click Confirm.

After the switch request, the system automatically diagnoses the current state of the Primary DB and determines the switching method.

• Primary DB is in a normal state: Performed using the Switchover method. The current Primary is safely shut down and data synchronization is completed, after which the selected Standby DB is promoted to the new Primary.

• Primary DB is in an abnormal state: Performed using the Failover method. The selected Standby DB is immediately promoted to the new Primary to restore service.

Subscribing to OwlDB in Azure Marketplace

This page describes the procedure for subscribing to OwlDB in Azure Marketplace.

1. Search for OwlDB in Azure Marketplace.

2. Select OwlDB from the search results.

3. Click Get It Now.

4. Click Continue to subscribe to the Subscription.

5. Click Create to begin the configuration for deploying OwlDB.

This page describes the parameters to enter in order to deploy OwlDB with an ARM Template.

Select the subscription and resource group for managing the deployed resources and costs. A Managed Application resource that holds the OwlDB deployment information is created in the resource group.

Directly specify the parameters of the ARM (Azure Resource Manager) Template for deploying OwlDB.

Specify the application's unique identifier and the resource group for resource management.

This page describes the tasks that must be performed after deploying OwlDB.

After deploying OwlDB, you must create an SSH Key resource within the automatically created OwlDB service resource group. The SSH Key is used in the OwlDB database provisioning process.

1. Search for SSH keys in the .

2. Select SSH keys from the search results.

3. Click Create in the upper left.

4. In Project details, select the resource group that was automatically created after OwlDB was created.

This page explains how to connect to the deployed OwlDB.

Once OwlDB deployment from the Marketplace is complete, a notification email containing the OwlDB connection address and account information is sent to . You can connect to OwlDB through this email. If you do not receive the email, contact the .

The OwlDB connection URL is in the format https://<sub-domain>.owl-db.com, where <sub-domain> contains a domain value unique to each customer.

The domain value unique to each customer can be checked using the following methods.

• Check it in Azure Portal > OwlDB resource group > Settings - Deployments > the Deployment corresponding to OwlDB > Outputs > Sub Domain Name.

• Refer to the hosting zone name corresponding to OwlDB among the resources of the DNS zones service.

On the Eventlog page, you can view event logs that occurred according to the rules defined by OwlDB.

In the Monitoring > Log Monitoring > Eventlog menu, you can check logs that occurred in the DB Service, and filter out only the events you want by combining the query period and filters. Results are displayed in order of most recent received date.

1. Click the Monitoring > Log Monitoring > Eventlog menu.

2. Select the query period. To specify a particular range, select Direct Input and then set the start date and end date.

3. Select a status or message filter to narrow the type of events to view.

4. To find a specific message, enter a keyword in the search box.

5. In the query results, click the DB Service or instance name to go to its detail page.

The types of event logs displayed in the message column are as follows.

Changes the configuration of a running Cloud DB service, such as instance type, DR configuration, and storage.

Spec changes start from Management > Overview and proceed through five steps: Engine Options → DR Configuration → AZ Configuration → Instance Configuration → Configuration Information Review. In each step, you review the current settings and modify the necessary items, and in the final step, you compare the configuration before and after the change along with the estimated cost and request to apply it. Depending on the changes, a DB service restart may be required.

The range of changeable items differs depending on the DB engine and license type (LI/BYOL). The LI license allows changing most items including instance type, DR configuration, availability zone, and storage settings, while the BYOL license is limited in change scope to storage items such as volume size, IOPS, and MBps.

1. Go to Management > Overview.

2. Click Spec Change.

3. Go to each tab: Engine Options, DR Configuration, AZ Configuration, and Instance Configuration.

4. Set the items to change.

5. Go to the Configuration Information Review tab.

6. Review the configuration before and after the change and the estimated cost.

7. Click Complete.

8. Review the contents in the confirmation modal.

9. Click Confirm.

The items that can be changed differ depending on the engine type and license option.

• ¹ Can be changed between Single ↔ HA in OpenSQL LI

• ² Automatically determined by Topology in OpenSQL (HA → DR used, Single → DR not used)

• ³ Can be changed when initially configured to use DR

• ⁴ Can be changed when initially configured as HA

DB Service Name, DB Engine Type, License Option, and Node Count display the current settings and cannot be changed.

The changeable items are as follows.

• Edition: Select between Standard Edition (SE) and Enterprise Edition (EE). SE can use up to 8 vCPU, and EE has no vCPU limit. In TAC or HA Topology, EE is automatically applied, and it can be changed only with the LI license.

• Topology: Can be changed between Single ↔ HA only in OpenSQL LI.

In the Tibero TAC configuration of the LI license model, you can adjust the node count by directly adding or deleting TAC nodes in the instance Scale In/Out table. The minimum is 2 and the maximum is 4.

• Enable DR: Select whether to use DR. It can be changed directly only in Tibero LI, while OpenSQL is automatically determined by Topology (HA → DR used, Single → DR not used). BYOL cannot be changed.

• Failover Automation Level: Selects the failover automation level when DR is used. It is not displayed when DR is not used.

OpenSQL on the LI license model adjusts its configuration by adding or deleting Replica nodes in the Replica Scale In/Out table. Only Replica Node #2 and above can be deleted.

Check and set the Availability Zone (AZ) for each instance. Settings can only be configured for newly added instances.

Perform Scale Up/Down by changing the instance type. BYOL licenses cannot change the instance type.

The storage-related settings are as follows.

Compare and review the configuration before the change (left) and the configuration after the change (right). Changed items are shown in blue.

The estimated cost is displayed as hourly and monthly costs. The values are calculated based on the Seoul region, and the actual cost may vary depending on the region and actual usage.

After reviewing the information, clicking Done will result in different processing methods depending on the type of change.

View the status of databases running in OwlDB, and perform operations such as modify, stop, start, delete, role switchover, license renewal, and spec change.

Viewing database information

1. Click the Management > Overview menu.

2. Click the DB Service Alias dropdown button and select the database whose information you want to view.

3. Check the detailed information in the Operation Information, Instance, Installation Information, (DR/HA) Switchover History Management, and (BYOL) License tabs.

1. Click the pencil icon next to the DB Service alias.

2. Modify the DB Service alias and description.

3. Click the Save button.

Under My Page > Usage Management, you can view and manage the current month's usage status and past monthly usage history for databases (DB Service licenses), excluding infrastructure resources.

Usage Status

You can view this month's database usage status based on the DB service license. Data is automatically updated daily at 00:00 UTC.

1. Go to the OwlDB console screen > My Page > Usage Management > Usage Status menu.

2. Check the summary information at the top (usage period, number of DB services, total usage charge).

3. Check the detailed usage list in the table at the bottom. It supports a DB type filter (Tibero / OpenSQL) and name search.

You can view the monthly database usage history report and download it as a file. The final usage history report for the current month is automatically generated at 00:00 UTC on the 1st of the following month and is retained for up to 5 years.

1. Go to the OwlDB console screen > My Page > Usage Management > Usage History menu.

2. Use the calendar picker (query period selector) to set the desired range.

3. Check the monthly report list.

4. Select the report to download from the checkbox on the left of the list. When selecting a single report: download as a PDF file When selecting multiple reports:

When you click a report name in the usage history list, you can view the detailed information of that report.

The items that can be viewed are the same as in Usage Status.

• You can download the usage history as a PDF file by clicking the [Download] button in the upper right.

OwlDB can restart a database in a single-instance or multi-instance configuration.

The database restart feature can be accessed from the following menu paths.

• OwlDB Console Screen > Dashboard

• OwlDB Console Screen > Overview > Instances tab

• OwlDB Console Screen > Overview > Instance Details

Required Tasks Before Subscribing to OwlDB

This page describes the OS image subscription and SSH Key creation tasks that must be completed before subscribing to OwlDB.

1. OS Image Subscription

To build a database through OwlDB, a prior subscription to the Rocky Linux 9 (Official) - x86_64 AMI is required. The subscription method is as follows.

1. Search for and select Rocky Linux 9 (Official) - x86_64 in the AWS Marketplace.

2. Click Continue to Subscribe to subscribe to the Subscription.

2. SSH Key Creation

Before subscribing to OwlDB, you must create an SSH Key pair resource. The SSH Key pair is used in the deployment of OwlDB and the database provisioning process.

1. Search for and select Key pairs in the .

2. Click Create key pair in the upper right corner.

3. Enter the desired Key pair name in Name.

4. Select the Key pair type. For compatibility, the default setting RSA is recommended.

This page describes how to subscribe to OwlDB on AWS Marketplace and start the deployment configuration.

1. Search for and select OwlDB in the .

2. Click Continue to Subscribe to subscribe to the Subscription.

3. Click Continue to Configuration to start the configuration for OwlDB deployment.

This page explains the process of deploying OwlDB using AWS CloudFormation step by step.

• Select the items below and click Continue to Launch.

• Check the Configuration details.

• Under Choose Action, select Launch CloudFormation and click Launch.

Creating a CloudFormation stack requires going through all of the following four steps in order.

For the template preparation item in the prerequisites, use the choice of an existing template.

Specify template

Provide a stack name

Parameter [Fulfillment option : Deploy into new VPC]

OwlDB Infra Setting

OwlDB Setting

Personal Information

Check and review the specified template and stack details.

Click Submit to start provisioning.

This page explains how to connect for the first time after OwlDB deployment is complete and how to check the connection URL.

Once OwlDB deployment from the marketplace is complete, a guide email containing the OwlDB connection address and account information is sent to the email entered when creating the stack. Connect to OwlDB through this email. If the email is not received, contact .

Check the customer-specific unique domain value using the following methods.

1. Check it in CloudFormation console > Stacks > Stack name > Outputs tab > ManagementPlaneStackId.

2. Refer to the hosting zone name corresponding to owl db among the hosting zones of the Route 53 service.

On the instance monitoring page, you can check the key performance metrics of database instances in real-time line charts.

Core metrics such as CPU usage, memory usage, and the number of active sessions are always displayed at the top of the screen. Select the Quick Insight, Load, I/O, Writes, or All tab to focus on situation-specific metrics, and switch between Tibero and OpenSQL using the DB Type toggle in the GNB to apply the metric configuration suited to each engine.

The instance monitoring page starts by selecting the DB Type and the resource to view at the top of the GNB. The selectable resource hierarchy and the displayed metrics vary depending on the DB Type.

1. In the left menu, click Monitoring > Instance Monitoring.

2. In the GNB's DB Type toggle, select Tibero