Removing IBM Big SQL

When you remove a working Big SQL installation, make sure there are no remaining files so as not to cause problems for future installations.

About this task

This clean-up process does not remove the Ambari server, nor does it impact any of the Hortonworks Data Platform (HDP) configurations. The script will remove the top-level Big SQL RPMs.

If you encounter a problem during Big SQL installation, you can use the IBM® Big SQL clean-up utility to help you restore the cluster environment. See Clean-up utility for details.

Note: In the Ambari UI, when you click the IBM Big SQL service, the last action listed under Service Actions is Delete Service. In our current implementation, this Ambari-provided Delete Service action is not complete in removing Big SQL from the cluster, and can leave the service in a inconsistent state. The proper way to remove this service is to follow the steps on this page.  If you already used the Delete Service option for Big SQL, you will still need to follow the steps on this page for proper removal of the service. In such a scenario, you will see a message like the following during removal. You must type in y or Y to finish the removal successfully.
Current BIG SQL status: EMPTY
Unable to detect BIGSQL in Ambari. It may have already been removed.
Would you like to continue cleanup? (Y/n) y

Procedure

  1. In the Ambari UI, in the Big SQL service, click the Service Actions menu and select the following actions.
    Important: If Big SQL high availability (HA) is enabled, do not attempt to decommission the service directly; otherwise, the secondary head node will become the primary head node and the service will not be decommissioned. You must disable Big SQL HA first.
    1. Disable HA if it is enabled.
    2. Put Big SQL in Maintenance mode.
    3. Decommission Big SQL by clicking the IBM Big SQL service, and choose the Decommission action under Service Actions.
    4. Delete the Big SQL service.
  2. If you have DSM installed, you must follow these steps before moving on to Step 3 below:
    1. In Ambari, select Services > Big SQL DSM, then select Service Actions > Turn On Maintenance Mode to put BigSQL - DSM into Maintenance mode.
    2. Run the DSM Cleanup script: 
      /var/lib/ambari-server/resources/extensions/IBM-Big_SQL/5.0.1.0/services/BIGSQL/package/scripts/dsm-cleanup.sh -u <ambari_user> -p <ambari_password> -x <ambari_port>
    3. Manually delete the dsm user by typing the following command:
      userdel dsmuser
    4. Delete the BigSQL - DSM service from the UI.
  3. On the Ambari server node, execute the /var/lib/ambari-server/resources/extensions/IBM-Big_SQL/5.0.1.0/scripts/DisableBigSQLExtension.py script.
  4. Restart the Ambari server.

Results

These steps remove the Big SQL link so that Big SQL is no longer seen as an installable service.

Note: The IBM-Big_SQL package is still installed. You must remove it before you can install a newer version of Big SQL.