The SYNC_TABLE_IN_DOC procedure synchronizes the source table (IN_DOC) and the destination table (NEW_DOC) by propagating changed data that is recorded and staged in the SYNC_STAGE_DOC table.
For every row modified (INSERT, UPDATE, DELETE) in the source table (IN_DOC) the SYNC_TRG_DOC trigger will insert a row into the staging table to stage it for synchronization by the SYNC_TABLE_IN_DOC procedure.
During the execution of the SYNC_TABLE_IN_DOC procedure, staged rows are processed in batches according to the BATCH_SIZE parameter and ordered by the STAGE_ID to promote a first in first out process. After a batch of rows has been successfully committed, the respective rows are deleted from the staging table. If all staged rows have been successfully processed the SYNC_STAGE_DOC table will be empty.
Use the SYNC_GET_STATUS procedure to get a detailed report on the current state, and history, and performance of previous executions of the SYNC_TABLE_IN_DOC procedure.
The SYNC_TABLE_IN_DOC procedure accepts the MAX_MINUTES parameter to limit the amount of work that is completed per execution of the procedure. Using a smaller value for MAX_MINUTES can help to keep a synchronization event limited to a shorter timeframe per execution of the procedure.
- If document creation volumes are high, the SYNC_STAGE_DOC staging table will grow as rows are staged for synchronization. Be sure to execute the SYNC_TABLE_IN_DOC procedure periodically to synchronize the new IN_DOC table (NEW_DOC) with the current IN_DOC table.
- You can schedule this procedure or manually execute it as needed to synchronize rows between the source and destination tables at any point after setup and creation of the destination table and primary key index and prior to the execution of the downtime steps.