Text index migration

Starting with Db2® Version 9.7 Fix Pack 3 and later fix packs, Db2 Text Search and Net Search Extender text indexes can coexist within the same database. A Db2 Text Search text index can now be created on the same column for which a Net Search Extender index already exists. However, only one text index can be active for the same column, and all text indexes used in a single query must be of the same type.

Administration commands can be executed for active and inactive text indexes. This allows populating a Db2 Text Search index for a column while the existing Net Search Extender index is still actively used.

It is recommended to maintain the inactive Net Search Extender index until you are satisfied that the new text index suits your needs. If yes, the inactive Net Search Extender index can be dropped, if no, it can be reactivated together with the associated application switch.

Administrative commands for Net Search Extender are prefixed with db2text, while those for Db2 Text Search are prefixed with db2ts. The most straightforward conversion is to map the db2text commands into their corresponding db2ts equivalent, if supported. Futhermore, you can convert db2text commands into Db2 Text Search administrative procedures instead.