search cancel

iDash Reports do not produce data for some applications

book

Article ID: 215842

calendar_today

Updated On:

Products

iDash Workload Automation

Issue/Introduction

We Have identically defined reports with only the application HLQs being different. At times, data for some HLQs are not produced. When i remove the HLQ from one report, and add it to the other, it works. 

 

Environment

Release : 12.1

Component : CA WORKLOAD AUTOMATION iDASH FOR CA 7

Resolution

1) Split the Autosys Job Run Report into multiple sub-reports
2) Increase the idash.server.maximum.report.rows limit to a number higher than what their largest report should return; With this approach, there could potentially be performance and resource problems especially when the reports are run from the iDash UI

Note: The below log message gives cumulative runs from the RunAggregator rather than per Instance, which is misleading.


As you can see from the log messages below which are extracted from the console output in sql.txt (attached to the case), the RunAggregator in RunReport.process() truncated the rows in the run report to 1000000

RunReport:process idashdb returned 0 rows
RunReport:process autosysdb returned 0 rows for PA1
RunReport:process autosysdb returned 8543 rows for PA2
RunReport:process autosysdb returned 502236 rows for PA3
RunReport:process autosysdb returned 589854 rows for PA4
RunReport:process autosysdb returned 625000 rows for PA5
RunReport:process autosysdb returned 757546 rows for PA6
RunReport:process autosysdb returned 826303 rows for PA7
RunReport:process autosysdb returned 960556 rows for PA8
RunReport:process autosysdb returned 960556 rows for PA9
RunReport:process autosysdb returned 1000000 rows for PAA