Syncing Oracle® to GritDB with a CDC tool
TPC-H data (SF10, 86.58 million rows in 8 tables) is loaded into Oracle and synced to GritDB with a CDC tool.
Reference setup · in-house test
Adding an analytics system to an Oracle® operational database with CDC
GritDB does not read Oracle directly. A CDC tool writes Oracle's changes straight into GritDB's transaction engine (PostgreSQL). In this test, the same changes also went to PostgreSQL, and we ran the same queries on both databases to compare their times.
- Query with the largest speedup · Q18 (PostgreSQL 32.6 s → GritDB 1.5 s)
- Up to 21.3 times
- SF10 · total of 20 queries (PostgreSQL 134.0 s → GritDB 24.8 s)
- 5.4 times in total
- TPC-H data (SF10) synced from Oracle with a CDC tool
- 86.58 million rows
In-house test (2026-09) · Amazon EC2 r8i.16xlarge (64 vCPU, 512 GB). PostgreSQL ran with the default parallel and work_mem settings (2 parallel workers per query, work_mem 4MB). Speedups are computed from times before rounding. The numbers are query times measured on GritDB and PostgreSQL, and totals count the 20 queries that both databases finished. Speedup per query: 1.8 to 21.3 times. These results are derived from TPC-H. They are not official TPC-H results and cannot be compared with published TPC-H results.
Problem
Teams that use Oracle, or are moving to PostgreSQL, also want to keep analytics separate. If analytics queries run on the operational database, they share its resources with business transactions. If you keep a separate analytics database, you need an ETL pipeline.
Setup
Oracle Database 26aiOperational database · TPC-H data SF10 (86.58 million rows)
CDC tool (same changes to two targets)
GritDBTransaction engine: PostgreSQL
PostgreSQLComparisonSame queries
Query time comparisonGritDB and PostgreSQL
- The CDC tool in the demo is Oracle GoldenGate. GritDB accepts writes from a CDC tool that targets PostgreSQL as they are.
- PLUG in the analytics engine (GritDB engine) takes over the writes that GritDB's transaction engine receives.
Demo video
Show the test environmentHide the test environment
| Role | Setup | Server | CPU | Memory |
|---|---|---|---|---|
| Source | Oracle Database 26ai | Amazon EC2 r8i.16xlarge | 64 vCPU | 512 GB |
| Target | GritDB (transaction engine: PostgreSQL 17.4) | Amazon EC2 r8i.16xlarge | 64 vCPU | 512 GB |
| Comparison | PostgreSQL 17.4 | Amazon EC2 r8i.16xlarge | 64 vCPU | 512 GB |
Data: TPC-H data at SF10 (8 tables, 86.58 million rows). All three use the same instance type, and GritDB and PostgreSQL received the same changes through the CDC tool. The data and queries are derived from TPC-H. These results are not official TPC-H results and cannot be compared with published TPC-H results. Per-query times are in Analytics performance based on the TPC-H benchmark.
Notes for 1.1
- Create and register the tables in GritDB first, then start the CDC initial load. Rows that existed before registration are not moved to the analytics engine.
- After you register or unregister a table, restart the apply process of the CDC tool. Each connection uses the registration status it checked first.
- Features that the CDC tool does not support for a PostgreSQL target (for example, DDL replication) are not supported in GritDB either.
- A TRUNCATE sent by the CDC tool is not reflected in the analytics engine in 1.1 either.
- Tables with an unsupported column type cannot be registered. Check the column types before you register a table.
- Create columns that must be exact, such as amounts, as numeric(p, s) with a declared precision. Keep p at 38 or less. The analytics engine computes numeric columns without a declared precision as approximate values.
- Write analytics queries in PostgreSQL syntax. Rewrite reports that use Oracle-specific syntax or PL/SQL in PostgreSQL syntax.
The setup of the two engines is in Architecture, and the installation steps are in QuickStart.
Oracle and Oracle GoldenGate are registered trademarks of Oracle and/or its affiliates, and Amazon EC2 is a trademark of Amazon.com, Inc. or its affiliates. TPC-H is a trademark of the Transaction Processing Performance Council. Postgres, PostgreSQL and the Slonik Logo are trademarks or registered trademarks of the PostgreSQL Community Association of Canada, and used with their permission.
See GritDB for yourself
Ask for a discovery meeting or a PoC, and we will get in touch.