Manage Replication Metabase

A collection of internal objects that define and enable data distribution within the Data Integration components. A source data connection is required to configure a metabase.

Upgrade Metabase

Occasionally, metabases need to be upgraded to ensure that the metabase version on the source system matches the installed version of the Data Integration on the runtime server. Upgrading ensures the latest tables, indexes, and other objects are installed on the metabase.
Note: Upgrading recreates metabase indexes and procedures.
See Guidelines
  • Only certain users have the privileges to upgrade a metabase. You must supply the proper credentials depending on your connection type:
    • For Db2 for LUW, Oracle, and SQL Server metabases, you must supply the database administrator credentials.
    • For Db2 for IBM i metabases, you must supply the credentials for the repository user associated with the metabase.
  • You upgrade one metabase at a time.
  • Before you upgrade the metabase:
    • Disable capture for all enabled tables in all data flows that are using the data connection associated with the metabase.
    • Stop the current project. If you do not, an error will occur and the upgrade metabase action will not complete.

To upgrade a metabase

  1. Disable capture for all enabled tables in all data flows that are using the data connection associated with the metabase.
  2. Stop the project, if not already stopped.
  3. Click Projects from the navigation menu and open the replication project associated with the metabase you want to upgrade. The Metabases portlet opens under the Data Flows portlet, displaying all metabases associated with the project.
  4. Select the metabase you want to upgrade and click More > Upgrade. The Upgrade Metabase window opens showing metabase details including the database server, data connection, the current metabase version, and the version to which the metabase needs to be upgraded.
  5. Specify user credentials depending on the connection type:
    • Db2 for IBM i. Specify the Replication user ID credentials for the metabase. The default is the current replication user associated with the metabase.
    • Db2 for LUW. Specify the Db2 administrator user ID credentials for the source server.
    • SQL Server. Specify the SQL server administrator user ID for the source server. The default is sa.
      Note: For Oracle, the Oracle administrator user ID for the Oracle system displays. By default, this value is SYS and cannot be changed.
  6. For Password, enter the password for the user. If the password is not valid you are prompted to enter a valid password.
  7. Click Upgrade. One of the following occurs:
    • If there are no problems or errors upgrading the metabase, the window closes and the metabase is upgraded.
    • If errors occur and the metabase could not be upgraded, the Upgrade Metabase Errors window opens detailing problems detected during the process.

Delete Metabase

You can delete any metabase you created for a replication data connection. For example, you may want to make changes to a metabase, in which case you must delete it and add another to the data connection.
When you delete a metabase, tables, procedures, and indexes are removed. The following also occurs based on the source connection type:
Source Connection Type Description
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 and associated privileges are removed.

The replication user schema is removed.
SQL Server

The data and log files are deleted.

The replication user and associated privileges are removed.
Note: The physical files associated with the metabase on the database system are not removed during this process. These files must be manually removed.
  • You delete one metabase at a time.
  • Before deleting a metabase, disable capture for any tables enabled for capture in the data flow using the current data connection, then stop the project. Before you can start the replication project again you must first add another metabase.
  • Ensure the replication backlogs are empty.
  • Only certain users have the privileges to delete a metabase. You must supply the proper credentials depending on your connection type:
    • For Db2 for LUW, Oracle, and SQL Server metabases, you must supply the database administrator credentials.
    • For Db2 for IBM i metabases, you must supply the credentials for the user associated with the metabase.

To delete a metabase

  1. On the Metabases portlet, select the metabase you want to delete and click More > Delete. The Delete Metabase window opens, showing the metabase name, associated database server, and data connection.
  2. Specify user credentials depending on the connection type:
    • Db2 for IBM i. Specify the Replication user ID credentials for the metabase. The default is the current replication user associated with the metabase.
    • Db2 for LUW. Specify the Db2 administrator user ID credentials for the source server.
    • SQL Server. Specify the SQL server administrator user ID for the source server. The default is sa.
      Note: For Oracle, the Oracle administrator user ID for the Oracle system displays. By default, this value is SYS and cannot be changed.
  3. For Password, enter the user password for the user. If the password is not valid, you are prompted to enter a valid password.
  4. To delete the metabase, click Delete. One of the following occurs:
    • If there are no problems or errors deleting the metabase, the window closes and the metabase is deleted.
    • If errors occur and the metabase could not be deleted, the Delete Metabase Errors window opens detailing problems detected during the process.
  5. Add another metabase as needed. You cannot start the project again without a metabase.