3 Functionality Overview

Table of Contents Previous Next


3 Functionality Overview

Use the -safeMode option to commit each row as it is migrated.
Use the -fastCopy option to bypass WAL logging to optimize migration.
Use the -batchSize option to control the batch size of bulk inserts.
Use the -cpBatchSize option to specify the batch size used with the COPY command.
Use the -filterProp option to migrate only those rows that meet a user-defined condition.
Use the -customColTypeMapping option to change the data type of selected columns.
Use the -dropSchema option to drop the existing schema and create a new schema prior to migration.
On Advanced Server, use the -allDBLinks option to migrate all Oracle database links.
On Advanced Server, use the -copyViaDBLinkOra option to enable the dblink_ora module.
1.
Edit the toolkit.properties file to specify the source and target database.
For detailed information about defining toolkit.properties entries, please refer to Section 5, Building the toolkit.properties File.
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 Section 7.1, Offline Migration.

3 Functionality Overview

Table of Contents Previous Next