Uninstalling from Linux (disconnected scenario)

Edit online

To uninstall License Metric Tool from Linux, uninstall the server, VM Manager Tool, and the scanners. Optionally, you can also uninstall the DB2 instance if it is used only for License Metric Tool.

Procedure

Uninstall the License Metric Tool server.
1. Log in to the computer where the License Metric Tool server is installed as the user who performed the installation.
2. Go to the /opt/ibm/LMT/Uninstall directory.
3. Uninstall the server in interactive or silent mode.
  - To uninstall the server in interactive mode, run the uninstall.sh script. Follow instructions in the uninstallation wizard. When the uninstallation finishes, click Done.
  - To uninstall the server in silent mode, open the uninstall_response.txt file, and edit the uninstallation parameters. Start the command line, and run the following command.
```
uninstall.sh -f /opt/ibm/LMT/Uninstall/uninstall_response.txt -i silent
```
4. Optional: The License Metric Tool server is uninstalled but the database (including user logins and passwords) is preserved. If you do not plan to uninstall the DB2 instance, remove the License Metric Tool database. To remove it, log in as the DB2 instance owner on the computer where the database is installed, and run the following command.
```
db2 deactivate db database_name
db2 drop db database_name
```
  Where database_name is the name of the License Metric Tool database, by default TEMADB.
Uninstall the scanner.
- If you manage disconnected scans by automation technology of your choice, see: Uninstalling the disconnected scanner (disconnected scenario).
- If you manage disconnected scans with Ansible, run the lmt_uninstall_scanner playbook.
Uninstall the VM Manager Tool. If you use the local VM Manager Tool, it is automatically uninstalled together with the License Metric Tool server. If you use any other type of VM Manager Tool, follow the relevant procedure. For more information, see: Uninstalling the VM Manager Tool.
Optional: Uninstall the DB2 instance. For more information, see the DB2 documentation.