Re: Guidance Requested: Migrating Large-Scale DB2 Databases to PostgreSQL

From: Muhammet Kurtoğlu <muhammet(dot)kurtoglu(at)bisoft(dot)com(dot)tr>
To: Brian Crockard <bcrockard(at)yahoo(dot)com>
Cc: Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>, mahamood hussain <hussain(dot)ieg(at)gmail(dot)com>
Subject: Re: Guidance Requested: Migrating Large-Scale DB2 Databases to PostgreSQL
Date: 2025-10-16 12:50:20
Message-ID: CANM7_8VrstAOduJ44mEm7-KTjkM_NkFHpjZjfrVBKiZNsuVwdQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Try symetricds

*Muhammet KURTOĞLU*

T: +90(312) 220 12 20 <%2B90%28374%29%20262%2098%2000>

F: +90(312) 286 00 10 <%2B90%28374%29%20262%2090%2091>

muhammet(dot)kurtoglu(at)bisoft(dot)com(dot)tr <caner(dot)olkan(at)bisoft(dot)com(dot)tr>

16 Eki 2025 Per, saat 15:46 tarihinde Brian Crockard <bcrockard(at)yahoo(dot)com>
şunu yazdı:

> You may want to look into an IBM product called InfoSphere Data
> Replciation (CDC)
>
>
> https://www.ibm.com/docs/nl/idr/11.4.0?topic=requirements-supported-source-targets
>
> It will replicate data from DB2 to PostgreSQL. You can set it up to
> actively replciate the data and keep it consistent. Then perform a cutover
> at some point to the new system running against the new replicated
> database. You will then have all of your historical data in the new system.
> We used this on an extremely active system and it hard very few issues.
>
> On Wednesday, October 15, 2025 at 05:15:00 PM EDT, mahamood hussain <
> hussain(dot)ieg(at)gmail(dot)com> wrote:
>
>
> Hi Team,
>
> We are in the process of migrating several DB2 databases to PostgreSQL,
> primarily to reduce the high licensing costs associated with DB2. These
> databases support retail applications (e.g., supermarkets and stores), and
> during peak hours, we anticipate over 100 concurrent connections.
> ------------------------------
> Current Database Profile:
>
> -
>
> Approximately 3,000 tables in total
> -
>
> Around 100 tables contain active data
> -
>
> Most tables have low data volume
> -
>
> A few large tables range from 10 GB to 2 TB
> -
>
> The largest table contains approximately 80 billion rows
>
> ------------------------------
> Migration Approach:
>
> -
>
> We are using Ispirer for code conversion (DB2 to PostgreSQL).
> -
>
> For data migration, we are evaluating Fivetran, but noted that it
> relies on the COPY method for data loading.
>
> ------------------------------
> Questions & Areas Where We Need Guidance:
>
> 1.
>
> Is Fivetran a suitable option for migrating very large datasets (e.g.,
> tables with 80+ billion rows)?
> 2.
>
> Are there any reliable open-source tools for DB2 to PostgreSQL data
> migration that we can use internally, without needing to invest in a tool
> like Fivetran?
> 3.
>
> Are there more scalable or efficient alternatives for both the initial
> load and ongoing/incremental sync to PostgreSQL?
>
> ------------------------------
> Additional Input Requested:
>
> -
>
> What are the key best practices (Do’s and Don’ts) to keep in mind
> during a large-scale DB2 → PostgreSQL migration?
> -
>
> Are there specific PostgreSQL settings or configurations we should pay
> attention to for optimizing performance, especially for large datasets and
> DB2-style workloads?
>
> ------------------------------
>
> We are keen to ensure performance, data integrity, and scalability
> throughout this migration. Any insights—particularly from those with
> experience in similar large-scale PostgreSQL implementations—would be
> highly appreciated.
>
> If this is not the right forum for these questions, please do let me know
> if there is a better place to seek this guidance.
>
> Thanks in advance for your support!
>

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Jean-Christophe Boggio 2025-10-16 13:17:16 Looking for a linux tool to automate PG admin tasks
Previous Message Brian Crockard 2025-10-16 12:45:57 Re: Guidance Requested: Migrating Large-Scale DB2 Databases to PostgreSQL