Removing a virtualized object in Data Virtualization

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

1. On the navigation menu, click Data > Data virtualization to reveal the service menu.
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 (), 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, Data Virtualization 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 re-add the connection before you can remove the virtual object.

     The error message indicates that when Data Virtualization performs a DROP TABLE statement for a virtualized table in object storage, the underlying Hive system must have access to the credentials. However, if the connection to the data source was removed, the credentials are not available, and the DROP fails. Virtualized tables in object storage must be removed before you remove the associated connection to the data source in object storage. If the connection was removed, re-enable the connection, remove all the associated tables, and then remove the connection.