Overview

This document explains the methods used when migrating to Tibero DBMS.

Methods

1. T-UP

Features

• Internally uses JAVA’s JDBC Driver to connect to both the Source DB and Tibero, so the Source DB and Tibero JDBC Driver are required, and JDK or JRE must be installed in advance.
• If the Source DB is a heterogeneous RDBMS, the Source DB’s JDBC Driver is also required.
• A separate PC (client) capable of running T-UP is required, and this client PC must be able to communicate over the network with both the Source DB and Tibero.
• Since data moves through the network twice in the direction Source DB T-UP Tibero, it may be disadvantageous for large volume transfers.
• Supports transferring entire databases, users, and tables, and is provided in a GUI format, making it easy to operate.
• If a problem occurs during the process, it does not stop; problems are handled after the entire transfer is complete.

Preliminary Tasks (Optional)

• If you want to change the data file path and name within the Tablespace, you must extract the Tablespace creation statement and manually create it in advance.
• If you want to change the Default Tablespace for a Schema (=user), you must extract the Schema creation statement and manually create it in advance.

2. Table Migrator

Features

• Command-based and internally uses JAVA’s JDBC Driver to connect to the Source DB and Tibero, so the Source DB and Tibero JDBC Driver are required, and JDK or JRE must be installed in advance.
• No separate PC (client) is required; it runs on the Source DB server or Tibero server.
• Since no intermediate server is needed, data moves through the network only once.
• Only one table’s data can be transferred at a time, which is advantageous for transferring large tables.
• Supports conditional clauses or partitioned tables.

Preliminary Task (Required)

• Before using Table Migrator to migrate the DB, the table to be migrated must be created in advance.

3. DB Link

Features

• Create a DB Link object on either the Source DB or Tibero.
• Since no intermediate server is needed, data moves through the network only once.
• Only one table’s data can be transferred at a time, which is advantageous for transferring large tables.

Preliminary Tasks (Required)

• Before using DB Link to migrate the DB, DB Link configuration must be performed.
• If the Source DB is Oracle, configuring Tibero to Oracle DB Link has fewer restrictions.

4. tbLoader

Features

• Only data is created as SAM files and can be loaded all at once.
• Advantageous for transferring large amounts of data.

Preliminary Tasks (Required)

• Before using tbLoader to migrate the DB, text files (SAM files) must be created in advance from the Source DB and copied to the Tibero server.

5. tbExport / tbImport

Features

• Since they are internal utilities of Tibero, they can only be used for migrating between Tibero instances (heterogeneous migrating is not possible).
• tbExport / tbImport are installed together during the Tibero installation process and are removed if Tibero is uninstalled.
• Implemented in JAVA language, and JDK or JRE must be installed in advance.
• Extracts internal Schema and data of Tibero as SQL statements.
• Supports entire databases, users, and tables, and when extracting one Schema object, related objects are automatically extracted together.
• Files generated by running tbExport can be saved on FTP or CD-ROM and transferred to a remote Tibero for tbImport; tbImport can also be performed over the network without physically moving the generated files.

Preliminary Task (Required)

• Appropriate parameters must be applied for performing tbExport / tbImport.

6. Manual Migration

Features

• Extract scripts using client tools on the Source DB and manually apply them to Tibero.
• Data cannot be manually moved, so tools like T-UP or Migrator must be used for data migration.
• If a problem occurs during the process, it can be addressed immediately before proceeding.
• Can be automated by linking with shell scripts.

Preliminary Task (Required)

• Before using manual migration, DDL creation scripts must be extracted in advance using client tools.