Create a new server for Oracle - Connect_CDC - aws_mainframe_modernization_service - connect_cdc_mimix_share - Latest

Name

Use alphanumeric characters to specify a unique server name for use in the model.

DBMS Type

Select Oracle from the dropdown list.

DBMS version

Server name

Specify the Service Name to connect to Oracle. This value is used for connections to Oracle by the kernel components and client utilities such as MonCon and the Director. For additional information, refer to Connect CDC uses service name instead of SID to connect to Oracle.

DBMS instance port

From a command line, enter:

lsnrctl status

This displays the status of the listener. One of the lines shows the port number. For example:

Connecting to

(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.1.2)(PORT=1521)))

JDBC Driver

The JDBC Driver is automatically selected based on the database you specified in the DBMS version field.

• Oracle 11g. Use this driver for DBMS version 11g.

• Oracle 12c. Use this driver for DBMS version12c, 18c, and 19c.

DriverVersion 

View the JDBC Driver version. This information is obtained each time a connection to the database is made (including a Test Connection).

DBMS logon IDs and DBMS logon password

Specify the Default and Rep user IDs.

1. Input the user login ID for accessing this server.

2. Specify the owner of the metabase on this server.

3. Select Default and Rep user (they may be different).

• The Default user is what Connect CDC Director uses to connect to the server.

• The Rep user is what the kernel uses to connect to the server.

Metabase schema

Set to the value entered for the DBMS logon ID. This is the owner of the metabase. It is the qualifier of the metabase tables, in the format qualifier.tablename.

Enable Prepared Statements

If selected, prepared statements are enabled for the entire database server. A prepared SQL statement is a statement in which the steps to parse, analyze, validate, and determine the access path are only done once, when the statement is first prepared. On subsequent executions of the statement, the database has this information stored in memory and can skip the initial preparation steps. After a statement is prepared, only the column values change from one execution of the statement to the next.

Each table can have as many as seven prepared statements: one for insert, up to five for update, and one for delete. The first time an insert, update, or delete is encountered, the statement is prepared, added to the cache, and is used to update the table. The statements are kept in the cache until removed.

Using prepared statements provides a significant performance improvement when the same SQL statement is executed over and over. However, in some cases data for unchanged columns will be captured and sent across the network.

Individual tables can disable prepared statements. This is useful for managing the size of the cache file.

Database limit

Displays the maximum size allowed by the database for open statements in the cache. The Specified limit, below, cannot exceed this value. The correct value is provided after you run a Test Connection. To do so, right-click the server name, then select Test Connection.

Specified limit

Enter the maximum size allowed for open statements in the cache. When the statement cache is full, the least recently used statement is removed from the cache, closed, and destroyed. If Journal batching is enabled, prior to removing the statement, pending batch updates are executed, If the statement that was removed is later referenced, a new prepared statement is created and added to the cache.

Note the following:

• The default is 700.

• The minimum value is 7.

• The maximum value is specified in Database limit, above. If you set the specified limit to a value lower than the number of prepared statements in the model, performance may decrease.

Remote Machine Name or IP

Select this checkbox if you are creating a new remote server for Oracle. Refer to Create a new remote Oracle server. Specify the remote machine name or IP address. The remote machine name or IP address must be a valid machine name or IP address of the machine hosting the remote Oracle instance. The remote machine name (or IP address), and the Server name establish the connection with the remote server. This is a required field.

Note: If you are connecting to an Oracle Real Application Cluster (RAC) the Single Client Access Name (SCAN) is required to connect to the RAC instance as the remote machine name/IP Address. This provides a single name for clients to access Oracle databases running in a cluster. This ensures that Connect CDC will reconnect if a node in the cluster goes offline.

Pluggable database (PDB)

Select this checkbox if you are working with a pluggable Oracle database.

Selecting the checkbox enables the PDB Settings tab.

Enable JDBC Encryption

Select this checkbox to enable JDBC encryption, which encrypts communication with the Oracle database server using, in priority order, the AES256, AES192, or AES128 encryption algorithm and sets encryption to required on the server.

Credential Management

Select a credential management provider that contains the login credentials for DBMS user IDs. Possible values are None and CyberArk. Selecting CyberArk enables the CyberArk Settings tab.

Tnsname

Available if you are creating a new remote server for Oracle. Refer to Create a new remote Oracle server. Specify the net service name that is required to connect to the remote Oracle instance. This field is optional and only available if you select "use load when possible" for a copy or sync request.

Model using metabase

Displays the name of the model. (Informational only)

Model version

Displays the version number, updated after each commit. (Informational only)

Metabase version

Displays the version of the metabase (for example, 40d). (Informational only)

GMT offset(minutes)

Displays the amount of time, in minutes, that local time differs from Greenwich Mean Time (GMT). For example, Boston is 300 minutes less than GMT. (Informational only)

PDB Settings tab 

CDB$ROOT Rep User 

Enter the root container user name.

Password 

Enter the root container user password.

CyberArk Settings tab 

Login ID

Unique identifier for default, rep, PDB root container, and additional user IDs used for DBMS logon. All the login IDs are displayed here, whether or not they use a credential manager.

Type

Identifies the credential manager that applies for a login ID. Possible values are None and CyberArk.

Configure...

Click Configure... to open the CyberArk Options dialog, which accepts changes in 2 fields to configure the CyberArk connection required to connect to CyberArk:

• Application ID: an application ID registered in CyberArk

• Query String: query string listing CyberArk fields like Safe, Object, Address, PolicyID, etc.