Backing Store Data Migration Property Reference

Oracle-Only to JDBC Backing Store Data Migration
Property Notes
be.migration.batchsize
  Defines the database batch size to be used during the migration process. The best size depends on the database configuration.

Default is: 200

be.migration.workersize
  Defines how many concurrent threads to use during the migration process. Set to the number of processors available.

Default is: 10

be.migration.objecttable
  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).

Default is true.

be.migration.target.type
  Defines which type of schema to use for the new backing store. Values are:
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
: No longer valid as an option.

Default is jdbc.