Functionality Overview¶
Migration Toolkit is a powerful command-line tool that offers granular control of the migration process. Using Migration Toolkit is a two-step process:
Edit the
toolkit.propertiesfile to specify the source and target database.Invoke Migration Toolkit at the command line, specifying migration options.
Migration Toolkit facilitates migration of database objects and data to an Advanced Server or PostgreSQL database from:
Oracle
MySQL
SQL Server
Migration Toolkit also allows you to migrate database objects and data to an Advanced Server database from Sybase. You can also use Migration Toolkit to migrate between Advanced Server and PostgreSQL. Migration Toolkit includes a number of options, allowing you granular control of the migration process:
Use the
-safeModeoption to commit each row as it is migrated.Use the
-fastCopyoption to bypass WAL logging to optimize migration.Use the
-batchSizeoption to control the batch size of bulk inserts.Use the
-cpBatchSizeoption to specify the batch size used with the COPY command.Use the
-lobBatchSizeoption to specify the batch size used for large object data types.Use the
-filterPropoption to migrate only those rows that meet a user-defined condition.Use the
-customColTypeMappingoption to change the data type of selected columns.Use the
-dropSchemaoption to drop the existing schema and create a new schema prior to migration.On Advanced Server, use the
-allDBLinksoption to migrate all Oracle database links.On Advanced Server, use the
-copyViaDBLinkOraoption to enable thedblink_oramodule.
Object Migration Support
Migration Toolkit migrates object definitions (DDL), table data, or both. The following table contains a platform-specific list of the types of database objects that Migration Toolkit can migrate:
Object |
Oracle |
Sybase |
SQL Server |
MySQL |
|---|---|---|---|---|
Schemas |
X |
X |
X |
X |
Tables |
X |
X |
X |
X |
List-Partitioned Tables |
X |
|||
Range-Partitioned Table |
X |
|||
Constraints |
X |
X |
X |
X |
Indexes |
X |
X |
X |
X |
Triggers |
X |
|||
Table Data |
X |
X |
X |
X |
Views |
X |
X |
||
Materialized Views |
X |
|||
Packages |
X |
|||
Procedures |
X |
|||
Functions |
X |
|||
Sequences |
X |
|||
Users/Roles |
X |
|||
Profiles |
X |
|||
Object Types |
X |
|||
Object Type Methods |
X |
|||
Database Links |
X |
|||
Queues |
X |
For detailed information about the commands that offer granular control of the objects imported, please see Schema Object Selection Options.
Online Migration vs. Offline Migration
Migration Toolkit can migrate immediately and directly into a Postgres database (online migration), or you can also choose to generate scripts to use at a later time to recreate object definitions in a Postgres database (offline migration).
By default, Migration Toolkit creates objects directly into a Postgres database; in contrast, include the -offlineMigration option to generate SQL scripts you can use at a later time to reproduce the migrated objects or data in a new database. You can alter migrated objects by customizing the migration scripts generated by Migration Toolkit before you execute them. With the -offlineMigration option, you can schedule the actual migration at a time that best suits your system load.
For more information about the -offlineMigration option, see Offline Migration
Options.