ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

C_PERIOD fails if the last day of the month - can cause outage


Article ID: 210389


Updated On:


CA Automic Workload Automation - Automation Engine CA Automic Workload Automation - Automation Engine


The Jobs or Workflows running as recurring (C_PERIOD) can fail on last day of the month with FAULT_OTHER and stop executing.  This may also cause an outage on the last day of the month or first day of the month due to long running time critical calls and a system loop.

This happens when the following conditions are met:

  • The C_PERIOD is scheduled to skip certain days of the week (for instance Sundays or Saturdays and Sundays)
  • One of the skipped day is the last days of the month 

Sometimes, the last Report will end on the before last day of the month with the following error: U01001200 Invalid input timestamp

It is possible variants of this scenario with from and to times going across midnight without any skipped days can also cause a system loop.  When this happens the following may be seen:

There will be very long running time critical database calls on statement:
select * from eh where eh_ah_idnr = ?

Sometimes this is accompanied by a message from Oracle:
U00003592 UCUDB - Status: '' Native error: '1555' Msg: 'ORA-01555: snapshot too old: rollback segment number 1 with name "snapshot_name" too small'
as well as locking on the db

When the blocking session is killed the system appears to recover


Improper calculation of date/time within the Automation Engine


Release : 12.2 & 12.3




Update to a fix version listed below or a newer version if available.

Fix version:

Component(s): Automation Engine

Automation.Engine 12.3.5 HF4 - available

Automation.Engine 12.3.6 - available

Automation.Engine 12.2.10+HF.2 - available