EAM-55814 Data Lake Upload Setup | Tables - R5SUMUSAGE error: There is an error getting Tenant data for table R5SUMUSAGE. Check Tenant connection information. Exception Message There are more than 15001 rows with the same timestamp in table R5SUMUSAG - HxGN EAM - Version 12.0 - Hexagon

EAM-55814 Data Lake Upload Setup | Tables - R5SUMUSAGE error: There is an error getting Tenant data for table R5SUMUSAGE. Check Tenant connection information. Exception Message There are more than 15001 rows with the same timestamp in table R5SUMUSAGE

 Description 

Steps to reproduce:

1. You need sufficient data in the table R5SUMUSAGE for this error to occur.

2. Job Setup screen. Make the job PARTUSAGE active. This job runs once a day.

3. Add the R5SUMUSAGE table to a Datalake schedule and schedule to run.

4. When the Datalake schedule runs it will generate the error on the Tables tab - "There is an error getting Tenant data for table R5SUMUSAGE. An error occurred getting the Tenant Data from table R5SUMUSAGE. Check Tenant connection information. Exception Message There are more than 15001 rows with the same timestamp in table R5SUMUSAGE."

5. If the correct correctlastsaved - EAM-46693 script is applied to reseed the usg_lastsaved dates when this occurs, this will only fix the data in R5SUMUSAGE once and the original problem will occur again the next day because R5SUMUSAGE is rebuilt each day due to the PARTUSAGE job being active. This process update all the usg_lastsaved rows in this table with essentially the same date/time stamp and the error occurs again.

Actual Results: "There is an error getting Tenant data for table R5SUMUSAGE. An error occurred getting the Tenant Data from table R5SUMUSAGE. Check Tenant connection information. Exception Message There are more than 15001 rows with the same timestamp in table R5SUMUSAGE."

Expected Results: "No data in the Table data result set. Possibly we are at the latest updated timestamp"