Data sharing and text search servers

The text search feature is fully supported in a Db2 for z/OS® data sharing Parallel Sysplex® environment.

All of the administration data is stored in Db2, so the data is available to all data sharing group members. If you use data sharing, you can run the administration stored procedures on any subsystem in the Db2 data sharing group.

You can define multiple text search servers. By defining more than one text search server, you prevent one server from becoming a single point of failure.

Each text index is assigned to a server that works with the latest copy of the text index from Db2. The administration stored procedures that contact a text search server can detect if a server is no longer available for creating, updating, and searching indexes. If a server is not available, a console message is written. You can run the SYSPROC.SYSTS_TAKEOVER stored procedure to verify that a server is not available. When a server isn't available, the SYSPROC.SYSTS_TAKEOVER stored procedure selects a different server and restores the index to that server.

If the SYSPROC.SYSTS_UPDATE stored procedure is running and detects that a server is not available, this stored procedure automatically checks for the availability of another server and restores the index to that server. The next call to the SYSPROC.SYSTS_UPDATE stored procedure will perform the index update on the new server.

You can run the SYSPROC.SYSTS_RESTORE stored procedure to copy an index to another text search server. By using this stored procedure, the original text index can be searched while the stored procedure is running (for example, if you are preparing for a planned outage of a text search server).