Disconnecting Db2 from watsonx.data

It is possible to disconnect Db2 from watsonx.data by unregistering the watsonx.data metastore from Db2 and deleting the access storage alias or aliases used by Db2 to connect to the watsonx.data object storage container.

Unregistering the watsonx.data metastore

To unregister the watsonx.data metastore in Db2, run the following command:
CALL UNREGISTER_EXT_METASTORE('metastore-name', ?, ?)
with the following parameters:
metastore-name
The name under which the metastore was registered.
After the metastore has been unregistered, the watsonx.data metastore is not accessible and the following actions fail:
  • Running the EXTERNAL_CATALOG_SYNC() stored procedure to import tables or refresh their schema.
  • Issuing a SELECT or INSERT statement from Db2 on an Iceberg table created in watsonx.data.
Important: Due to the nature of non-Iceberg Datalake tables, issuing a SELECT or INSERT statement against them continues to be successful. However, SELECT or INSERT statements will not be successful when the access to the underlying storage is revoked after deleting the access storage alias used to connect to the watsonx.data object storage container.

Deleting the access storage alias

To completely disconnect watsonx.data from Db2, you must also delete the access storage alias used to connect to the watsonx.data object storage container.

To delete the storage access alias, see Deleting the storage alias.