Appendix A. Migration Options#
Migration Options affect the migration project. They can be edited by selecting the "Migration Option" menu item from the Migration menu in GUI mode. Migration Options can usually be edited right after the project is created.
The primary option is the Migration Type: either "DB to DB" or "DB to File".
- DB to DB Migration Options
- DB to File Migration Options
DB to DB Migration Options#
Object and table data of the source database to be migrated are migrated directly to the database (Altibase) to be stored.
| Name | Description |
|---|---|
| Execution Thread | Specifies the maximum number of threads to be used when executing data migration. The default value is triple of the number of logical processors in the system running the Migration Center. The suggested range of this value is from 1 to triple of the number of logical processors in the system running the Migration Center. |
| Migration Target | Specifies the targets for migration: - Object & Data: Database objects and table data - Object: Database objects only |
| Object Options | |
| Foreign Key Migration | Specifies whether or not to include foreign key constraints in migration target. This option is set to 'No' by default. |
| PSM Migration | Specifies whether or not to include PSM objects such as procedures, functions, materialized views, views, typesets, and triggers in migration target. This option is set to 'No' by default. |
| Drop Existing Objects | Specifies whether or not to recreate the database object before migration. When this option is set to 'Yes', DROP and CREATE will be executed on migration target objects in target database. When this option is set to 'No', migration will be executed without dropping the database objects. This option is set to 'No' by default. |
| Keep Partition Table | Specifies whether or not to maintain partitioned tables. When this option is set to 'Yes', partitioned tables in the the source database will be migrated as partitioned tables. In this case, additional work is required for the partitioned tables in the reconcile stage's '5. Partitioned Table Conversion'. When this option is set to 'No', target partitioned tables will be migrated as non-partitioned tables. This option is set to 'No' by default. |
| Use Double-quoted Identifier | Specifies whether or not to use double quotation marks for schema and object names. This option is set to 'No' by default. |
| Remove FORCE from View DDL | Specifies whether or not to remove 'FORCE' keyword from the statement creating a view. |
| Invisible Column Migration | Specifies whether invisible columns should be included in the table columns to be migrated. Altibase does not support the invisible column feature. Yes means that invisible columns will be converted to normal columns and included in the migration. No means that invisible columns will be excluded from the migration. The default value is No. |
| Postfix for reserved word | Specifies a user-defined word which is to be added to the database object name in the source database as a postfix when it conflicts with a reserved keyword of Altibase. The defualt value is _POC. |
| Default '' (Empty String) Not Null Column | Defines how to modify the column definition when an empty string1 is set as the default value and a NOT NULL constraint is applied - Replace Default Empty String: Setting this option to 'Yes' allows to replace the default empty string with a user-defined value. The default setting is 'No'. - Replacement Default Value: Specifies the string to be used as the new default value. This option is only enabled when Replace Default Empty String is set to 'Yes'. - Remove Not Null: Setting this option to 'Yes' removes the NOT NULL constraint from the column where the empty string is the default value. The default setting is 'No'. |
| Data Options | |
| Batch Execution | Specifies whether or not to use batch insert in JDBC for higher performance. This option is set to 'Yes' by default. |
| Batch Size | Specifies the batch size when batch insert in JDBC is used. The default value is 10,000. |
| Batch LOB type | Specifies whether or not to batch process BLOB and CLOB data types. 'Yes' means to allow batch processing. However, it should be noted that problems such as out of memory (OOM) may occur depending on the size of the LOB data. Also, an exception may be raised in TimesTen, which does not support the batch processing for LOB data types.'No' does not allow batch processing. This option is set to 'No' by default. |
| Log Insert-failed Data | Specifies whether or not to log insert-failed rows during data migration. This option is available only when the Batch Execution option is disabled. This option is set to 'No' by default. |
| File Encoding | Specifies the encoding character set to be used when logging the insert-failed data into files. This option is available only when the Log Insert-failed Data option is enabled. The default value is UTF8. |
| Convert Oversized String VARCHAR To CLOB | When a column's data type is mapped to the Altibase VARCHAR type, and its size exceeds 32,000 bytes — the maximum size supported by Altibase VARCHAR — it is specified whether the data type should be converted to CLOB. Yes means the data type is converted to CLOB and processed accordingly. No means the data type is converted to VARCHAR with a column size of 32,000 and processed as such. The default setting is Yes. |
| Replace Empty String Data | Specifies how to replace empty string data encountered during data migration with a user-defined string. - Replace Empty Strings in Not Null: Setting this option to 'Yes' allows to replace empty string data with a user-defined string. The default setting is 'No'. - Replacement String: Specifies the string that will replace the empty string. This option is only enabled when Replace Empty Strings in Not Null is set to 'Yes'. - Apply to Nullable Columns: Setting this option to 'Yes' allows to replace empty string data in columns without a NOT NULL constraint with the value specified in Replacement String. The default setting is 'No'. |
| Data Validation Options | |
| Operation | Specifies the operation to be executed in the data validation stage: - DIFF: Check data difference between the source and the target databases. - FILESYNC: Apply the CSV file created as a result of DIFF operation to the target database. |
| Write to CSV | Specifies whether or not to write the inconsistent data to the CSV file. |
| Include LOB | Specifies whether or not to include LOB data when writing inconsistent data to the CSV file. |
| Data Sampling | Specifies whether or not to use data sampling feature. When this option is set to 'Yes', to decrease the data validation time, only sample data will be validated. When this option is set to 'No', each data will be validated. This option is set to 'Yes' by default. |
| Percent Sampling (exact counting) | Specifies the percentage of data to be sampled from target tables. This option is used only when the Exact Counting Method is selected in the build stage. |
| Record Count Sampling (approximate counting) | Specifies the number of records to be sampled from target tables. This option is used only if the Approximate Counting Method is selected in the build stage. |
DB to File Migration Options#
Object and table data of the source database to be migrated are stored as SQL script file, form file, and CSV type data file, respectively.
The stored files can be migrated to the database (Altibase) to be saved using iSQL and iLoader.
| Name | Description |
|---|---|
| Execution Thread | Specifies the maximum number of multi thread to be used when executing data migration. Default value is triple of the amount logical processors in the system running the Migration Center. The suggested range of this value is from 1 to triple of the amount logical processors in the system running the Migration Center. |
| Migration Target | Specifies the targets for data migration: - Object & Data: Database objects and table data - Object: Database objects only |
| Object Options | |
| Foreign Key Migration | Specifies whether or not to include foreign key constraints in migration target. This option is set to 'No' by default. |
| PSM Migration | Specifies whether or not to include PSM objects such as procedures, functions, materialized views, views, typesets, and triggers. This option is set to 'Yes' by default. |
| Keep Partition Table | Specifies whether or not to maintain partitioned tables. When this option is set to 'Yes', partitioned tables in the the source database will be migrated as partitioned tables. In this case, additional work is required for the partitioned tables in the reconcile stage's '5. Partitioned Table Conversion'. When this option is set to 'No', target partitioned tables will be migrated as non-partitioned tables. This option is set to 'No' by default. |
| Use Double-quoted Identifier | Specifies whether or not to use double quotation marks for schema and object names. This option is set to 'No' by default. |
| Default '' (Empty String) Not Null Column | Defines how to modify the column definition when an empty string is set as the default value and a NOT NULL constraint is applied - Replace Default Empty String: Setting this option to 'Yes' allows to replace the default empty string with a user-defined value. The default setting is 'No'. - Replacement Default Value: Specifies the string to be used as the new default value. This option is only enabled when Replace Default Empty String is set to 'Yes'. - Remove Not Null: Setting this option to 'Yes' removes the NOT NULL constraint from the column where the empty string is the default value. The default setting is 'No'. |
| Data Files | |
| File Encoding | Specifies the encoding character set to be used for scripts and data files. |
-
A string of length zero ↩