Maximo Open Forum

I assume your database platform is SQL Server? If so, look at the mxe.db.sqlserverPrefetchRows system property. The IBM performance best practices recommend changing this to 200 but it causes what you're seeing here. I personally recommend leaving this at the default of 0 if you can but never setting this to anything less than your mxe.db.fetchResultStopLimit setting. If Maximo ever tries to retrieve more records than this fetch setting it will fail. For example, if you have more than 200 reports and try to generate request pages for all reports, it completely fails. There are some scenarios where Maximo ignores the fetch limit, but normally the fetch limit is enforced and Maximo will not fetch more records than the number defined in mxe.db.fetchResultStopLimit. 

0 is often the most performant option from a Maximo perspective but the prefetch setting was introduced to avoid some issues where the JDBC driver pulls too much data into memory and causes a heap dump. For example, if a user used the All Records query in WOTRACK and it brought back millions of records, that data in memory in the JDBC driver could crash the system. Some systems can't handle 0 because of that.