JavaScript must be enabled to correctly display this content
Create Data Transforms resources
To use Data Transforms in OCI GoldenGate, create a
Data Transforms deployment, and then create and assign a Generic
connection type to the deployment.
Create a Data Transforms
deployment
Before you begin
Before you create a
deployment, review the following requirements:
If you enable public deployment console access in Step 10, OCI GoldenGate creates a load balancer in your tenancy VCN on your behalf. To
ensure successful creation of the deployment and load balancer, you must have the
appropriate policies, quotas, and limits in place.
In Oracle Cloud Infrastructure Identity and Access Management (OCI IAM)
enabled tenancies, Step 16 requires you to select the credential store you'll use to log
in to the deployment console.
Depending on your source and target technology types, you may need more
than one deployment. If you're not sure how many deployments you need for your solution,
see Example topologies for details.
To create a Data Transforms deployment:
In the Console navigation menu, click Oracle Database, and then
select GoldenGate.
On the Deployments page, click Create deployment.
In the Create deployment panel, enter a name and optionally, a description.
From the Compartment dropdown, select a compartment in which to create the
deployment.
Select one of the following options:
Production: Sets up a deployment with
recommended defaults for a production environment. The minimum number of OCPUs is 4,
with auto-scaling enabled.
Development or testing: Sets up a deployment
with recommended defaults for a development or testing environment. The minimum number
of OCPUs is 1.
For OCPU count enter the number of
Oracle Compute units (OCPUs) to use.
Auto scaling enables OCI GoldenGate to scale up to three times the number of OCPUs you specify for
OCPU Count, up to 24 OCPUs. For example, if you specify your OCPU Count as 2 and enable
Auto Scaling, then your deployment can scale up to 6 OCPUs. If you specify your OCPU
Count as 20 and enable Auto Scaling, OCI GoldenGate can only scale up to 24
OCPUs.
From the Subnet in <Compartment> dropdown, select the
subnet to which a private endpoint is created from the OCI GoldenGate service
tenancy. This ensures that the deployment is always available over this subnet, as long as
the policies for this subnet allow access. The private endpoint is only used to access the
deployment console, and doesn't provide access to other resources in the subnet.
To select a subnet in a different compartment, click Change
compartment.
Note:
You can only select a private subnet
when creating a deployment.
Select a license type.
(Optional) Click Show advanced options for network options and
to add tags.
In the Network tab,
Select Enable GoldenGate console public
access to include a public endpoint in addition to a private
endpoint, and allow public access to the deployment console for users. If
selected, OCI GoldenGate creates a load balancer in your tenancy to
create a public IP. Select a subnet in the same VCN as this deployment in which to
create the load balancer.
Note:
The
load balancer is a resource that comes with an additional cost. You can manage
this resource, but ensure that you don't delete the load balancer while your
deployment is still in use. Learn more about load balancer
pricing.
Select Customize endpoint to provide a private fully
qualified domain name (FQDN) prefix that you'll use to access the private
service console URL. You can also optionally upload an SSL/TLS certificate
(.pem) and its corresponding private key, however, password protected
certificates are not supported.
It's your responsibility to ensure that the FQDN resolves to the
deployment's private IP address in the subnet you previously selected.
If the deployment is public, it's your responsibility to ensure
that the FQDN publicly resolves to the deployment's public IP address.
A self-signed certificate is generated for you, if you don't
provide one.
Note:
Your SSL certificate must meet the following requirements:
It's common name should match the deployment's FQDN. If it
doesn't, you'll encounter warnings when you access the deployment
console.
It must be signed using a strong hashing algorithm. arcfour,
arcfour128, arcfour256, none algorithm types are not permitted.
It must not be expired.
It's maximum validity should not exceed 13 months.
It must not be a self-signed certificate.
If you encounter "Invalid Private Key" errors, you can
check the correctness of the key using the following OpenSSL commands. Run
this command against the
certificate:
For GoldenGate instance name, enter the name that the
deployment will assign to the GoldenGate deployment instance upon
creation.
The Administrator username automatically populates with SUPERVISOR for
you.
For Administrator password, enter a password for the SUPERVISOR user, and then
confirm that password.
Click Create.
The deployment takes a few minutes to create. Its status changes to Active when it's
ready to use. You can then click Launch console from the deployment details page, or
select Launch console from the deployment's Actions (three dots) menu on the
Deployments page.
Create a Generic connection
Use a Generic connection for the Data Transforms deployment to use as a data
source.
From the OCI GoldenGate Overview page, click
Connections.
You can also click Create Connection under the
Get started section and skip to step 3.
On the Connections page, click Create Connection.
In the Create Connection panel, complete the General Information
fields as follows:
For Name, enter a name for the connection.
(Optional) For Description, enter a description that helps
you distinguish this connection from others.
For Compartment, select the compartment in which to create
the connection.
From the Type dropdown, select Generic
connection.
(Optional) Click Show advanced options to manage keys or add
tags.
Under Security, select one of the following:
Select Use Oracle-managed encryption key to leave all
encryption key management to Oracle.
Select Use customer-managed encryption key to select a
specific encryption key stored in your OCI Vault to encrypt your connection
credentials.
Under Tags, add tags to organize your resources.
Click Next.
Complete the Connection details page as follows:
For Host, enter a comma separated list of
<host>:<port> entries.
For Network connectivity, select a
Traffic routing method:
Shared endpoint, to share an
endpoint with the assigned deployment. You must allow connectivity from the
deployment's ingress IP.
Dedicated endpoint, for
network traffic through a dedicated endpoint in the assigned subnet in your VCN.
You must allow connectivity from this connection's ingress IPs.
Note:
Select this option if your Azure SQL Managed Instance doesn't have a public endpoint.
If selected:
Select the subnet
(Optional) Enter the Private IP only if the hostname is not
resolvable from your subnet or if it uses SSL/TLS.
Note:
OCI GoldenGate
rewrites the private IP in the format,
ip-10-0-0-0.ociggsvc.oracle.vcn.com.
It takes a few minutes for the connection to become Active. Ensure that you assign
the connection to a deployment to use it in a data replication.
Assign a connection to a
deployment
Ensure that you have connections created for your source and target
technologies.
To assign a connection to a deployment:
On the deployment details page, under Resources, click
Assigned connections.
Click Assign connection.
In the Assign connection dialog, select a connection from the dropdown. If you
want to select a connection from a different compartment, click
Change Compartment.
Click Assign connection.
The selected connection appears in the Assigned connections list. You can also
view and manage this relationship from the Connection details page under
Assigned deployments.