Scheduling GoldenGate Veridata Job
Date: June 17, 2024
Author: Eric Yen
Table of Contents
Determine and confirm that the job to be schedule can be ran manually.
Confirm proper permission for the script.
Schedule the script in crontab.
Within Veridata there is a command line utility; vericom. We will use vericom, create a supporting script, and then schedule that script to run via cron. Each script will support one Veridata compare job.
In LabCorp’s Veridata environment vericom is located in the following directory:
/u01/app/oracle/fusion_mw_infra/12.2.1.4/user_projects/domains/base_domain/veridata/bin
Some background is needed at this point to explain the two steps taken by Veridata during a comparison. First, the is an initial pass to determine what is Maybe Out Of Sync (MOSS). Then a second pass is ran to Confirm Out Of Sync (COOS).
It is during the COOS phase that three possible statuses can be returned:
1. In-flight
2. In-sync
3. Persistently out of sync
An important note here is that we can schedule some delay time between the MOOS and COOS phases. By doing so this allows for time to “catch up” for any in-flight transaction to be applied.
Log into the Veridata server and move to the proper directory
cd /u01/app/oracle/fusion_mw_infra/12.2.1.4/user_projects/domains/base_domain/veridata/bin
the format to immediately run a job with vericom is
./vericom.sh -j <job name>
Find the job name using the web interface.
We will add an additional parameter to schedule some delay between the MOOS and COOS phases. The command will then look like:
./vericom.sh -j <job name> -rD <number of seconds delay before COOS starts>
Once you have confirmed that you can manually run the command copy it to a script using vi editor (or editor of your choice).
The example below would run the job Prod_LCCPPRD_LCGGAP_Link_Job with a 2 minute (120 seconds) delay between MOOS and COOS phases:
./vericom.sh -j Prod_LCCPPRD_LCGGAP_Link_Job -rD 120
chmod 775 <name of script>
./< name of script>
Schedule the script in crontab using the command
crontab -e
NOTE: Day Names 0-6 begin with Sunday.
The example below would be all on one line and would execute the script test_job1.sh at 5 pm everyday with the output going to /tmp/check1.txt
* 17 * * * /u01/app/oracle/fusion_mw_infra/12.2.1.4/user_projects/domains/base_domain/veridata/bin/test_job1.sh > /tmp/check1.txt
Log into the web interface and check the report.
Oracle® GoldenGate Administering Oracle GoldenGate Veridata 12c (12.2.1.4) F16425-06
Setting Up A GoldenGate Veridata Job To Run On A Schedule (Doc ID 966073.1)