After rebuilding jobstream history, the Analysis tab shows "There are no runs in the database for the selected jobstream"

Products

• Automation Analytics & Intelligence

Issue/Introduction

After rebuilding jobstream history, the Analysis tab shows "There are no runs in the database for the selected jobstream"

 

The jaws.log shows the error below after the jobstream rebuild is triggered:

ERROR [HistoricalJobStreamRunBuilder] caught JawsException in retrieveAndAssociateRuns(): com.termalabs.common.JawsException: Could not retrieve historical runs.
 at com.termalabs.server.app.jobstream.run.PredecessorBasedHistoricalJobStreamRunBuilder.getRunResult(PredecessorBasedHistoricalJobStreamRunBuilder.java:261)
 at com.termalabs.server.app.jobstream.run.HistoricalJobStreamRunBuilder.retrieveAndAssociateRuns(HistoricalJobStreamRunBuilder.java:351)
 at com.termalabs.server.app.jobstream.run.HistoricalJobStreamRunBuilder.associateAlreadyJammedRuns(HistoricalJobStreamRunBuilder.java:237)
 at com.termalabs.server.app.jobstream.run.HistoricalJobStreamRunBuilder.associateHistoricalRuns(HistoricalJobStreamRunBuilder.java:209)
 at com.termalabs.server.app.jobstream.JobStreamBuilder.buildRunsAndStatistics(JobStreamBuilder.java:569)
 at com.termalabs.server.app.jobstream.JobStreamBuilder.rebuildHistory(JobStreamBuilder.java:408)
 at com.termalabs.server.app.jobstream.JobStreamBuilder.rebuildHistory(JobStreamBuilder.java:290)
 at com.termalabs.server.ejb3.JobStreamDataManagerEJB.rebuildJobStream(JobStreamDataManagerEJB.java:1460)
 ... 12 skipped
 at com.termalabs.server.ejb3.RequestScopeEJB3Interceptor.invoke(RequestScopeEJB3Interceptor.java:94)
 ... 68 skipped
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.NullPointerException
 ... 91 in common

Environment

Release : 6.4.2-2

Component : AUTOMIC AUTOMATION INTELLIGENCE INTEGRATION FOR AUTOSYS

Resolution

Defect DE534448 has been created for this.

 

As a workaround you can attempt to rebuilt the jobstream history to a closer date.