Jobs end with ENDED_SKIPPED, no AH_TIMESTAMP4 record created in Database

Document ID : KB000084869
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Error Message:  N/A

There is already a Knowledge Article entry that describes how to maintain Date Records vs. old Static and Report Records, see the reference section below.

Basically, there is a bug in version 9 that causes a problem where some AH records do not have a timestamp4 in the database. (AH --> statistic table, timestamp4 --> end timestamp) and you'll find a solution to this issue in that Knowledge Article.

 

In some special cases where Jobs end with "ENDED SKIPPED" and there is no AH_TIMESTAMP4 in the AH table,  you will need to contact Automic Support to get update statements to resolve this special situation as the update statements in Article 000007161 will not.

Investigation

First, check to see if there are any special cases as described above in the Automic database by executing the following statement.
 
select AH_OTYPE, ah_status, count(*) as count from AH
where AH_TimeStamp4 is null
and AH_Idnr not in (select eh_ah_idnr from EH)
and (AH_STATUS >= 1800 or AH_STATUS is null)
group by AH_OTYPE, ah_status
order by 3 desc
 
If something is returned you will need to contact Automic support to get the update statements you will need to resolve the issue.

Reference
 
Resolution:
In some special cases where Jobs end with "ENDED_SKIPPED" and no AH_TIMESTAMP4 in the AH table, contact Automic Support and reference this knowledge article to get the update statements you will need to resolve this particular issue.