OmniFind Text Search Server for DB2 for i

The OmniFind Text Search Server for DB2® for i (5733-OMF) version 1.3 or higher allows customers to create a text search index over a column of a table that is protected by RCAC.

After a text search index is created, the CONTAINS and SCORE built-in SQL functions can be used to perform full text searches over the indexed column. Customers should be aware of the following considerations when creating a text search index over a column that is protected by RCAC.

• A text search server performs the task of indexing and searching documents; the indexed data is stored outside of DB2 as stream files in the integrated file system. Because the indexed data is stored outside of DB2, users that have access to the text search server could possibly reconstruct sensitive documents from the index.
• Data is exchanged with the text search server using network protocols that are not encrypted, digital certificates are not verified.
• A text search index requires that the base table contain one or more identifying columns that are a primary key, unique index, or ROWID. The identifying column is used to identify a specific row when interacting with the text search server or an administrator; the values are stored in the staging table, and may be returned from administrative procedures. When a text search index is created over a table that is protected by RCAC, the identifying column should contain a generated value, such as a ROWID or an identity column. This allows individual rows to be identified using non-sensitive information. For more information, please refer to the OmniFind Text Search Server for DB2 for i .