ORA-20000: Could not find next rundate for fiscal
search cancel

ORA-20000: Could not find next rundate for fiscal


Article ID: 260032


Updated On:


CA Automic Applications Manager (AM)


Applications Manager's upgrade may fail with the below error:

Error messages found
 ORA-20001: Submit_chains job_seq=26213
 [ORA-20000: Could not find " next rundate for fiscal
 ORA-06512: at "AUTOMIC.AWAPI2", line 498
 ORA-06512: at "AUTOMIC.AW_TIMEZONES", line 542
 ORA-06512: at "AUTOMIC.AW_TIMEZONES", line 612
 ORA-06512: at "AUTOMIC.AW_TIMEZONES", line 1178
 ORA-06512: at "AUTOMIC.AW_TIMEZONES", line 2365
 ORA-06512: at "AUTOMIC.AW_TIMEZONES", line 2436
 ORA-06512: at "AUTOMIC.AWAPI3", line 2828
 ORA-06512: at "AUTOMIC.SCHED_MIGRATION", line 749
 ORA-06512: at "AUTOMIC.SCHED_MIGRATION", line 918
 ORA-06512: at line 20

Fatal Error occurred - check the log /u01/automic9/install/aw_install.log
   Requested processes "all" not running
   stopso done
Installation exited with errors





Release : 9.3.x, 9.4.x

Component : CA Automic Applications Manager (AM)


When selecting Yes to the upgrade prompt "Update the next rundate for all schedules [Y]?"  installation/upgrade script is attempting to calculate the next run date for all schedules. 

If a Fiscal Calendar exist on a Job AND has expired (thus NOT having any valid future rundates), the above error is seen.


The issue is currently under review for a permanent fix.

As a workaround, before running an upgrade or after seeing the error, run the below sql to see if there are any expired Fiscal Calendars attached to a Job or Process Flow:

select a.so_module, b.aw_sch_name, b.aw_sch_start,b.aw_sch_end, b.aw_active , 
max(c.aw_rundate) max_rundate,  max(c.aw_next_rundate) max_next
from so_job_table a, aw_module_sched b, aw_rundates c
a.so_job_seq=b.aw_job_seq and
b.aw_sch_units=-7 and
group by a.so_module, b.aw_sch_name, b.aw_sch_start,b.aw_sch_end, b.aw_active

If no rows are returned, the upgrade issue will not occur. If one or more rows return, start Applications Manager (should start even if upgrade failed), and remove the Fiscal Calendar schedule from the affected Jobs and/or Process Flows.

Once removed, re-run the upgrade.