This command activates the cached table from either the DB2 user table or the persistent cache. After completion, search operations using the stored procedure are possible. See Stored procedure search function for further information.
This command is only available if the index was created with a CACHE TABLE option. See CREATE INDEX for further information.
According to the DB2 catalog views, the user ID in this command must have CONTROL privilege on the table for which the full-text index was created.
>>-ACTIVATE CACHE FOR INDEX--+------------------+--index-name---> '-index-schema-"."-' >--FOR-TEXT--+----------+--+----------------------+------------>< '-RECREATE-' '-|connection-options|-' connection-options: |--+--------------------------------------------------------------+--| '-CONNECT-TO--database-name--+-------------------------------+-' '-USER--userid--USING--password-'
You cannot issue the command if one of the following commands is running on the index:
Activation of a cached table may require its recreation from scratch, even though a persistent cache was used. This occurs if an update operation was performed whilst the persistent cache was deactivated.
The amount of memory taken to build the cache is dynamically calculated from the current number of documents and the size of the result columns. Use the PCTFREE value to increase the calculated minimal amount of memory by a factor of 100/(100-PCTFREE). The PCTFREE value is specified in the CREATE or ALTER INDEX command.
Thereby, PCTFREE describes the percentage of the allocated cache that is reserved for insert operations while the cache is activated. Note that for each ACTIVATE CACHE command, the actual memory size is re-evaluated.