Page tree
Skip to end of metadata
Go to start of metadata

This topic describes how to uninstall BMC TrueSight Capacity Optimization components.

Before you begin

Ensure that you are logged on to the host from which you want to uninstall BMC TrueSight Capacity Optimization as the BMC TrueSight Capacity Optimization system user.

To uninstall the BMC TrueSight Capacity Optimization, you must remove the database users and tablespaces, and uninstall the server and database schema.

Removing database users and tablespaces

You must be an Oracle database administrator.

You must have a BMC TrueSight Capacity Optimization database schema installed by the BMC TrueSight Capacity Optimization installation program.

You can manually uninstall the BMC TrueSight Capacity Optimization database users and tablespaces when the BMC TrueSight Capacity Optimization database schema was installed.

This procedure can not be used if:

In either of these cases, to manually uninstall the BMC TrueSight Capacity Optimization database users and tablespaces, you need to create a drop.sql script and use it to clean the database.

To manually uninstall the BMC TrueSight Capacity Optimization database users and tablespaces

  1. On all BMC TrueSight Capacity Optimization hosts, verify that all BMC TrueSight Capacity Optimization services are stopped or are not running. For more information, see To start and stop BMC TrueSight Capacity Optimization.
  2. From the installation directory (for example, $CPITBASE) of the host on which the BMC TrueSight Capacity Optimization database schema was first installed, run the drop.sql script.

After you have uninstalled the BMC TrueSight Capacity Optimization database users and tablespaces, you can continue with uninstalling the server.

Uninstalling the server and database schema

Ensure that you have Removed database users and tablespaces.

To uninstall the server

  1. Change the directory: Change the directory to the location of the uninstallation files. For example, $CPITBASE/UninstallBMCBCO/.
  2. Set the DISPLAY environment: Set the DISPLAY environment to enable the Uninstaller program UI to launch:

    ScenarioCommand
    If the machine has a local graphical console: Set the DISPLAY environment variable to start the installer UI locally.
    DISPLAY=<Local IP Address>:0.0
    export DISPLAY

    If the machine does not have a local graphical console: Set the DISPLAY environment variable to export to an XServer on a different workstation.

    Note: On the other workstation, give access grants to every incoming X window. That is, if the workstation is a Linux machine, or running X over a bash shell for Windows, type the command xhost +

    DISPLAY=<WorkstationName>:0.0
    export DISPLAY
  3. Run the uninstallation: At the shell prompt, type ./uninstall.sh, and then press Enter.
    The BMC TrueSight Capacity Optimization uninstallation program opens.
  4. Welcome screen: Click Next on the Welcome screen.
  5. Select the components to uninstall: Select the components that you want to uninstall from the screen that lists the installed components.

    Note

    The database schema can also be uninstalled manually by your Oracle database administrator. However, if you select a database schema from the list, a new window will be displayed. Type the word 'ERASE' into the text box to proceed with the database uninstall.

  6. Verify the selection: From the Uninstallation Preview screen, verify the accuracy of the information, and click Uninstall.
    The installation program uninstalls BMC TrueSight Capacity Optimization.
  7. Click Done to exit the uninstaller.

    Note

    You can safely remove any files that remain in the installed location (For example, $CPITBASE) by using the rm -rf* command.

To uninstall the database schema

You must first Remove database users and tablespaces, and then run the drop.sql script located in the installation path (for instance, $CPITBASE) to uninstall the BMC TrueSight Capacity Optimization database schema.

Note

You must modify this script, if you have customized user names and tablespace names.