Configuring Tables for Late Commit Changes

The system has to check and correct for late commit changes. You must configure the files it uses to achieve this.

The job process validation in Relational Replication counts the records in F.DATA.EVENTS and the Relational Replication staging table. It compares these two values. If there is a mismatch, it identifies any missing records, retrieves them from the Temenos Transact DATA.EVENTS table, processes them and loads them into Relational Replication.

Procedure

1. In the release pack, retrieve the SQL scripts from location https://docs.temenos.com/docs/Solutions/Technology/Data_Framework/RR/Relational_Replication/r-config-properties-data.htm.

2. For validation job process, additional configuration parameters are used by ETL and Purge application to process missing events. Enter the following parameters into the TMN_DF_CONF_EXTRACT table.

   Parameter	Value	Description
   df.rr.etl.validate.job.schedule.frequency	5000	The time (in milliseconds) between EJB thread invocation and another.
   df.rr.etl.validate.job.time.delay	900	After a job has finished, a delay (in milliseconds) is introduced to allow time for the validation process to start.
   df.rr.etl.validate.job.timeout	1800	The timeout for a validate job process (in seconds).
   df.rr.etl.validate.job.enable	Y	This determines whether to enable or disable the job validation process. If set to Y, it is enabled. If set to N, it is disabled.

3. Enter the following parameter into table RR_PURGE_DATA_CONFIG.

   Parameter	Value	Description
   df.rr.purge.validate.job.enable	Y	Enables or disables the job validation process.

4. Run the configuration scripts on path RelationalReplicationXXX.zip/database_schema/oracle/4_RR_CONFIG_TABLE_SCRIPTS.sql to create table RR_LOCK_VALIDATE_JOB_LOCK. This table helps to manage multiple purge instances.