DB2 10.5 for Linux, UNIX, and Windows

Upgrading DB2 Text Search for non-root installation (Linux and UNIX)

If you are upgrading DB2® Text Search Version 10.5, you must upgrade the DB2 server, instance, and all databases.

Before you begin

Complete the following tasks before you begin to upgrade your text search server:

Enable the root-based features for your user ID. You might have to ask a system administrator with root access to issue the db2rfe command.
Log in as the instance owner or as a user with SYSADM authority. Then stop the DB2 instance and the DB2 Text Search instance service.
Back up the old DB2 copy into a <backup-dir> directory.
If you enabled DB2 Text Search for rich text document support, disable rich text document support. For more information about how to disable rich text document support, see disabling DB2 Text Search for rich text document support.
Log on to the DB2 server as a non-root user. Review the database instance type to ensure it can be upgraded as a non-root installation.

Procedure

To upgrade DB2 Text Search:

Install a new DB2 Version 10.5 copy with the db2nrupgrade upgrade command. Select the DB2 Text Search component that you want to upgrade. If you specified the -f nobackup parameter and the DB2 database product installation failed, you must manually install the DB2 database product by selecting the DB2 Text search component from the feature tree and then upgrade the non-root instance by issuing the following command:
```
db2nrupgrade -b <backup-dir> -j "TEXT_SEARCH"
```
<backup-dir> specifies the directory where the configuration files from the old DB2 version are stored. For details about the upgrade non-root instance command, see db2nrupgrade command.
Back up values for all configurable properties of DB2 Text Search that is used in the previous release before the database upgrade by running the following script:
```
$INSTHOME/sqllib/db2tss/bin/bkuptscfg.sh
```
The backed-up configurable properties are redirected into the $INSTHOME/sqllib/db2tss/config/db2tssrvupg.cfg property file.
Upgrade the existing databases by issuing the UPGRADE DATABASE command.
For each upgraded database, verify whether the text search properties information in the text search catalog table SYSIBMTS.SYSTSSERVERS is correct by comparing the information with the property values from step 6. If the value of token or port number in the catalog table is empty or incorrect, you must update the text server information manually. For more information about the upgrading non-root instance, see updating DB2 Text Search server information.
Upgrade the DB2 Text Search server for your instances by issuing the configTool upgradeInstance command.
- For Linux and UNIX operating systems:
```
     $DB2DIR/db2tss/bin/configTool upgradeConfigFolder  
         -sourceConfigFolder $DB2DIR/cfg/db2tss/config
         -targetConfigFolder $INSTHOME/sqllib/db2tss/config
```
  INSTHOME is the instance home directory and DB2DIR is the location of the newly installed V10.5 copy.
Compare the values that you backed up in step 6 with the values for all the DB2 Text search configurable properties to ensure that all the values are correct. Issue the following command to check the configuration values:
```
configTool printAll -configPath configuration-directory
```
If you disabled DB2 Text Search for rich text document support, you must install the DB2 V10.5 Accessories Suite. For information about the Accessories Suite, see installing DB2 Accessories Suite for DB2 Text Search.
Then enable rich text document support. For more information about enabling support, see enabling DB2 Text Search for rich text and proprietary format support.
Verify that the upgrade was successful by starting the DB2 Text Search instance service. If you disabled rich text document support, verify that rich text document support is enabled by issuing text search queries and compare with pre-upgrade results.