Create a Simple Job for a Host Target in EM12c


The job in question, is a veridata compare job. You could just as easily, replace that job with . I’d like to show you how to set it up.


My innocent script is located in the $VERIDATA_HOME directory.

[oracle@as-sandbox-n1 scripts]$ pwd
total 4.0K
-rwxrwxrwx 1 oracle oinstall 68 Nov 8 12:43
[oracle@as-sandbox-n1 scripts]$ cat
/u01/app/oracle/product/ -j BLUE_YELLOW

A sample execution of the script looks like:

VERIDATA_HOME /u01/app/oracle/product/
JRE_HOME: /u01/app/oracle/product/
JAVA_OPTS: -Xmx1024m -Djava.awt.headless=true
Oracle GoldenGate Veridata Command Line Interface - Version OGGVDT_11.
Job BLUE_YELLOW started
Run ID: (1027,0,0)
Number of Compare Pairs: 3
Number of Compare Pairs With Errors: 3
Number of Compare Pairs With OOS: 0
Number of Compare Pairs With No OOS: 0
Number of Compare Pairs Cancelled: 0
Run ID: (1027,0,0)
Job Completion Status: IN SYNC

That was the easy part 🙂





















8. And that’s it!














  1. good post

  2. Hi Anjum,

    After reading the above article, i tried defining a job (in place of a crontab job) for multiple servers but whenever i do it, the ‘Add Target’ takes an entry for all the 4 targets as 4 different hosts and the shell script works only for the server where the script is placed.

    Can you please let me know the steps involved in defining the above requirement for 4 different targets?

    Do we have to place the Shell Script in all the different 4 targets/servers or just put the shell script in the EM12c Server to make it work for all the 4 targets.


    1. Panda,

      I just saw this comment. It all depends on the type of script you’re running. What does your script do actually?


  3. Great article . I have a very specific example where the shell script needs oracle SID as parameters as input and uses those SID to build text files which are compared later to see if something changed from last time . Please let me know if the JOBS solution allows the SIDs as input parameters so in that case I do not have to change the code (at all) or if it has to be changed then it would be minimal (like replacing $1 variable with something else).

    1. Hi Vikas,

      Thanks for the feedback. So, with jobs you can direct them to specific targets. I’m not aware of any “input” parameters you can dynamically pass to an existing script that won’t involve a reworking the script.

      Good luck!


  4. Hi Anjum,

    Is there a way to schedule the job in OEM to execute “monthly during the last weekend of the month” ?.

    Thank you,

    1. Hi Prasad,

      Well, not exactly. From what I could tell, you can only do it for the last day of the month from the direct options available – which makes the most sense. How would you know which day of the week from that month? It’s a moving target.

      Alternatively, you could schedule a “yearly” reoccurrence, and pick the day of the month you want the job to run.

      Good luck.


  5. Thanks for this post. Unfortunately the contents in the screen shots are Invisible – resolution, too small.

Leave a Reply


You are commenting using your account. Log Out /  Change )

Google photo


Twitter picture


Facebook photo


Connecting to %s


Things I see and learn!

Thoughts from James H. Lui


bdt's blog

Sharing stuff (by Bertrand Drouvot)

Frits Hoogland Weblog


Vishal desai's Oracle Blog

Just another weblog

%d bloggers like this: