The following is an example of the prosync configuration file fragment in the YAML format that lists prosync-specific configuration parameters:
prosync_options:
export_batch_size: 10000000
max_export_batch_size: 100000000
process_batch_size: 10000
batch_save_after_timeout: 5m0s
import_batch_size: 1000000
start_scn: 0
prefetch_rows: 250
use_online_logs_unsafe: false
validate_log_sequence: true
lob_write_size: 30000
operation_count_for_external_storage: 5000
For how to set values for time configuration parameters, refer to Section 4.3.6.
Table 5.3. prosync Configuration Parameters
| Name | Description | Default Value | Example |
|---|---|---|---|
prosync_options | prosync-specific parameters | ||
prosync_options.export_batch_size | Batch size for prosync reading from Oracle LogMiner | ||
prosync_options.max_export_batch_size | Maximum size to which the batch size can be increased when reading. If the maximum size is reached, prosync terminates with an error. This can happen if there is an open transaction that would not close. The user must resolve this issue. | ||
prosync_options.process_batch_size | Batch size for processing a transaction. This parameter is for internal tuning of the application. | 10000 | |
prosync_options.batch_save_after_timeout | Time interval after which a batch will be written to the destination DB if its size is still less than max_export_batch_size. The value of zero disables time-based flush to the destination DB. | 5s | 5m |
prosync_options.import_batch_size | Batch size for inserting data. Zero value means that the data will be inserted as new data occurs. | ||
prosync_options.start_scn | System change number (SCN) to start replaying the operations | ||
prosync_options.prefetch_rows | Deprecated. Number of rows that the driver retrieves from the databases at a time. | ||
prosync_options.use_online_logs_unsafe | Read the changes from archive and online REDO LOGS. The flag enables getting the changes as soon as they occur in online logs. Not recommended to use for reliability. Because of how Oracle writes logs, some operations can be missed. | false | |
prosync_options.validate_log_sequence | Validate a sequence of log files. If a log file is missing, prosync terminates with an error. If losing some data is OK, set this parameter to false. | true | |
prosync_options.lob_write_size | Maximum number of bytes to write at a time when writing LOBs | ||
prosync_options.operation_count_for_external_storage | Number of operations in one transaction that causes writing of intermediate data to disk | ||
prosync_options.storage | A supporting database to be used for storing intermediate data and transactions. The destination database is used by default. |