Question
Last activity: 5 Apr 2016 7:29 EDT
Getting The page size “10000” specified for this RDB call is invalid: either it is not a positive integer or it is larger than pyMaxRecords
Running a report in Pega 7.2, we are getting the error - The page size “10000” specified for this RDB call is invalid: either it is not a positive integer or it is larger than pyMaxRecords. pyMaxRecords is set to 500 as it was in 6.2. Maximum number of rows to retrieve is set to 10000 - as it was in 6.2. Also, I have no edit icons to try and change them - unlike 6.2 where I did. And even logged in as administrator, I have no ability to change these.
Still, I would expect the report to work as it did in 6.2 without getting that error - there are less than 300 rows being read in this report.
Has anyone run into this - either the error or not being able to edit the settings - in 7.2.
Accepted Solution
Pegasystems
IN
Looks like the behaviour changed not sure on the details yet.
That said, once you disable paging in the report, you can set the max records to a really high value (higher than the page size) and save the report. Then if you enable paging back, and save it back, it works correctly.
Rajiv:
I can only show you the trace. It happens under a Java step in a final activity - pxRetrieveReportData - and I don't see the doAction underneath. But the tracer screen shot is below. I do appreciate the response. It should be noted that this worked in 6.2 but fails in 7.2. Also, running the report without the activity invoking it works in 7.2, but the activity that we run it from is very simple and has not changed. I was asked to open an SR on this earlier today and will respond to this thread once this is resolved.
Rajiv:
I can only show you the trace. It happens under a Java step in a final activity - pxRetrieveReportData - and I don't see the doAction underneath. But the tracer screen shot is below. I do appreciate the response. It should be noted that this worked in 6.2 but fails in 7.2. Also, running the report without the activity invoking it works in 7.2, but the activity that we run it from is very simple and has not changed. I was asked to open an SR on this earlier today and will respond to this thread once this is resolved.
Pegasystems
IN
Would it be possible to share the entire tracer XML to see the primary page and the parameter page details when pxRetrieveReportData is invoked?
Pegasystems
IN
From the tracer it looks like pyMaxRecords property is not set. This is not visible if paging is enabled. One way to work around this is to disable paging, set the max records in data access table, save the report, re-enable paging and save the report again.
You might want to search Rule-Admin-System-Settings pyMaxRecords to change the global values for report definition.
I see pyMaxRecords set to 500 under Reporting Settings.
That said, I could not find it under Rule-Admin-System-Settings, but maybe that's the same thing. Also, I went back to the report to try to disable paging as you suggested. Unfortunately, I have no access to edit or do anything with the paging or the max rows - even with a private edit. And this is true logged in as administrator - both for the global report settings above or the data access settings in the report below - not sure why as we could in 6.2 - maybe this is part of the issue.
Pegasystems
IN
Yes, you need to disable paging before you can edit max records in the rule form of report definition.
This is the Rule-Admin-System-Settings that I was referring to
I did find this page but made no permanent changes here. I tried a private edit bumping everything to 10000, but it did not help. Are you saying, we would need a pyMaxPageSize set here?
What I did do was disable paging on the two reports which were giving us this issue. That fixed things. We are wondering what changed between 6.2 and 7.2. Logically, when I looked at the paging options on the report, the max data was set to 10000 - while under Report Settings, pyMaxPageSize was set to 500 - which I could see causing the error message we saw. But we did not get that in 6.2, and my team lead is asking me why we had to make the change - and if there were a better change we should have made in 7.2.
So, we are past the issue by disabling paging on the two reports, but are curious as to what changed between 6.2 and 7.2 - and whether there was a better option than disabling paging.
I appreciate all your help on this. I have asked support the same question, but if you have any ideas on this, I would appreciate them.
Accepted Solution
Pegasystems
IN
Looks like the behaviour changed not sure on the details yet.
That said, once you disable paging in the report, you can set the max records to a really high value (higher than the page size) and save the report. Then if you enable paging back, and save it back, it works correctly.
Sounds good to me - I will wait and see what support says- they were going to ask some of the developers on this. However, looking at it, I am more interested in why 6.2 worked - I would think it shouldn't have with these settings - than why 7.2 did not - as the error I got was correct per the configuration.
I will mark this thread answered - probably one response away from closing support ticket - will post any answers they might have to this thread, but I appreciate your help.