Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1v9NRH-00H3vD-3O for pgsql-admin@arkaria.postgresql.org; Thu, 16 Oct 2025 12:50:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1v9NRF-00CiaB-Ps for pgsql-admin@arkaria.postgresql.org; Thu, 16 Oct 2025 12:50:36 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1v9NRF-00Cia3-9m for pgsql-admin@lists.postgresql.org; Thu, 16 Oct 2025 12:50:36 +0000 Received: from mail-ed1-x536.google.com ([2a00:1450:4864:20::536]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1v9NRB-002Wc0-07 for pgsql-admin@lists.postgresql.org; Thu, 16 Oct 2025 12:50:35 +0000 Received: by mail-ed1-x536.google.com with SMTP id 4fb4d7f45d1cf-63c0e774250so87029a12.1 for ; Thu, 16 Oct 2025 05:50:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bisoft-com-tr.20230601.gappssmtp.com; s=20230601; t=1760619032; x=1761223832; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=6qBlSHRggF10YCm5hXiiuzJvvpf54pS4WLT7SaYdPrg=; b=BWVSbp1a6IjV2O1gxNQGv9mwy9IeLhNtgcQUygem9UhxsmC90EphaOHN3czthiemBD w4WUgk2O4Yr6RS+yEBhQVsHCrZp4dBRaMGL/u1gUhiW4H8a2kGwlagr1TdFw6RHRXI2E vDmt/jfvH1bXgydw9bFltCYoeksggPAdnlDmp+zxg1hXWaHBY2uvF8lJr4mNvn1Ra30s NgHCqPs9L9/QBUwl/uYlRC6XjGMdcyfzcdAwfZJJHak8W6O3U1gWS4FmC0pnAd+tUsaT /ef06aDxpaSIVIVC+fyXFvTUXWnEsQLrOPQjjp6zHsM6RcAhBojzaBva7rzeIAEpicxQ 8RIg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1760619032; x=1761223832; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=6qBlSHRggF10YCm5hXiiuzJvvpf54pS4WLT7SaYdPrg=; b=FcQm0VnExADEraDev2yHW6NbJyZBTi6psqrThc3wRH9aruleIs/GGmyQLEHk8939Yl vG9qfttOGa0/KpOYX7KgMcxeqovKGNCWNEqcvqAOHkAYSFx/FO6/WafpyRrTPkgZFN44 ET40gNJ6oGV3lFOoqCw4bl63r0Y+ntdXYlGbsuNPkpvmAmkiTxO+Di0uVttMmNso7Cci 5QDxocZo56mGpixEeu2SZGKQEk7pmNYN92a2Mpe8lYpsjhfMJ7B8m1i26KRRNPJEVJo2 nL3gbKk/NziMl/ZOJie9B94HvUWGGTgzkunsUJD9wrUGccEZnkgruFDCB8lQupbMvDr/ Qq+w== X-Gm-Message-State: AOJu0YwDZ+AyHfo9mMqSywTcehDIklEw54nx6Nd/ccfFUbGrfSlWSYTu 6mQkhMr+cYARqRxX++jjt+C1mFX/bbnEk4fBr3hfK6m9dUZ8MFQeWt4yUmR0EYziAEVukgrTrwq l0jSHO2LLz4ZQ23bez1bF/T7+zmzjw2dzc00usZeHPw== X-Gm-Gg: ASbGncsOPfjPm0oJs2GrZKZI+q1iBdyONHBrL866JTvY5antx/Dpg0+XmfAJTBN63KR b+6M+Qyj679nuSwpN6U2ss0yL0aFscMVTvX3XO1PEhOUCWU+aNpz07+NR39ikHSDy0yWz7HTOua kUZhem4mPZyonmKflLaUe115nULT8sSZvop9ytL4KVDsfSLClom0KoTACfc52VT+p9Y0TI62N1T GjsE6mMbOjSIgTa4TyG6/pAQoFap0dgLqUPSVNCXaIe3W20eqo4LQ3QOnY= X-Google-Smtp-Source: AGHT+IGBIUx+3Icp6aY1mFIzCX4tCBa6VrbeDg4oJ7UCpUrXKHL0ZxTNRe953W9+MmFwTLRrhcGsFNmcWqQomvq4Kyg= X-Received: by 2002:a17:907:7283:b0:b50:5956:482b with SMTP id a640c23a62f3a-b50ac1c38d2mr1879234966b.7.1760619031845; Thu, 16 Oct 2025 05:50:31 -0700 (PDT) MIME-Version: 1.0 References: <1915052734.3603827.1760618757611@mail.yahoo.com> In-Reply-To: <1915052734.3603827.1760618757611@mail.yahoo.com> From: =?UTF-8?Q?Muhammet_Kurto=C4=9Flu?= Date: Thu, 16 Oct 2025 15:50:20 +0300 X-Gm-Features: AS18NWCKINnqjzWZiqfiWqOSpUjg201Sfjnij_3cyN8dr5yZbw_K3H_t10SP95w Message-ID: Subject: Re: Guidance Requested: Migrating Large-Scale DB2 Databases to PostgreSQL To: Brian Crockard Cc: Pgsql-admin , mahamood hussain Content-Type: multipart/alternative; boundary="000000000000fa77070641460f79" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000fa77070641460f79 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Try symetricds *Muhammet KURTO=C4=9ELU* 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.kurtoglu@bisoft.com.tr 16 Eki 2025 Per, saat 15:46 tarihinde Brian Crockard =C5=9Funu yazd=C4=B1: > 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=3Drequirements-supported-sou= rce-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 cutove= r > 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 syste= m. > 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.ieg@gmail.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), an= d > 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 t= ool > 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=E2=80=99s and Don=E2=80=99ts) to k= eep in mind > during a large-scale DB2 =E2=86=92 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=E2=80=94particularly from those w= ith > experience in similar large-scale PostgreSQL implementations=E2=80=94woul= d 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! > --000000000000fa77070641460f79 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Try symetricds
<= div dir=3D"ltr">

Muhammet KURTO=C4=9ELU<= br>

T:=C2=A0=C2=A0+90(312) 220 12 20

=

F:=C2=A0=C2=A0+90(312) 286 00 10<= /span>

muhammet.kurtoglu@bisoft.com.tr=C2=A0

=C2=A0=C2=A0=C2=A0=C2=A0

<= /div>





<= /div>

16 Eki 2025 Per, saat 15:46 tarihinde Brian Crockard <bcrockard@yahoo.com> =C5=9Funu = yazd=C4=B1:

=20
=20


Hi Team,

We= are in the process of migrating several DB2 databases to PostgreSQL, prima= rily to reduce the high licensing costs associated with DB2. These database= s support retail applications (e.g., supermarkets and stores), and during p= eak 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:<= /h3>

  • 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., t= ables with 80+ billion rows)?

  2. Are there any reliable open-source tools for DB2 to PostgreSQL data migr= ation 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 l= oad and ongoing/incremental sync to PostgreSQL?

Additional Input Requested:=

  • What are the key best practices (Do=E2=80=99s and Don=E2=80=99ts) to kee= p in mind during a large-scale DB2 =E2=86=92 PostgreSQL migration?

  • Are there specific PostgreSQL settings or configurations we should pay a= ttention to for optimizing performance, especially for large datasets and D= B2-style workloads?

We are keen to ensure performance, data integrity, and scalabil= ity throughout this migration. Any insights=E2=80=94particularly from those= with experience in similar large-scale PostgreSQL implementations=E2=80=94= 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 g= uidance.

Thanks in advance for your support!

--000000000000fa77070641460f79--