IBM Content Navigator, Version 2.0.3         
CQL214
The results are too large for the action. The results contain too many documents of some complex document types or too many documents that are too complex. Request fewer results, use document types that are optimized for normal documents, or ask your administrator to disable the optimization that causes this error.

Explanation

The documentModelRetrieveOptimized=true compound document model optimization in cmpathservice.properties has failed due to large numbers of compound documents or parts. Compound documents are documents with an item type that is classified as document in IBM® Content Manager. When the retrieval optimization for compound documents is enabled, queries, searches, or folder browsing will fail if a large number of compound parts exist in the results. Actual numbers vary by variable data lengths, such as file names, and actual number of parts among all compound documents in the result.

For example, results can contain a maximum of 2127 compound documents with 1 part each. Results with 2128 compound documents will fail if each have at least 1 part. Results can usually support up to 89 compound documents with 30 parts each (up to 2670 parts), but will fail with any more. Documents from compound document types created through IBM Content Manager Collaboration ServicesIBM CMIS for Content Manager will have a maximum of 1 part unless modified by another IBM Content Manager application. The limitation supports the default maximum results size of 1500 for folder children and 500 for search with some room for compound documents. It is possible to have between 2128 and 2670 parts distributed among documents in the result set. But actual results vary and can be fewer than stated in this example.

The limitation is caused by the limitation of the IBM Content Manager API for the following retrieve option:
DKRetrieveOptionICM.
   behaviorPartsAttributesCoreOnly(true)
The optimization is directly limited by the stored procedure size currently configured for your IBM Content Manager library server, which is usually 320K by default. Actual stored procedure sizes can vary and can be customized. The default stored procedure size can support reasonable numbers that fit within the default settings and expectations for many applications.

User response

Request fewer results. If the application allows you to change the number of results requested such as the page size in a web based application, select a smaller number for this particular operation.

Use document types that are optimized for normal documents with a single binary. Do not use documents that are classified for compound documents. By reducing the number of compound document instances, you reduce the possibility of returning too many in any result set.

You can also ask your administrator to disable the optimization that causes this error.

Administrator response

Either accept the limitation and keep the optimization enabled, or turn off the optimization. You can disable the optimization by changing the configuration setting in cmpathservice.properties to documentModelRetrieveOptimized=false.

For documents, use item types classified as “resource” which are optimized for normal documents with a single binary.

If this error occurs when the maximum number or all results are requested, you can change the configuration settings for maximum number of folder children or search results per call.

It is not recommended that you change the stored procedure size to work around this error.

Parent topic: CQL messages for IBM CMIS applications