Parameter Description DefaultqueryTimeoutSecsno.exporter.batchSizeHow long before a querytimes outControls how many rowsare exported per batch.2,000 secondsDepends on whether or not the scaleargument is specified: if scale=true not specified,batch size is 5,000. if scale=true is specified, batchsize is 10,000.no.exporter.Workers Number of export threads Depends on whether or not the scaleargument is specified: if scale=true not specified, 5no.importer.batchSizeControls how many rowsare imported per batch.if scale=true is specified, batchsize is 12.Depends on whether or not the scaleargument is specified: if scale=true not specified,batch size is 5,000. if scale=true is specified, batchsize is 10,000.no.importer.Workers Number of import threads Depends on whether or not the scaleargument is specified: if scale=true not specified, 5disablednoOfPartitionsFor troubleshooting.The export processpartitions some datatables so that instead of asingle thread exporting allrecords serially, multiplethreads export differentchunks of a table inparallel. This behavior isconfigured for selectedtables in migrate.xml<strong>with</strong> thenoOfPartitionsparameter.if scale=true is specified, batchsize is 12.See migrate.xml for default values.90
Export Process ArtifactsExported Data FilesThe export process creates a subdirectory in the staging directory (MigrationHome/exportdataby default) for each table that it exports. The export process populates this directory,which has the same name as the table — for example EAM_PLATFORM — <strong>with</strong> files that containthe data from the table. The export data for a table is is split among files based on the value ofthe batchsize parameter in hq-migrate.xml (1,000 by default), and for big tables, the valueof the noOfPartitions parameter for the table (10, by default), also in hq-migrate.xml.Hence, the export files for a table for which partitioning is not configured will contain a 1,000rows of data (except for the final file in the set).The export files for a table for which partitioning is configured, will contain data from a singlepartition of 1,000 rows. The naming convention for the export files is:TABLE_NAME_BATCH_NO._PARTITION_NO.outwhere:BATCH_NO indicates the batch sequence number. For the first export file written for atable, BATCH_NO is "0", for the next file, BATCH_NO is "1".PARTITION_NO is the partition sequence number.o Given a file for which partitioning is configured, PARTITION_NO is 0 for the firstpartition, "1", for the next. For example,EAM_MEASUREMENT_DATA_1D_0._0.out,EAM_MEASUREMENT_DATA_1D_0._1.out and so on.o Given a file for which partitioning is not configured, PARTITION_NO is always 0.For example, EAM_PLATFORM_0_0, EAM_PLATFORM_1_0.out,EAM_PLATFORM_2_0.out, and so on.Export MetadataIn addition to the data files, the export process creates file for each table it exports, namedTableName.metadata, where TableName is the name of the table, for exampleEAM_PLATFORM.metadata. The file is written to the directory that contains the export datafiles for that table, for example MigrationHome/export-data/EAM_PLATFORM.metadata.The metadata file contain the total number of exported records and the column order in whichthe data was exported; the file is not compressed and is and is human-readable.Log FilesThe export process directs its output to three targets:console — By default, the trace level is info. You can alter the level by specifying oneof these commandline arguments: -verbose or debug.o On Unix-like platforms, that output is colorized.91