Search the VMware Knowledge Base (KB)
View by Article ID

Removing a solution from VMware vRealize Operations Manager 6.x (2114441)

  • 11 Ratings
Language Editions

Symptoms

  • Data migration fails due to an incompatible solution.
  • You are able to install the solution or management pack in VMware vRealize Operations Manager UI.
  • There is no way to uninstall the solution or management pack from VMware vRealize Operations Manager UI.

Resolution

To resolve the issue, you must manually remove the solution's .pak file and references from the VMware vRealize Operations Manager.

Note: In VMware vRealize Operations Manager 6.0.x the solution name remains listed in the UI. This is the expected behavior. You must be on VMware vRealize Operations Manager 6.1 or later to remove the solution name from the UI.

VMware vRealize Operations Manager 6.0.x:
  1. Log in to vRealize Operations Manager node as  root through SSH or console. 
  2. Run this command to determine the solution .pak files:

    $VMWARE_PYTHON_BIN $ALIVE_BASE/../vmware-vcopssuite/utilities/pakManager/bin/vcopsPakManager.py --action query_pak_files

  3. Run this command to determine the Adapter name:

    cat /storage/db/pakRepoLocal/Adapter_Folder/manifest.txt

    Notes:

    • Replace  Adapter_Folder with the name of the solution noted in step 2.
    • Adapters written for vRealize Operations Manager 5.x will not have a name displayed in the manifest.txt file.  Instead, use the same name as displayed in the vRealize Operations Manager UI.

  4. Assuming the solution you want to remove is VMwarevSphere-602537588, run this command:

    $VMWARE_PYTHON_BIN $ALIVE_BASE/../vmware-vcopssuite/utilities/pakManager/bin/vcopsPakManager.py --action cleanup --remove_pak --pak VMwarevSphere-602537588

  5. Remove the solution's .pak file from the $STORAGE/db/casa/pak/dist_pak_files/ directory.
  6. Open the /storage/db/pakRepoLocal/vcopsPakManagerCommonHistory.json file using a text editor.
  7. Delete any entries related to the deleted solution from { to },.
  8. Save the file.
  9. Log in to xDB using this command:

    XDB_PASSWORD=`grep "^db.password" /usr/lib/vmware-vcops/user/conf/persistence/persistence.properties | cut -f2 -d'='`;SSL_KEYSTORE_PASSWORD=`grep sslkeystorePassword /storage/vcops/user/conf/ssl/storePass.properties | cut -f2 -d'='`;export XHIVE_OPTS="-Djavax.net.ssl.keyStore=/storage/vcops/user/conf/ssl/tcserver.keystore -Djavax.net.ssl.keyStorePassword=$SSL_KEYSTORE_PASSWORD -Djavax.net.ssl.trustStore=/storage/vcops/user/conf/ssl/tcserver.truststore";$ALIVE_BASE/xdb/bin/xdb -f xhives://localhost:1235 -u Administrator -p $XDB_PASSWORD -d alivevm

  10. Change to the /globalpersistence/SolutionNamespace directory.
  11. Remove the SolutionInfo file of the Solution you want to remove by using the rm command.

    Note: Escape any spaces using / before the space.

    For example:

    rm SolutionInfo-
    VMwarevSphere-602537588

VMware vRealize Operations Manager 6.1 or later
  1. Log in to the vRealize Operations Manager Master node as root through SSH or Console.
  2. Run this command to determine the existing solution .pak files and make note of the name of the solution you want to remove:

    $VMWARE_PYTHON_BIN $ALIVE_BASE/../vmware-vcopssuite/utilities/pakManager/bin/vcopsPakManager.py --action query_pak_files

  3. Run this command to determine the solution's internal adapter name listed in the name section:

    cat /storage/db/pakRepoLocal/Adapter_Folder/manifest.txt

    Notes:

    • Replace Adapter_Folder with the name of the solution noted in step 2.
    • Adapters written for  vRealize Operations Manager 5.x will not have a name displayed in the manifest.txt file.  Instead, use the same name as displayed in the vRealize Operations Manager UI.

  4. Change to the  /usr/lib/vmware-vcops/tools/opscli/ directory.
  5. Run the ops-cli.sh script with the uninstall option for the solution name selected in step 3:

    ./ops-cli.sh solution uninstall "adapter_name"


    Note: Replace adapter_name with the internal adapter name found in step 3.  The cluster must be online for the opscli.sh command to complete successfully.

  6. Run the cleanup script:

    $VMWARE_PYTHON_BIN $ALIVE_BASE/../vmware-vcopssuite/utilities/pakManager/bin/vcopsPakManager.py --action cleanup --remove_pak --pak "adapter_name"

    Note: Replace adapter_name with the internal adapter name found in step 3.

  7. Remove the solution's .pak file from the $STORAGE/db/casa/pak/dist_pak_files/deployment_type/ directory.

    Note: Replace deployment_type with the deployment type of vRealize Operatrions Manager.

    Example:

    NON_VA_LINUX = Linux deployment
    NON_VA_WINDOWS = Windows deployment
    VA_LINUX = vApp deployment

  8. Open the /storage/db/pakRepoLocal/vcopsPakManagerCommonHistory.json file using a text editor.
  9. Delete entries related to the deleted solution from { to },.

    Note: The solution name found in step 2 will be listed in the entries in the pak section.

  10. Save and close the file.
Notes:
  • Any solution in step 2 that shows compatible with vRealize Operations Manager 5.x  needs to be removed by performing the steps 3 to 7.
  • If there are any dashboards created using solution, you must delete the dashboards from vRealize Operations Manager UI.
  • You must log out and log in to vRealize Operations Manager UI for the changes to be reflected.

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 11 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 11 Ratings
Actions
KB: