Entries in the services file prevent reinstalling the DB2 Universal Database

When you uninstall DB2 Universal Database, some port entries are not deleted. If you attempt to reinstall the database, the installation fails.

This situation and the solution apply in all the following situations:

To all supported versions of DB2 Universal Database
To manual installation and configuration of DB2 Universal Database
To the IBM Verify Identity Governance installation program

The DB2 Universal Database uninstallation does not delete corresponding DB2® port entries from the system services file. The default location of the file depends on the operating system.

Microsoft Windows systems: %SystemRoot%\System32\drivers\etc\services; For example: C:\WINDOWS\system32\driver\etc

UNIX and Linux® systems: /etc/services

The following example shows the default service name entries and corresponding port values that remain in the file:

db2cdb2admin				50000/tcp
db2cdb2admini				50002/tcp

Note: If you specify a different DB2 administrator user ID during installation, the service uses the specified names. For example:

Microsoft Windows systems: db2cinstanceowner and db2cinstanceowner

UNIX and Linux, and DB2: instanceowner and DB2_instanceowner

When you try to reinstall, the services file is searched to determine whether DB2 port entries are present. If DB2 finds the port entries in the services file, the installation fails and returns the following message:

SQL5043N Support for one or more communications protocols failed to start successfully.

The core database manager functionality started successfully. This message is generated when the middleware configuration utility issues a db2start command to start the database.

Because the uninstall operation did not remove the entries, you must manually edit the services file and remove them before installing again.