{ Abhilash Kumar Bhattaram : Follow on LinkedIn }

OCI Golden Gate Registrations were the method
to register source and target Databases so far for Golden Gate Deployments , on 20th Oct 2022 , OCI "Database Registrations" were migrated to Connections

For those users who need to know quickly know about Connections , the Oracle documentation is below

OCI Golden Gate Connections
https://docs.oracle.com/en/cloud/paas/goldengate-service/mcjzr/index.html#articletitle

So precisely what does OCI Golden Gate Connections do and why is this migrated from Registered Databases.

1. OCI Connections are intended to ovecome several limitations from Registered Databases , one such example is the FQDN for ExaCS registrations were always a pain , this Connection has made it easier to detect ExaCS targets without any manual interventions. These connections require many IAM roles which are well documented in the link above

2. The Assignment of OCI Connections are a big move forward , in earlier "Registered Database" pretty much all registrations are visible for every deployment , which is not a good use case , the assignment of Connections to Deployment helps choose only the relevant connections are used.

3. The following are the various OCI Connections that can be used by Oracle Golden Gate Deployments from multiple Cloud Targets , I'm sure more would be added soon here.

• OCI Streaming
• GoldenGate
• Apache Kafka
• Amazon RDS Oracle
• Amazon RDS for MySQL
• Amazon RDS for MariaDB
• Amazon Aurora for MySQL
• Azure Database for MySQL
• Google Cloud SQL for MySQL

1. The OCI Golden Gate Connections pretty much makes the Oracle Stream Analytics redundant ( https://cloudmarketplace.oracle.com/marketplace/en_US/listing/70961838 ) , the connections is to ensure there is a single point of contrl in Golden Gate Deployments

2. OCI Golden Gate Deployments higher than version 21.6.0.0.3 will be having persistent Database Registrations , which means any Database connection changes within the OCI deployment will not be taken into effect upon Deployment restarts ( this is now where Documented ) , to overcome such issues the "Connections" would be a single point of configurations.

*Disadvantages : *

Every OCI Golden Gate Connection would assign an Internal IP and requires to use an IP in the subnet for compartment , this means once a "Connection" is established the IP changes will be persistent and connot be changed ( atleast at the point of writing this blog ) , if connection changes to TNS , FQDN , etc are needed a new connection will need to be set up. This is one of drawbacks I see with connections , however I believe this is ever evolving feature and will be improved at some point.

#oracle #oci #oracledatabase #goldengate #oraclecloud #oracledba #nabhaas