Automic Continuous Delivery Automation

 View Only
  • 1.  RunID Turnover

    Posted Oct 13, 2017 11:12 AM
    @Automic,

    I noticed following article posted recently (10/6/2017) about this known error.

    Sporadically occurring scheduling error: some activities stuck with status "In Generating" 
    000009852  *  Known Error 
    ...
    *RunID Turnover:  The last possible sequence number has been reached and the RunID sequence starts again from the lowest possible number.
    The RunID turnover itself causes no impact on the workload processing and it’s normal for environments existing for longer period of time or processing lots of Jobs.
    ....

    Can someone provide more details on what is the "last possible sequence number" for RunID and how to lookup this information in the AE Database to determine if the system is getting close to this limit for this number?

    Thanks,

    Vlad_Navazhylau_6186


  • 2.  RunID Turnover

    Posted Oct 14, 2017 12:37 AM
    You can run:

    select * from ids

    This gives you an overview on where you are with your RunIDs.


  • 3.  RunID Turnover

    Posted Oct 16, 2017 11:36 AM
    When you display RUNID, the scripting language displays it as a 10 digit integer.

    The RunID value in the IDS table in SQLServer is datatype "int".  This datatype is 4 bytes of storage, and has a maximum positive value of 2,147,483,647.  This doesn't necessarily mean the Automic Workload Engine will support this high of a number though?  I still don't know what the upper range might be.