Sign inTry Free

Connect with Oracle GoldenGate

On this page

You can load your data from various sources into SingleStore using Oracle GoldenGate and analyze the data in real time. Add a connection to your SingleStore cluster in GoldenGate, and use it in the Replicat that loads data in the target SingleStore database.

Prerequisites

  • Access to Oracle GoldenGate.

  • Download and install Oracle GoldenGate Microservices for MySQL v21.3.x.

  • Install the following patch: Patch 35271106: Oracle GoldenGate 21.10.0.0.1 Microservices for MySQL-compatIble DBs.

  • Hands-on knowledge of the GoldenGate application/UI (refer to GoldenGate documentation).

Connect to SingleStore from Oracle GoldenGate

To connect your SingleStore databases with Oracle GoldenGate, perform the following tasks:

  1. Create a source Extract, select Administration Service > Overview. Under Extracts, select the + (plus) icon to add a new extract. The trails from this extract will be used by a SingleStore Replicat. Any database supported by Oracle GoldenGate as a source can support a SingleStore Replicat.

  2. Select Administration Service > Configuration > Database > Credentials > + (plus icon) to create/configure a connection to the SingleStore database.

  3. On the Credentials page, enter or select the following information:

    • Credential Alias: Enter an alias for this credential configuration.

    • Database Server: Enter the IP address or hostname of the SingleStore cluster.

    • Port: The default port is 3306.

    • User ID: Enter the username of the SingleStore user. The user specified in the Credential Alias must have the required privileges to create a table in the SingleStore database.

    • Password: Enter the password for the SingleStore user.

    • Verify Password: Re-enter the Password.

    • Use defaults for other configuration items.

  4. Select Submit.The Credential Alias is created.

  5. From the Credentials section, use the Credential Alias created earlier to connect to the target database.

  6. If you want to create a Parallel Replicat, skip to step 8. A checkpoint table is automatically created for a Parallel Replicat when it starts. Create a checkpoint table to be used by the Replicat. Select the + (plus) icon next to Checkpoint.

  7. Enter a name for the table in the Checkpoint Table box, and select Submit. The checkpoint table is added.

  8. Select Administration Service > Overview. To create a new Replicat, select the + (plus) icon next to Replicats.

  9. From the Replicat Type list, select a Replicat type, and then select Next.

  10. On the Basic Information page, select or enter the following information:

    • Process Name: Enter a name for the process.

    • Intent: Select the Intent from the list.

    • Credential Alias: Select the Credential Alias created earlier from the list.

    • Trail Name: Name of the Extract created in step 1.

    • Use defaults for other configuration items.

  11. Select Next.

  12. On the Parameter File page, update the parameter setting to include the required source schema tables that will be mapped to the target schema tables in SingleStore.

  13. Select Create and Run, and confirm that the new Replicat is running.

To confirm that the replication process is running, perform some DML operations on your database, and then perform the following tasks:

  • Under Extract, select Action > Details. On the Statistics tab, you can see the number of operations performed.

  • Select the Statistics tab for the Replicat (Replicat > Action > Details). The updates are visible in the Table Statistics section.

Remarks

  • You cannot replicate your data to views. Refer to CREATE VIEW for more information.

  • Updates to columns in the shard key are not supported.

  • Updates to the primary key on tables without explicit shard keys are not supported, because SingleStore assigns the primary key column as the shard key in these cases.

  • The LIMITROWS option for the Replicat is not supported for SingleStore tables without either a primary key or a unique key that is spread across multiple partitions.

  • SingleStore does not support cross-database transactions. Therefore, Replicat can only map to a single database or schema. This includes mappings for checkpoints and heartbeat tables, which must all be created in the same database.

Refer to Oracle GoldenGate Integration for SingleStore for related information.

Last modified: July 5, 2023

Was this article helpful?

On this page

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined

  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined

  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
        cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
          --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
          --bundle undefined \
          --new-bundle-format -
    Verified OK