Removing a Data Gate instance

Delete a Data Gate instance that you no longer need, or delete an instance to create a new instance with the same name.

About this task

A removal of an instance from the Cloud Pak for Data user interface sometimes does not delete all related objects of that instance. That is, you might be unable to pair a new instance with the same route host and port to the same Db2 for z/OS subsystem or data sharing group without doing some clean-up work before.

Procedure

  1. Make sure that the Cloud Pak for Data perspective is selected. If necessary, click Perspective icon to change the perspective.
  2. On the side bar, click Instances.
    You see the Service instances page. All instances are listed in the Name column. You find a 3-dot-menu (Drop-down menu on instances table on My instances page.) to the right of each listed instance name.
  3. Locate and click the Drop-down menu on instances table on My instances page. menu of the instance that you want to remove.
  4. From the menu choices that are displayed, select Delete.
    A confirmation window is displayed:
    Figure 1. Instance-removal confirmation window
    Confirmation window that is displayed after you select the "Delete" option for an instance
  5. Click Delete.

Results

After completing the steps in the procedure, your instance should be removed entirely. However, in some situations, the removal function cannot remove all related objects. This surfaces as a problem in the following situations:
  • You want to pair a new instance with the same route host and port to the same Db2 for z/OS subsystem or data sharing group. In this case, the removal function cannot remove all related objects from the Db2 for z/OS communications database.

    Therefore, you must clean up the communications database manually. Follow Instance not fully removed for instructions.

  • You want to pair a new instance with the same route host and port, and want to use the same storage as the removed instance (existing storage).

    In this case, remove the following folders and files manually from the storage entity:

    • appliance_etc
    • clone-api
    • dwa
    • dwa-apply-container-start.log
    • scratch
    • stunnel.conf
    • stunnel.pem
    • stunnel.pem.old