Property reference for creating metabases for Oracle, Db2 for IBM i, Db2 for LUW, SQL Server, and Azure SQL Database data connections.
What's changed: In the new user experience, some metabase field labels have changed. Data connection appears as Connection, Replication user ID appears as Replication user, and the separate admin and replication password labels appear as Password. Oracle field labels such as Tablespace for metabase, Size, and Temporary tablespace for metabase also use updated labels. For more information on the new experience, see About the new user experience.
Oracle metabase settings
| Option | Description |
|---|---|
| Data connection | Oracle JDBC data connections. If there is only one Oracle JDBC data connection, it is selected by default. |
| Database server | Address of the database server where the metabase will be created. Populated when the data connection is selected. |
| Oracle administration user ID | Oracle system admin user ID for the source server. The value is SYS. |
| Password (admin) | Password for the Oracle admin credentials, used to create the metabase. Not stored. |
| Replication user ID | User created for replication. Must be unique to the metabase or project. The user ID cannot be reused across projects. |
| Password (replication) | Password for the replication user ID. |
| Metabase name | Name of the metabase. Defaults to the replication user ID value. |
| Tablespace for metabase | Name of the tablespace to create for the metabase. |
| Data file | File on the database server used to store the metabase tablespace. |
| Size | Size of the tablespace file in megabytes. Default: 200. |
| Temporary tablespace for metabase | Name of the tablespace for temporary metabase space. |
| Temporary data file | File that stores the temporary tablespace for the metabase. |
Db2 for IBM i metabase settings
| Option | Description |
|---|---|
| Data connection | Db2 for IBM i JDBC data connections. If there is only one, it is selected by default. |
| Database server | Address of the database server where the metabase will be created. Populated when the data connection is selected. |
| Replication user ID | User chosen during the Change Selector (Log Reader) software installation on IBM i, for example OMNIENT. |
| Password | Password for this ID. |
| Metabase library | Name of the metabase library to create. Must be unique for this project or source combination and not used by any other replication project. |
Db2 for LUW metabase settings
| Option | Description |
|---|---|
| Data connection | Db2 for Linux, Unix, or Windows JDBC data connections. If there is only one, it is selected by default. |
| Database server | Address of the database server where the metabase will be created. Populated when the data connection is selected. |
| Db2 administrator user ID | Db2 admin user ID. |
| Password (admin) | Password for the admin credentials, used to create the metabase. Not stored. |
| Replication user ID | User ID to associate with the metabase. |
| Password (replication) | Password for the replication user ID. |
| Metabase name | Name of the metabase. Default: RPUSER. |
SQL Server metabase settings
| Option | Description |
|---|---|
| Data connection | SQL Server JDBC data connection for the metabase. If there is only one, it displays by default. When adding a metabase from a data connection, this value is auto-populated. |
| Database server | Address of the database server where the metabase will be created. Auto-populated from the data connection. |
| SQL Server administrator user ID | SQL Server system administrator user ID, used to create the metabase. Default: sa. Must have privileges to create a database on the source system. |
| Password (admin) | SQL Server administrator password. Not stored; protected by SSL. |
| Replication user ID | Replication user associated with the metabase database. Default: rpuser (cannot be changed). The first metabase installed creates the rpuser login. |
| Password (replication) | Replication user password. Select Show or Hide to toggle visibility. |
| Metabase name | Name of the metabase. Default: omnirep. Each metabase in the SQL Server instance must have a unique name. |
| Maximum transaction rows per user pool | For trigger-based capture: maximum rows per user pool. Default: 400000. If the limit is reached, the trigger fails. |
| Data logical name and size |
|
| Data physical name | Physical path of the data file on SQL Server. Available after selecting
Retrieve Path. Example:
C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\metabase_name_data.mdf. |
| Log logical name and size |
|
| Log physical name | Physical path of the log file on SQL Server. Available after selecting
Retrieve Path. Example:
C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\metabase_name_log.ldf. |
Azure SQL Database metabase settings
Preview: Azure SQL Database target support is currently in Preview for select workspaces and might be subject to change before general availability.
For Azure SQL Database targets, the Data Integration service installs the replication metabase tables in the selected target database after you map the source tables. It does not create a separate metabase database or a separate replication user.
| Option | Description |
|---|---|
| Data connection | Azure SQL Database target data connection. The database user defined in the connection must have SELECT, INSERT, UPDATE, DELETE, and CREATE permissions at a minimum. |
| Metabase installation | If no metabase tables are present in the target database, Data Integration installs them after mapping. If some metabase tables are present, Data Integration flags the metabase as potentially damaged and asks you to confirm before reinstalling it. If all metabase tables are present, installation is skipped. |
| Project use | Use a separate Azure SQL Database target for each project. Because replication tracking information is stored inside the selected target database, pointing a second project at the same Azure SQL Database can interfere with replication tracking for the first project. |