The reason you get the failure is because the legacy behavior of selecting the maximum result-set length and advancing the cursor position was considered a poor performance choice. Dialects which did not have an efficient way to avoid this were changed to no longer support such functionality, which included DB2390Dialect.

We've added a property where you could enable the old poorly performing behavior, use hibernate.legacy_limit_handler=true. This will allow the dialect to use offset behavior using the result-set advancing functionality as in Hibernate 4. However a bug was identified with this new configuration option behavior in HHH-11747 In Progress , which I have recently fixed. See HHH-11747 In Progress for more details.