IBM Content Navigator, Version 2.0.3         

CQL178
The total size of the property values of {1}, with name {0} and document type {2}, exceeds the global text search feature capacity to index properties. The global text search feature cannot index {1} with name {0}. Reduce the total size of the property values for {0} so that it is within the property values size limit of {4} bytes for the global text search feature to index properties. The recommended total size of metadata values should be 100 KB or less and 32 KB for best performance. If a larger metadata size limit is required, ask your system administrator to configure the global text search feature metadata size limit or disable the global text search to skip indexing this item. If you disable global text search, you cannot find this item later by using global text search.

Explanation

The total size of the metadata property values that is supported by the search feature is currently defined with the limit that is specified in the error message out of a maximum possible configuration setting, which includes additional formatting for the global text search index. You might have properties with very large string values and properties that are defined at CLOB attribute types in the repository.

User response

Reduce the size of the property values until the combined size fits in the search feature capacity. The total size of the metadata property values is currently defined at the limit that is specified in the error message out of a maximum possible configuration setting, which includes additional formatting for the global text search index. If a larger metadata size limit is required, ask your system administrator to configure the global text search feature metadata size limit or disable the global text search to skip indexing this item. If you disable global text search, you cannot find this item later by using global text search. Use metadata values with a total size of 100 KB or less and 32 KB for best performance.

Administrator response

Disable the global text search feature so that documents do not get indexed. If the feature is turned off, documents that are created or updated when the global text search feature is disabled will not be able to be searched with global text search, based on the recent changes or additions. Increase the total size limit if the current global text search metadata capacity is configured to less than the maximum possible size of 5 MB.

The total size is based on bytes that are used for serialized property values and not just string lengths. Strings use one to four bytes per character depending on the code page. The actual values that are used affect this limitation, not the defined maximum sizes of individual attributes. Some features impose a slightly reduced capacity that are due to space that is used by the feature, such as drafts and search indexing. This means that the property might have string attributes with very large values, such as CLOB attributes.

Redefine the metadata capacity if the metadata capacity model is limited to 100 KB from the Version 1.0 release.

To define the metadata capacity again:

  1. Create and use a tool to save a list of the IDs for all items in the ClbTextIx item type.
  2. Delete all items in the ClbTextIx item type.
  3. Delete the ClbTextIx item type definition.
  4. Delete the clbTextToIndex attribute definition.
  5. Run the PathModelCreate tool with search enabled to create the attribute definition and global search index item type definition again with the new larger capacity.
  6. Create and use a tool to update all of the items through the services supporting search that were previously indexed. These items are on the list that you saved as described in step 1. When you update the items, the items will be re-indexed.
Important: If you do not save a list of the previously indexed items and force a new index to be created for each, the items will not be found by search until they are updated again to force an index to be created.
Attention: Back up the repository, test the tools and migration process, and be able to restore the system if there are any problems before deleting any index data or item types. You might not need to change the capacity if the current metadata capacity value is optimal for their environment.