Remove a metabase - Connect_CDC - aws_mainframe_modernization_service - connect_cdc_mimix_share - 6.x

DB2/IBM i

1. Select Remove Metabase.

2. Review the text in the Remove Metabase dialog.

3. Click OK to remove the metabase.

• Removes all tables from the metabase (Product) library.

• Does not remove the metabase library.

• Does not remove log or configuration files.

• Does not remove replication user ID.

Informix DS

1. Select Remove Metabase.

2. Provide a user ID and password with Informix DS privileges to remove a database.

3. Review the text in the Remove Metabase dialog.

4. Click OK to remove the metabase.

Deletes omnirep database.

MS SQL Server

1. Select Remove Metabase.

2. Provide a password for the user sa, the system administrator. The user sa is used at the server to execute scripts that remove the Connect CDC metabase.

3. Review the text in the Remove Metabase dialog.

4. Click OK to remove the metabase.

1. Deletes omnirep data and log files.

2. Deletes rpuser login.

If the user rpuser is the default, you receive a warning message when you next try to access this server with that connection. A message reminds you of this.

Oracle

1. Select Remove Metabase.

2. Specify a user that has SYSDBA privileges. This user is used at the source to execute scripts that remove the Connect CDC metabase.

3. Specify if each tablespace, either data or temp, should be dropped.

4. Review the text in the Remove Metabase dialog.

5. Click OK to remove the metabase.

1. Removes the replication user schema (if user approves).

2. Deletes the replication users default tablespace if no other user is using it as a default or temporary tablespace.

3. Deletes replication user login to this server (if approved by user).

PostgreSQL

1. Select Remove Metabase.

2. Enter the database administrator user ID and password.

3. Review the text in the Remove Metabase dialog.

4. Click OK to remove the metabase.

1. Removes the metabase schema defined on the server properties page.

SQL Azure

1. Select Remove Metabase.

2. Review the text in the Remove Metabase dialog.

3. Click OK to remove the metabase.

1. Drops the 3 Metabase tables: trans_hwm, req_syncpoint and rp_process.

Sybase

1. Select Remove Metabase.

2. Provide a password for the user sa, the system administrator for the Sybase server. The user sa is used at the server to execute scripts that remove the Connect CDC metabase.

3. Review the text in the Remove Metabase dialog.

4. Click OK to remove the metabase.

1. Deletes omnirep data and log files.

2. Deletes rpuser login.

If the user rpuser is the default, you receive a warning message when you next try to access this server with that connection. A message reminds you of this.

Teradata

1. Select Remove Metabase.

2. Enter the database administrator user ID and password.

3. Review the text in the Remove Metabase dialog.

4. Click OK to remove the metabase.

1. If the replication user and metabase schema name are the same, all traces of the metabase are removed, including the tables, database and the user.

2. If the replication user and the metabase schema name are different:

• The metabase is removed.

• If no other metabases exist under the user, the user is removed.

• If the user owns other metabases, the user remains untouched.

UDB

1. Select Remove Metabase.

2. Provide a user ID and password with UDB SYSADM privileges.

3. Review the text in the Remove Metabase dialog.

4. Click OK to remove the metabase.

You receive a message that your original Connect CDC Director connection used the rpuser ID, which has now been removed. You must change the user ID to log on to the database.

1. The UDB metabase schema (RPUSER) is removed.

2. Tablespace (RPUSER) is removed.