Uninstalling DB2

Technote (FAQ)


Question

Uninstallation instructions for DB2 UDB Version 8 on Windows.

Answer



For further discussion on this topic, visit this developerWorks forum thread:
https://www.ibm.com/developerworks/community/forums/html/topic?id=f618b308-1373-48d3-964f-d26ce110b405



DB2 UDB Version 8 uses “Windows Installer” technologies which have significantly changed the installation and uninstallation procedures from previous releases.

Although there are four methods of uninstalling DB2 UDB Version 8 for Windows, they are not all equally desirable. The primary option of uninstalling DB2 UDB Version 8 should be the ONLY option attempted. The subsequent methods should only be attempted after the DB2 UDB Service team has been contacted, and determined that the uninstallation through the primary method has been unsuccessful.

The four uninstallation techniques are outlined in order of preference.

PRIMARY UNINSTALL OPTION

Control Panel - Add/Remove Programs
Uninstalling through the Add/Remove Programs facility of the Windows Control Panel is the preferred method for DB2 UDB Version 8 for Windows. Depending on the specific Windows platform, the DB2 product in Add/Remove Programs may have a "Remove" and/or "Change" button. Either of these options can be used for removal purposes.

At the first screen of the DB2 uninstallation process, the Next button is grayed out while Windows Installer performs various functions in the background to ensure that DB2 is prepared to be uninstalled. Once the Windows Installer is ready to proceed, the Next button will be enabled and the user can proceed.

In the event that the uninstallation fails, the user should contact the service team to receive instructions for taking an uninstallation log and trace to determine the cause of the problem.

The following Uninstall options should ONLY be attempted if the Primary Option fails.

TROUBLESHOOTING UNINSTALL OPTIONS ONLY

Running SETUP from the original source
Unfortunately, DB2 UDB Version 8 for Windows can’t always be removed by using the Control Panel’s Add/Remove Programs facility. In this situation, the first action that should be attempted is to run 'setup' from the original install source location (either CD or network drive). Remember to make sure that it is the same DB2 product (ie. ESE, ADMCL, WSE, etc.) and level (ie. GA, FP2, V82, etc.) as the DB2 product installed. Windows Installer should recognize that it is already installed, and present you with three options - Repair, Modify and Remove. Simply click the radio button REMOVE and continue, to remove product.

Another possible problem is if Windows Installer asks for the original .msi file. In this case, the original install source should be pointed to, and the .msi file should be selected from [source]\db2\Windows\[DB2 product].msi.


Using FORCE_UNINSTALL
The inability to remove DB2 can also be the result of a number of factors, such as user tampering with the system registry, DB2 UDB files, or directory structure. In this situation, the FORCE_UNINSTALL uninstallation method should be attempted to remove DB2 UDB if the methods above are unsuccessful.

This uninstallation option combines the use of the msiexec Windows Installer function with manual cleanup procedures. To carry out the uninstall using this method:
  1. Stop all DB2 Services. The DB2 Services are listed below in the References section. This step can be done through the Windows Services facility which is part of the Operating System’s Administrative Tools suite. The Administrative Tools can be found in the Windows Control Panel.
  2. From a command prompt, go to the windows Installer directory for the OS on which you have DB2 installed on (such as c:\Windows\Installer or c:\WinNT\Installer).
  3. Run the msiexec /x <product ID> FORCE_UNINSTALL=Y command. The product IDs are listed below in the References section. If this command does not complete, you must proceed to the Manual Uninstallation section below. Otherwise, continue to the next step.
  4. Environment Variable Cleanup. The DB2 Environment Variables are listed below in the References section. Go to the Control Panel, click System, click the Advanced tab and click Environment Variables. Remove all DB2 environment variables.
  5. Registry Cleanup - search your Windows registry for SQLLIB and remove any keys that are left behind.
  6. Services File Cleanup - under [Windows]\system32\drivers\etc, remove the DB2 entries.
  7. SQLLIB Cleanup - Delete the SQLLIB directory.
  8. Shortcut Cleanup - Look for the “IBM DB2” shortcut folder, in the 'All Users' profiles in the ‘Start Menu/Programs’ folder, and delete it. Then delete any DB2 links in the ‘Startup’ folder (such as “First Steps”).


Manual Uninstallation
The following procedure can be used if there is a severe problem with DB2 uninstallation caused by a Windows Installer error and the FORCE_UNINSTALL option does not help. The procedure for products other than ESE is basically the same, but the product key in the registry will be different.

When product IDs are entered in the registry they are transformed slightly. In the example below, the registry key for DB2 ESE is transformed. From {D8F53726-C7AD-11D4-9155-00203586D551} (taken from Product table at bottom of page) to 62735F8DDA7C4D111955000253685D15.

NOTE: The following procedure describes how to find the transformed key based on a product ID.

For example, the product GUID for ESE, is {D8F53726-C7AD-11D4-9155-00203586D551}, taken from the Product table below.
a) This GUID is composed of 5 segments - D8F53726-C7AD-11D4-9155-00203586D551
b) Reverse the first 3 segments individually - 62735F8D-DA7C-4D11
c) Remove all dashes - 62735F8DDA7C4D11
d) The previous step will give you the first 16 characters of the key for ESE as it is entered in the registry. So the above key becomes: 62735F8DDA7C4D111955000253685D15 in the registry. Remember, you are mostly concerned with the first 16 characters.

Steps to Manually Remove (ESE example)
  1. Stop all DB2 Services. You can do this through the Windows Services facility which is part of the Operating System’s Administrative Tools suite. The Administrative Tools can be found in the Windows Control Panel.
  2. Remove all files and directories under SQLLIB.
  3. Remove all shortcuts and folders.
  4. Remove all updates to environment variables(My Computer/Properties/Advanced/Environment Variables).
  5. Clean up the registry. The following keys need to be cleaned up:
    HKEY_LOCAL_MACHINE\Software\Classes\Installer\Features
    62735F8DDA7C4D111955000253685D15 is the key for ESE and needs to be deleted HKEY_LOCAL_MACHINE\Software\Classes\Installer\Products
    62735F8DDA7C4D111955000253685D15 is the key for ESE and needs to be deleted HKEY_LOCAL_MACHINE\Software\Classes\Installer\UpgradeCodes
    62735F8DDA7C4D111955000253685D15 is the key for ESE and needs to be deleted HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Folders
    all folder names containing sqllib should be deleted HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\UpgradeCodes
    62735F8DDA7C4D111955000253685D15 is the key for ESE and needs to be deleted HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components all components that start with 000182B are DB2 components and need to be deleted HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products
    62735F8DDA7C4D111955000253685D15 is the key for ESE and needs to be deleted HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\{D8F53726-C7AD-11D4-9155-00203586D551} needs to be deleted
    HKEY_LOCAL_MACHINE\Software\IBM\DB2 needs to be deleted HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services
    All DB2 services need to be deleted
  6. Reboot the machine.


References

DB2 Services (In general, all service names beginning with DB2):
DB2 - [Instance Name]
DB2DAS - DB2DAS00
DB2 Data Links File Manager
DB2 OLAP Server
DB2 Governor
DB2 JDBC Applet Server
DB2 License Server
DB2 Security Server
DB2 OLAP Integration Server
DB2 Remote Command Server
DB2 JDBC Applet Server - Control Center
DB2 Warehouse Agent
DB2 Warehouse Logger
DB2 Warehouse Server
DB2 Registry Reflector
DB2 Query Patroller

DB2 Environment Variables (Remove all contents of the variable value pointing to the Install directory. For example, SQLLIB... then remove if empty):
PATH
INCLUDE
LIB
DB2TEMPDIR
CLASSPATH
LOC_PATH
VWS_TEMPLATES
VWS_LOGGING
VWSPATH

Product Codes:
Product ID code
ESE {D8F53726-C7AD-11D4-9155-00203586D551}
WSE {7A28F948-4945-4BD1-ACC2-ADC081C24830}
PE {C0AA883A-72AE-495F-9601-49F2EB154E93}
WM {84AF5B86-19F9-4396-8D99-11CD91E81724}
DLM {1D16CA65-F7D9-47E5-BB26-C623A44832A3}
RCON {273F8AB8-C84B-4EE6-85E7-D7C5270A6D08}
CONEE {9C8DFB63-66DE-4299-AC6B-37D799A728A2}
CONPE {F1912044-6E08-431E-9B6D-90ED10C0B739}
ADMCL {ABD23811-AA8F-416B-9EF6-E54D62F21A49}
ADCL {68A40485-7F7F-4A91-9AB6-D67836E15CF2}
RTCL {63F6DCD6-0D5C-4A07-B27C-3AE3E809D6E0}
GSE {F6846BF9-F4B5-4BB2-946D-3926795D5749}
LSDC {DD30AEB3-4323-40D7-AB39-735A0523DEF3}
WMC {5FEA5040-22E2-4760-A88C-73DE82BE4B6E}
DOC {73D99978-A255-4150-B4FD-194ECF4B3D7C}
QP {7A8BE511-8DF3-4F22-B61A-AF0B8755E354}
CUBE {C8FEDF8F-84E8-442F-A084-0A0F6A772B52}
EXP {58169F10-CA30-4F40-8C6D-C6DA8CE47E16}
RTLITE {07C9CEE7-4529-4E60-95D3-6B6EF6AC0E81}



For further discussion on this topic, visit this developerWorks forum thread:
https://www.ibm.com/developerworks/community/forums/html/topic?id=f618b308-1373-48d3-964f-d26ce110b405

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

DB2 for Linux, UNIX and Windows

Software version:

8.2

Operating system(s):

Windows

Software edition:

All Editions

Reference #:

1104569

Modified date:

2005-02-04

Translate my page

Machine Translation

Content navigation