Configure metabase - Precisely Data Integrity Suite

Data Integrity Suite
Product
Spatial_Analytics
Data_Integration
Data_Enrichment
Data_Governance
Precisely_Data_Integrity_Suite
geo_addressing_1
Data_Observability
Data_Quality
dis_core_foundation
Services
Spatial Analytics
Data Integration
Data Enrichment
Data Governance
Geo Addressing
Data Observability
Data Quality
Core Foundation
ft:title
Data Integrity Suite
ft:locale
en-US
PublicationType
pt_product_guide
copyrightfirst
2000
copyrightlast
2026

Create, upgrade, and delete metabases for data replication projects.

Metabases are repositories of database tables and objects that define and manage data replication projects. Each project has a unique metabase tied to a source data connection. Db2 for IBM i, Db2 for LUW, Oracle, and SQL Server data connections used for a replication project must be associated with a metabase. Metabases store replication backlogs, capture status, and metadata about tables enabled for replication.

What's changed: In the new user experience, access metabases from the project row context menu in Continuous Replication. Metabase appears as Metabases, +New Metabase appears as Add metabase, and upgrade and delete actions are available from the metabase row context menu. For more information on the new experience, see About the new user experience.

Create metabase

You can create a metabase when creating a new pipeline, or from the project-level action menu.

  1. From Integration > Continuous Replication, click the ellipsis from the global action menu and select Metabase.
  2. On the Metabase page, if no metabase is present, click +New Metabase.
  3. Specify the metabase properties for the connection type and click Create. For property details, see Supported metabase.

Upgrade metabase

Upgrade a metabase so the version on the source system matches the installed version of Data Integration on the runtime server.

Warning: Upgrading recreates metabase indexes and procedures.
  1. Disable capture for all enabled tables in all data connections associated with the metabase.
  2. Stop the project if not already stopped.
  3. From the navigation menu, click Projects and open the replication project associated with the metabase.
  4. Select the metabase and click More > Upgrade. The Upgrade Metabase window opens with the current and target versions.
  5. If using Key Vault authentication, provide the secret key path. For multiple user IDs, enter multiple secret key paths.
  6. Specify user credentials for the connection type (Db2 for IBM i, Db2 for LUW, or SQL Server).
    Note: For Oracle, the Oracle administrator user ID (SYS) displays and cannot be changed.
  7. Enter the password and click Upgrade.

Delete metabase

When you delete a metabase, tables, procedures, and indexes are removed. What else occurs depends on the connection type:

  • Db2 for IBM i: Tables are removed from the metabase library. The library, log files, and configuration files are not removed.
  • Db2 for LUW: The metabase schema and tablespace are removed.
  • Oracle: All tablespaces are dropped. The replication user, associated privileges, and schema are removed.
  • SQL Server: The data and log files are deleted. The replication user and associated privileges are removed.
    Note: Physical files on the database system are not removed and must be deleted manually.
  1. Select the metabase and click More > Delete. The Delete Metabase dialog opens showing the metabase name, database server, and data connection.
  2. Specify user credentials for the connection type (Db2 for IBM i, Db2 for LUW, or SQL Server).
    Note: For Oracle, the Oracle administrator user ID (SYS) displays and cannot be changed.
  3. Enter the user password and click Delete.
  4. Add another metabase as needed. The project cannot be restarted without a metabase.