Uninstall IBM Db2 Event Store Standalone/IBM Watson Studio deployment

You must use the command line to uninstall IBM® Db2® Event Store Standalone/IBM Watson® Studio deployment.

Before you begin

You must have Python 2.7 to run the uninstall command. Python 2.7 comes with the Red Hat Enterprise Linux (RHEL) 7.2 and 7.3 operating systems.

Procedure

To uninstall the Standalone/IBM Watson Studio deployment:

  1. Change to the installer files partition (or the directory where you extracted the contents of the installation package).

    The uninstall.sh file is in the same directory as the installation file, db2-event-store-enterprise-multinode-n.n.n or db2-event-store-enterprise-singlenode-n.n.n.

  2. Run the command to uninstall the multi-node installation of IBM Db2 Event Store: 
    ./uninstall.sh
    You can optionally specify the following parameters when you run uninstall.sh:
    Parameter Description
    --clean Specify this parameter to remove all IBM Db2 Event Store files.
    Note: This parameter does not remove any files from COS. You must remove those files manually.

    If you do not specify this parameter, the IBM Db2 Event Store persistent volume and the data in the persistent volume remain in your Kubernetes cluster.

    This parameter does not take any arguments.

    Important: If you specify this parameter, you must also specify the --compute-path parameter.
    --compute-path Specify this parameter to remove the files that are stored in the compute path partition.
    Important: If you specify the --clean parameter, you must also specify this parameter
    Specify this parameter with the format:
    --compute-path compute_path

    If you do not specify this parameter, the computation data remains in the compute path partition.

    Replace compute_path with the value that you specified when you installed IBM Db2 Event Store
    --uninstall-es-dsx Specify this parameter to remove both IBM Db2 Event Store and IBM Watson™ Studio.

    If you do not specify this parameter, IBM Watson Studio remains on the system.

    This parameter does not take any arguments.
    Note: When re-installing, you must use the --use-existing-db option to allow the new installation to use the preserved database.