Skip to main content
๐Ÿ““ Tibero Online Manual Click here ๐Ÿ““

Search

Welcome to Tibero GTS!

How to Extract T-UP Conversion DDL Script

Document Type | Technical Information

Category | Migration

Applicable Product Versions | 6FS07, 6FS07PS, 7FS02, 7FS02PS

Document Number | TMITI020

 

Overview

This document explains how to extract conversion DDL scripts using T-UP in order to extract Oracle DDL.

 

Method

1. T-UP > Migrator

Run T-UP and select Migrator.

 

 

2. Source Database > Type Conversion

Select the data types corresponding to Oracle.

 

3. Schema Object

Select Independent Objects, check Tablespace and User, then select Dependent Objects and check the objects for which DDL extraction is needed.

 

4. Migration Option

Disable Data Transfer and DDL Execution, then check Export DDL Script and specify Filename and Path. (If Data Transfer and DDL Execution are not disabled, DATA will be transferred as well.)

If you need to separate files by schema, select Create Individual DDL Script Files.

 

5. Target Database > Summary

Verify that the extraction target is correct.

 

6. Data Migration

Click the Migrate button to execute migration. (Actual DATA will not be transferred; only the DDL script will be extracted.)

 

7. Result > Close

The Result stage displays Execution information; DDL Export information is not displayed.

 

8. File Verification

Go to the specified path and verify that the DDL script has been extracted correctly.

 

9. DDL Script Correction

Modify the extracted script so that it can be executed in Tibero.

 

Tablespace DDL

  • If the Tibero DB has already been created in advance, System, Undo, and default Temp Tablespaces already exist, so do not create them. (However, Temp Tablespaces other than the default Temp Tablespace must be created.)
  • Exclude Oracle-specific Tablespaces. (e.g., SYSAUX)
  • If adjustments are needed for data file paths, filenames, or sizes, modify them within the DDL script.
  • Items not supported by Tibero must be commented out.
Item Description
BLOCKSIZE 4K

Tibero does not allow block size specification per Tablespace, so comment this out.

It is fixed during DB creation in the initialization parameters, typically 8K is used.
SEGMENT SPACE MANAGEMENT MANUAL Tibero only supports AUTO; change MANUAL to AUTO.
FLASHBACK ON Tibero supports FLASHBACK in full mode via parameters, so comment this out.
TABLESPACE GROUP

TABLESPACE GROUP feature is not supported, so comment this out.

Use multiple data files separated within a single Tablespace.

 

User DDL

  • Passwords per user need to be confirmed in advance. (Contact the Oracle DB administrator.)
  • By default, user passwords are set to tibero.
  • Apply only to users subject to conversion; Oracle default users do not need conversion.
  • Items not supported by Tibero must be commented out.
Item Description
GRANT UNLIMITED TABLESPACE TO USER_NAME Tibero has UNLIMITED by default and does not support this syntax, so comment it out.
ALTER USER USERNAME QUOTA UNLIMITED ON USERNAME User quota feature is not supported, so comment it out.

 

Table DDL

  • Active Value errors may occur due to character set conversion from Oracle.
  • If errors occur in the column type section, refer to Data Types "Oracle".

 

 

 

Related to