Defines the database batch size to be used during the migration process. The best size depends on the database configuration. Defines how many concurrent threads to use during the migration process. Set to the number of processors available. If the existing Oracle backing store contains a large amount of data, the migration process can take many hours to complete. If this is the case, you can shorten the process using this property.When this property is set to false, the migration process ignores the data contained in OBJECTTABLE table. Skipping this table can shorten the migration time considerably.If you skip migration of the OBJECTTABLE table, you must then copy this table from the Oracle to the JDBC backing store database using other tools (or simple SQL scripts). jdbc: The JDBC backing store schema. Use this value for migrating from an Oracle backing store to a JDBC backing store (the procedure documented in this section).oracle: The Oracle-only backing store schema. The migration utility can also be used to copy data from an Oracle backing store to another Oracle backing store. This is generally done to migrate data from an older to a newer implementation of the Oracle backing store.If you set this property to oracle, then you must create a new Oracle-only backing store in Task A, and you must define the migration TRA file properties as appropriate, for example:be.oracle.dburi.1= newConnectionURI (as in Task C).
Copyright © TIBCO Software Inc. All Rights Reserved.