Basic Parameters for Batch Jobs

Some Oracle Loyalty batch jobs require you to set basic parameters when you schedule the job.

Let's look at those parameters and what they do.

Basic Parameter	Description
Object Type	The type of object to process. Transactions Tiers (Expired) Both (Transactions and Tiers) Points (Expired) Events Point Blocks (for Prepaid Partners)
Number of Sub Jobs	The number of parallel processes the job can spawn. Enter a multiple of 15 that's based on the number of ESS servers in the cluster. For example if you have one server, enter 15. If you have two servers, enter 30, and so on. A multiple greater than 15 may not always give optimal performance if the number of ESS servers isn't increased proportionally.
Database Fetch Size	The maximum number of objects the job can retrieve from the database in a given fetch. The fetch size depends on: Your database pod size The object type
Number of Database Fetches	The number of times the job queries the database in a given run. Ideally, you want to enter batch parameters where the number of objects to process equals the database fetch size times the number of fetches. For example, if you have 1,500,000 objects to process, and you set the database fetch size to 150,000 and the number of database fetches to 10, then the job processes all the objects (150,000 x 10 = 1,500,000). If you have 1,500,100 objects to process, then the job would result in 100 unprocessed objects. These objects would get picked up the next time the job runs.
From Date	The earliest date in a range, used in conjunction with the To Date parameter.
To Date	The latest date in a range, used in conjunction with the From Date parameter.