Pre-Migration Considerations
This section explains the pre-migration considerations.
Considerations for migration
Migration Procedure
The procedure for the database migration requires a database and application migration team and a testing team.
[Figure 1] Migration Procedure
Migration Complexity
When migrating from another database to Tibero, the complexity varies depending on the situation, and the migration method may differ on the level of complexity.
The following explains the scenarios for each complexity level.
Low
Consists of a few schemas (=users).
The dependencies between objects are not complex.
It consists of objects that are in use, and all are VALID.
High
Consists of many schemas (=uses).
The dependencies between objects are complex.
Many objects are not in use and are INVALID.
Pre-Migration Recommendations
To reduce the migration validation time, it is recommended that the client’s DB administrator clean up any INVALID objects in the Source DB before starting the migration.
Pre-Migration Analysis
The compatibility validation is conducted before migration using the analysis feature of T-UP
[Figure 2.1 ] T-UP Analysis
[Figure 2.2 ] T-UP Analysis
[Figure 3.1] T-UP Analysis Report
[Figure 3.2] T-UP Analysis Report
Last updated