6.1.1 EOD Triggered Twice

Following are some of the most common EOD batch failure scenarios and steps to resolve them.

There are instances where the EOD batch job is triggered twice, and the date is updated to the NEXT_WORKING_DAY. Follow the below approach to resolve the issue.
  1. Restore the Database backup.
  2. Restart the OBSCF EOD batch job.
    The OBSCF EOD batch should run successfully.
  3. If there is no Database backup available, please follow the below steps;
    1. Update the following dates in OBSCF, CMC_TM_SYSTEM_DATES and CMC_TW_SYSTEM_DATES to the current date.
      1. PREV_WORKING_DAY = 20-MAR-23
      2. NEXT_WORKING_DAY = 22-MAR-23
      3. TODAY = 21-MAR-23
    2. Restart the following services:
      • cmc branch
      • instruments
      • finance
      • manual recon
      • auto recon
      • obscf core
    3. Create Invoice and complete Disbursements.

      Note:

      No settlement/payments are supported in this approach.
    4. Update the following dates in OBSCF, CMC_TM_SYSTEM_DATES and CMC_TW_SYSTEM_DATES to the next date.
      1. PREV_WORKING_DAY = 21-MAR-23
      2. NEXT_WORKING_DAY = 23-MAR-23
      3. TODAY = 22-MAR-23
    5. Repeat Substep b.
    6. The OBSCF EOD batch job is run successfully.
      Transactions are not allowed once you complete the previous step.

    Note:

    EOD batch job should not be executed again for the day (22-MAR-23).

    Note:

    If the EOD is triggered twice, it is necessary to verify the finance maturity, overdue status, and any additional interest accrued for a single day. The customer should be notified of the findings.