Removing a virtualized object in Watson Query

Important: IBM Cloud Pak® for Data Version 4.7 will reach end of support (EOS) on 31 July, 2025. For more information, see the Discontinuance of service announcement for IBM Cloud Pak for Data Version 4.X.

Upgrade to IBM Software Hub Version 5.1 before IBM Cloud Pak for Data Version 4.7 reaches end of support. For more information, see Upgrading IBM Software Hub in the IBM Software Hub Version 5.1 documentation.

You can remove a virtualized object that uses any of the supported data sources.

About this task

When you remove a virtualized object, it is permanently removed from your Virtualized data. However, if the virtualized object was published to catalogs or added to projects in Watson Knowledge Catalog, Watson Query doesn’t remove it from the catalogs or the projects.

Procedure

  1. On the navigation menu, click Data > Data virtualization.
    The service menu opens to the Data sources page by default.
  2. On the service menu, click Virtualization > Virtualized data.
    The list of virtualized objects appears. You can narrow down the displayed objects by using the available filters. Additionally, you can search objects by name, schema, column, or business term.
  3. In the overflow menu (Overflow menu icon), click Remove.
    Tip: If the overflow menu is not visible, clear any selections and hover over the end of the row of the virtualized object.
  4. On the Remove virtual object dialog box, click Remove.
    Important: When you remove a virtualized object that was published to a catalog, Watson Query doesn’t remove it from the catalog. The data assets that represent the removed virtualized object remain in catalogs and projects. You can find the data assets by searching for the object name in the global search.
  5. Verify that the object was removed successfully.
    • If you see an error message that is similar to The customers table cannot be removed: The statement references an object that identifies an unexpected object type, check the connection to this data source. If the connection to the data source was deleted before the virtual object was removed, you must drop the table by using the SQL editor or by navigating to Data > Tables in the service menu.
    • If you see an error message that is similar to The statement failed because a Big SQL component encountered an error. Component receiving the error: "DDL". Component returning the error: "HIVE". Log entry identifier: "[BSL-0-1be1bf7a]". Reason: "Unable to load credentials from envir".. SQLCODE=-5105, SQLSTATE=58040, DRIVER=4.29.24, and the virtual object was defined in cloud object storage, you must readd the connection before you can remove the virtual object. See Credential error message when you remove a virtualized table in object storage.