An array of name-value pair attribute entries. Used as additional parameters in connection string.
The OCID of the compartment being referenced.
The name of the database.
Tags defined for this resource. Each key is predefined and scoped to a namespace.
Example: {@code {\"foo-namespace\": {\"bar-key\": \"value\"}}}
Metadata about this specific object.
An object's Display Name.
A simple key-value pair that is applied without any predefined name, type, or scope. Exists for cross-compatibility only.
Example: {@code {\"bar-key\": \"value\"}}
The name or address of a host.
Refers to the customer's master key OCID. If provided, it references a key to manage secrets. Customers must add policies to permit GoldenGate to use this key.
Locks associated with this resource.
An array of Network Security Group OCIDs used to define network access for either Deployments or Connections.
The password Oracle GoldenGate uses to connect the associated DB2 database.
The port of an endpoint usually specified for a connection. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
Controls the network traffic direction to the target: SHARED_SERVICE_ENDPOINT: Traffic flows through the Goldengate Service's network to public hosts. Cannot be used for private targets. SHARED_DEPLOYMENT_ENDPOINT: Network traffic flows from the assigned deployment's private endpoint through the deployment's subnet. DEDICATED_ENDPOINT: A dedicated private endpoint is created in the target VCN subnet for the connection. The subnetId is required when DEDICATED_ENDPOINT networking is selected.
Security protocol for the DB2 database.
The base64 encoded keystash file which contains the encrypted password to the key database file.
The base64 encoded keystore file created at the client containing the server certificate / CA root certificate.
The base64 encoded file which contains the self-signed server certificate / Certificate Authority (CA) certificate.
The OCID of the target subnet of the dedicated connection.
The DB2 technology type.
The username Oracle GoldenGate uses to connect to the DB2 database. This username must already exist and be available by the DB2 to be connected to.
Refers to the customer's vault OCID. If provided, it references a vault where GoldenGate can manage secrets. Customers must add policies to permit GoldenGate to manage secrets contained within this vault.
The information about a new DB2 Connection.