Uninstalling Db2 Connect (Windows)
This task provides steps for completely removing your Db2® database product from your Windows operating system. Only perform this task if you no longer require your existing Db2 instances and databases.
About this task
If you are uninstalling the default Db2 copy, and you have other Db2 copies on your system, use the db2swtch command to choose a new default copy before you proceed with the uninstallation. Also, if your Db2 Administration Server (DAS) is running under the copy being removed, move your DAS to a copy that is not being removed. Otherwise, re-create the DAS using the db2admin create command after the uninstall, and you reconfigure the DAS for some function to work.
Procedure
To remove your Db2 database product from Windows:
What to do next
Unfortunately, your Db2 database product cannot always be removed by using the facility or using the db2unins /p command or the db2unins /u command. The following uninstallation option must ONLY be attempted if the previous method fails.
To forcefully remove all Db2 copies from your Windows system, run the db2unins /f command. This command will perform a brute force uninstallation of ALL Db2 copies on the system. Everything except user data, such as Db2 databases, will be forcefully deleted. Before running this command with the /f parameter, see the db2unins command for details.
If you did not successfully remove the Microsoft Cluster Service Instance, entries are left behind in the registry. These entries can prevent successful reinstallation of Db2, or switching between ESE and WSE. You can edit the registry to manually remove these entries. Using the regedit tool, remove the Db2 entries from the following locations:
- HKEY_LOCAL_MACHINE\Cluster\
- HKEY_LOCAL_MACHINE\SOFTWARE\IBM\DB2\
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\