AAI error when adding a CA7 Scheduler while pre loading historical data: WARN [AbstractRunUpdateBuilder] The maximum number of allowed jobRuns per transaction has been violated. Number of maximum runs allowed: 75,000,

Products

• Automation Analytics & Intelligence

Issue/Introduction

When adding a new CA7 scheduler and pre loading several months of historical events, the scheduler takes many hours to be added, the error below is seen, and no historical data is seen in AAI:

WARN [AbstractRunUpdateBuilder] The maximum number of allowed jobRuns per transaction has been violated. Number of maximum runs allowed: 75,000, Number trying to be processed: 75,001,  JobRun that caused the number of runs to be proccessed to exceed this value: jobName [<jobName>]

 

Why does this error occur and how can it be prevented?

Cause

There is a 75,000 job run limit per database transaction, once that limit is hit, the error will occur and all data prior to that error will be discarded,

 

 

Resolution

The error is a cumulative job run limit for all job runs being loaded at that time.

There are two parameters that could be increased potentially:

• maxRowsPerTransaction: Default 50,000
• maxRowsPerTransactionMultiplier: Default 1.5

The first number is multiplied by the second number to get the total job runs to get the total allowed.

To get around this, the better approach would be to pre load only a small number events from CA7 when adding the scheduler.

This will allow the CA7 scheduler to be added much quicker and prevent hitting the error above.

Once the scheduler is added, make sure the CA7 Data Provider is not sending new data, and pre load smaller batches of historical data.

You can test with a few days or weeks at a time and let AAI process the RPT70 files that are sent to AAI.

Once all historical data is loaded, you can switch the CA7 Data Provider to send live data.