Resolving Schema Inconsistencies

You can check for schema changes between installed data products and their catalog versions and then resolve the discrepancies.

Prerequisites

To run the schema inconsistency check and resolve inconsistencies, you must have:
  • A global role that grants you the following privileges:

    • Data Warehouse General (-R------) - To access SAP Datasphere.

    • Catalog Asset (–RU––--) - To run the schema inconsistencies check and update the data product installations.

  • A scoped role that grants you the following privilege:

    • Data Warehouse Connection (-R------) - To access remote objects.

The Catalog User global role and the DW Modeler scoped role template, applied together for example, grant these privileges. For more information, see Privileges and Permissions and Standard Roles Delivered with SAP Datasphere.

Context

To check for and resolve data product inconsistencies, use the Check for Schema Changes action.

If a data product is inactive, you can resolve the schema inconsistencies by activating it in SAP Business Data Cloud cockpit. Activating the data product automatically updates its installation. You can also uninstall the data product by ending all access agreements for it.

Procedure

  1. In the side navigation area, choose (Catalog & Marketplace) Start of the navigation path Next navigation step End of the navigation path (Data Product Access).
  2. At the top of the Data Product Access page select Check for Schema Changes.

    A dialog informing you that the check has started appears. The check might take some time to complete. When it's finished, the Resolve Inconsistencies page appears, showing a list of the data products that have schema inconsistencies.

  3. Select the data products that you want to update and choose Update Installations.

    If you don't want to update any of the data products, choose Cancel to return to the Data Product Access page.

  4. Review the confirmation dialog and select Confirm.

Results

A message confirms that some data products are queued for update. Updates start in a staggered sequence: the first data product begins updating, and each subsequent update starts a few moments after the previous one. You receive an in-app notification when each update starts and another when it ends.

During the installation update, all objects are redeployed, the replication flow to load the data in the updated schema is restarted, and all spaces where the data product is installed are refreshed.