Installing and configuring Db2 Text Search

Db2 Text Search is an optionally installable component whose installation and configuration are fully integrated with the installation of all Db2 database server products. The stand-alone server deployment is the preferred option for using Db2 Text Search.

You can have the Db2 installer automatically install and configure Db2 Text Search. The steps that you must take are platform dependent. Figure 1 describes the installation and configuration process on Windows operating systems, and Figure 2 describes the process on Linux® and UNIX operating systems.

Figure 1. Installation and configuration on Windows platforms
Flow chart describing the installation and configuration steps in a Windows environment.
On Windows, choose the installation type, decide whether to configure, and choose the configuration method.
Figure 2. Installation and configuration on Linux and UNIX platforms
Flow chart describing the installation and configuration steps for Linux and UNIX environments
On Linux and UNIX, choose the installation method and type, decide whether to configure, and choose the configuration method. If you run db2setup as a non-root user, have your system administrator (who has SYSADM authority) run the DB2RFE command afterwards to reserve the port number that you want in the services file.
Figure 3. Configuration of a stand-alone Db2 Text Search server
Flow chart describing the configuration steps for a stand-alone DB2 Text Search server.
For a stand-alone Db2 Text Search server, update the integrated text search server configuration. Then update the server connection data and run the CONFIGURE procedure.
Db2 Text Search has the following restrictions:
  • You need to be on the coordinating member or instance owning partition when creating a database partitioned instance using the Db2 Setup Wizard.
  • Only stand-alone text servers are supported in a Db2 pureScale® environment.
  • Db2 Text Search is not supported on column-organized tables.
  • Db2 Text Search is supported only in the default SYSTEM tenant.