Known issues with OCI GoldenGate connections

Explore known issues related to connections and how to work around them.

Oracle AI Data Platform: Resource Principal authentication

Resource Principal authentication for Oracle AI Data Platform connections encounter the following error:

JDBCMDP-00034 Current attempt to connect failed with error: [[JDBC Driver]Could not find private key: /tmp/ogg/ocid1.goldengateconnection.oc1.phx.amaa...lqabqqxq/privateKeyFile].

Workaround: Edit the connection and select a different authentication method such as Use current tenancy and user or Specify another tenancy and user.

Errors encountered when using Connections with Secrets

You may encounter connectivity errors when using Connections with secrets and vaults in the following versions of OCI GoldenGate:

Workaround: Recreate your connection without using OCI Vault Secrets:

  1. In the Create connection page, expand Advanced options on the bottom of the page.

  2. Under Advanced options, expand Settings.

  3. Deselect Use secrets in vault.

  4. Select Create.

Or, if Advanced options is not available in your connection, try using an earlier version of the deployment.

Oracle Object Storage replication error when using Resource Principal

If your Oracle Object Storage connection uses Resource Principal authentication, the Replicat fails with the following error:

ERROR 2025-06-12 14:48:16.000489 [main] - An exception has occurred: java.lang.NullPointerException: Cannot invoke "String.startsWith(String)" because "path" is null java.lang.NullPointerException: Cannot invoke "String.startsWith(String)" because "path" is null

Workaround: To work around this issue, edit the connection, and then select a different authentication method.

Apache Iceberg connection to AI Data Catalog service authentication error

Apache Iceberg connections to AI Data Catalog service expires due to authentication error caused by token expiration. If you encounter this issue, contact Oracle Support.

Apache Iceberg NoSuchFileException error

If you encounter the following error when using Apache Iceberg connections, open a support ticket, share the details and error message:

Caused by: java.nio.file.NoSuchFileException: /tmp/ogg/ocid1.goldengateconnection.oc1...../restCatalogProperties

Java.net.UnknownHostException errors for Amazon S3 and Google Cloud Storage connections

Amazon S3 and Google Cloud Storage connections with Shared endpoints encounter Java.net.UnknownHostException errors.

Workaround: Edit the connection and change the Traffic routing method to Dedicated, or select Dedicated when you create Amazon S3 and Google Cloud Storage connections.

Issue with Amazon S3 connections in OCI GoldenGate

If you encounter the following error when using Amazon S3 connections, then open a support ticket, share the details and error message.

ERROR 2024-03-04 11:42:31.000505 [TaskEngine_2(FileFinalizeTask)] - Verify S3 bucket
      [ggstest] failed.com.amazonaws.SdkClientException: Unable to execute HTTP request: s3.us-east-2.amazonaws.com

Workaround:

  1. Connect to Cloud Shell.

  2. Create a new Amazon S3 connection using the following CLI sample:

    oci goldengate connection create-amazon-s3-connection --routing-method SHARED_SERVICE_ENDPOINT --display-name <connection_name> --compartment-id <compartment_ocid> --technology-type AMAZON_S3 --access-key-id <aws_access_key> --secret-access-key <aws_secret> --connection-region <amazon_s3_bucket_region>
  3. Assign the connection to your deployment.

  4. Add and run a Replicat for Amazon S3.

Alternatively, if you prefer not to use public access, configure your Amazon S3 connection’s buckets to use AWS VPC Endpoints. For OCI GoldenGate to access your S3 bucket using VPC Endpoints, you must also configure an IPsec VPN between your VCN and the AWS VPC.

To set the endpoint for Amazon S3, add the gg.eventhandler.s3.url property to Replicat Properties File, and provide the endpoint for the private connection.

MongoDB Test connection issue

You may encounter an error when using Test connection with MongoDB connections. You can ignore this error and test MongoDB connections in the OCI GoldenGate deployment console. In the deployment console, open the navigation menu for the Administration Service, select Configuration. Your MongoDB connection should be listed as a credential, where you can select **Connect to ** to test the connection.

Action required for Autonomous AI Database connections that use mTLS Authentication

When an Autonomous AI Database wallet is rotated, the OCI GoldenGate connection to this database must be refreshed to retrieve the latest wallet information.

For more information see, My Oracle Support (MOS) Document 2911553.1.

To refresh an Autonomous AI Database connection: Edit and save the connection to the Autonomous AI Database (Autonomous AI Transaction Processing or Autonomous AI Lakehouse). Saving the connection automatically downloads and refreshes the wallet. No other changes to the connection is needed.

To verify:

  1. Launch the deployment console for a deployment that uses the Autonomous AI Database connection.

  2. In the deployment console, open the navigation menu, and then select Configuration.

  3. On the Credentials screen, observe the Autonomous AI Database connection string.

    Before the wallet is refreshed, the connection string looks like the following:

    ggadmin@(DESCRIPTION=(TRANSPORT_CONNECT_TIMEOUT=3)(CONNECT_TIMEOUT=60)(RECV_TIMEOUT=120)(retry_count=20)(retry_delay=3)(address=(protocol=tcps)(port=1522)(host=adb.us-phoenix-1.oraclecloud.com))(CONNECT_DATA=(COLOCATION_TAG=ogginstance)(FAILOVER_MODE=(TYPE=SESSION)(METHOD=BASIC)(OVERRIDE=TRUE))(service_name=<adb-servicename>_low.adb.oraclecloud.com))(security=(MY_WALLET_DIRECTORY="/u02/connections/ocid1.goldengateconnection.oc1.phx.<ocid>/wallet")(SSL_SERVER_DN_MATCH=TRUE)(ssl_server_cert_dn="CN=adwc.uscom-east-1.oraclecloud.com, OU=Oracle BMCS US, O=Oracle Corporation, L=Redwood City, ST=California, C=US")))

    After the wallet is refreshed, the connection string is updated to look like the following:

    ggadmin@(DESCRIPTION=(TRANSPORT_CONNECT_TIMEOUT=3)(CONNECT_TIMEOUT=60)(RECV_TIMEOUT=120)(retry_count=20)(retry_delay=3)(address=(protocol=tcps)(port=1522)(host=adb.us-phoenix-1.oraclecloud.com))(CONNECT_DATA=(COLOCATION_TAG=ogginstance)(FAILOVER_MODE=(TYPE=SESSION)(METHOD=BASIC)(OVERRIDE=TRUE))(service_name=<adb-servicename>_low.adb.oraclecloud.com))(security=(MY_WALLET_DIRECTORY="/u02/connections/ocid1.goldengateconnection.oc1.phx.<ocid>/wallet")(SSL_SERVER_DN_MATCH=TRUE)(ssl_server_dn_match=yes)))

MySQL databases not appearing in Credential Alias list

MySQL database usernames that include an ‘@’ symbol don’t appear in Credential Alias list when creating an Extract in the OCI GoldenGate deployment console.

Workaround: Select a different alias from the list and then manually update the Parameter File on the next screen.

Network timeouts affect database connections using private endpoints

If you’re using a private endpoint to connect to a database, then you may encounter network timeouts when starting or stopping Extract processes.

Workaround: You can do one of the following:

SCAN proxy doesn’t support TLS

While OCI GoldenGate supports Oracle Single Client Access Name (SCAN) hosts and IPs, the SCAN proxy does not support TLS.

Workaround: You can connect to a RAC database using the Database Node IP.

User OCID Mismatch in Oracle Object Storage connection (Federated users only)

If a federated user selects Use current user when creating an Oracle Object Storage connection, their OCID doesn’t match the OCID picked up by the system.

Workaround: When you create an Oracle Object Storage connection, ensure that you choose Specify another user, and then enter the federated user’s OCID.

To find the user OCID, select Profile in the Oracle Cloud console global header, and then select the user name. On the User Details page, under User Information, select Show for OCID.