My Oracle Support Banner

"The result set size exceeds maximum fetch size" error while exporting the Organization XML from the Process Administrator (Doc ID 1274280.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Business Process Management Suite - Version 10.3.1 and later
Information in this document applies to any platform.
***Checked for relevance on 30-May-2012***

Symptoms

When you try to export the Organization from the Process administrator you are not able to so and you see "The result set size exceeds maximum fetch size specified in search or maximum page size defined in Directory Server." in the webconsole.log.
The complete stack trace will look something like the following:

[<D> 0611 12:52:55.909] Main (<12> http-9696-Processor45): href = http://download.oracle.com/docs/cd/E13154_01/bpm/docs65/admin_guide/index.html?t=modules/proc_adm_ref/c_Org_Participants.html
[<D> 0611 12:52:57.378] Main (<12> http-9696-Processor45): The result set size exceeds maximum fetch size specified in search or maximum page size defined in Directory Server.
[ (cont) ] Main: fuego.directory.exception.FetchSizeExceededException: The result set size exceeds maximum fetch size specified in search or maximum page size defined in Directory Server.
[ (cont) ] Main: at fuego.directory.exception.FetchSizeExceededException.createWithList(FetchSizeExceededException.java:54)
[ (cont) ] Main: at fuego.directory.provider.jdbc.JDBCUtils.createObjectsFromResultSet(JDBCUtils.java:102)
[ (cont) ] Main: at fuego.directory.provider.jdbc.HumanParticipantAdaptor.createAllFrom(HumanParticipantAdaptor.java:43)
[ (cont) ] Main: at fuego.directory.provider.jdbc.JDBCPersistenceManager.fetchAll(JDBCPersistenceManager.java:331)
[ (cont) ] Main: at fuego.directory.provider.jdbc.JDBCPersistenceManager.fetchAll(JDBCPersistenceManager.java:302)
[ (cont) ] Main: at fuego.directory.provider.jdbc.JDBCParticipantsAccessor.fetchAllByFilter(JDBCParticipantsAccessor.java:449)
[ (cont) ] Main: at fuego.directory.provider.jdbc.JDBCParticipantsAccessor.fetchAllMinimalByFilter(JDBCParticipantsAccessor.java:465)
[ (cont) ] Main: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[ (cont) ] Main: at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
[ (cont) ] Main: at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
[ (cont) ] Main: at java.lang.reflect.Method.invoke(Unknown Source)
[ (cont) ] Main: at fuego.directory.provider.DirectorySessionImpl$AccessorProxy.invoke(DirectorySessionImpl.java:756)
[ (cont) ] Main: at $Proxy8.fetchAllMinimalByFilter(Unknown Source)
[ (cont) ] Main: at fuego.directory.DirHumanParticipant.fetchAllMinimalByFilter(DirHumanParticipant.java:743)
[ (cont) ] Main: at fuego.mami.NOrganizationManager.getParticipantsMinimalByFilter(NOrganizationManager.java:2365)
[ (cont) ] Main: at fuego.webconsole.model.ParticipantFilteredHandler.getPresentables(ParticipantFilteredHandler.java:141)
...

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.