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 1v9NMw-00H2VB-KC for pgsql-admin@arkaria.postgresql.org; Thu, 16 Oct 2025 12:46:10 +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 1v9NMv-00Cemf-EK for pgsql-admin@arkaria.postgresql.org; Thu, 16 Oct 2025 12:46:08 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1v9NMu-00CemW-Mo for pgsql-admin@lists.postgresql.org; Thu, 16 Oct 2025 12:46:08 +0000 Received: from sonic304-21.consmr.mail.ne1.yahoo.com ([66.163.191.147]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1v9NMn-0025vn-0v for pgsql-admin@lists.postgresql.org; Thu, 16 Oct 2025 12:46:06 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1760618758; bh=EAMDrYkDNbAm+ZYw0SfR0zBDLVN2LjjixkJclBQ3DIY=; h=Date:From:To:In-Reply-To:References:Subject:From:Subject:Reply-To; b=aH7rl9GGJ7sVqu4pfzuHD6+ZFTAkbGy9ShpBWZ5mUSuoyvOeD8vSRXjb8BbB9BxNBZdh/k4KTM+7o6le3m2m/tLhxfV0rZh3JNI+RxDJGhzB9NvzI5ZchzxKgvTDYFtow5cb1Tmzgejpb2NCsbViHohWsWAPWGbJqefB7ilrzMLKtMzqSRMOF5IqzR8cp9V+dQj1iJtHmC+PA0UO05Crt8knWtcQwgFba9QWDg+YWagInKYQ5O4+5K5wZujGnTaGd/33LODs8U5hO88DlD6LY4h0MQMS1tF+6dHvi7sY9nMUhVt+jvGKWKoJJcxf2UswDsMQPbabp1FQBtA/9ChxaQ== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1760618758; bh=2E6OHaMU/e2SVX6ekNrJLPfEkUBgQ8AX5OZhz5geW4c=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=Q18Wp3qi8DPfSzm10JSHI6u5wnkYt4ne+Z5oFD/6ec7SbzAXrNBCk8/p7EN0BaSNLBvCt98VHgUlHyMzufJa7UN8OYf8/IOj0owLBCd3l/Wo/nPgASDpWgTZegu7ecMIc5Wx7s5VB0G0Ra+RcWmm8huv/ePOznkCOwwFIZA0U8DRKNgsRwFHOFVdVrrXsl6w8N3a7pZ0GKlQ6zyaMoTxkN67ByGcJy3LVo8jpdyMY2r3w4NcH9GkC0QsJnCHc6xuX99ajAz7yFg9L1TG/DKm7FUJeGDOyzy8UEpZb4AzFzNZMIjEnDUt7fSyTcmUc3CiGG9JCksgjj2yPh8PFAlQJQ== X-YMail-OSG: W0hsa2kVM1k8F7RSmsBEf2d0OY7Em4BHZwEfHggJtr6uyZ.SlrLtnhGA1HBT1fV HmsRD._xT0qcbzK7pyqzrHbMvfIKt8xA8biNdNB.BAPnfhVaJpHwwzt2Q3yFE2UNuZzdD1q6XJ7y pWjiBnQCOuwZc6NPXEj7CZSYNGxkh4DfWEb7jBdWVsaDdTNxmoYaDqe0OZKpJTva0z8dmKx9bDof mN0_Noz6dJemmeyrNQf7ULkRgTJ5yL3K6MUE5rlIxPruPImNY8XeusaT1aqCCZTqz1mtEWoiHd2D GW6NPDb98.cBE66vAmuRUYLUfEDdbV1UUWiUoc0bEYcMjxGSTOrJ1Yj5TLbm5otHeu8iB5sAUro3 ZgtJTPZmBtBOVelkVyRFnfdLA7DNII_.vuBUktcRVYxCAF84ppme20VbLqPJmHWkoDtETGqROkqq qgqUfAHKYyyKnV7ILZK1SCpEKX0eP1Q9.nB8ZB2dqORnML8zaL5mFEuoqVrG2_96No8pVyXnwh0Q GXxsk4FqhwMRVXYw3GKYQ.UKp4VF0ACDM3NyXI8pYhy6KbWGoAIsW_JAM5DyylMlkwgFJNXqX8bT xc0s9WO0spPs_ESoWfRRPVuf08KvngwXGkLBCrsbTbMYR.T7SsONTwD2La5ncoOg8YHqCofz1uIH _XWVaB6T8WvwZ72YLxxPqKcD_atNO2SF5hYWfWtyoryxQo186ge.Qq_2Y5.Y5JEdCRAUsMbbfhx0 gPMhItfgz4C91xwqyTypBdVHNePt5XxdlguM6T1Hz5z5vivWEXjIgN.ncxjqrHKTtM.UiSDW8Lzg L8IYWOde0evraJAMJpAzEs3bwF3VsfsSSgVarHZGl9yuzvT3gPP3iCgd1hpIHyL9V0VsS9_9nJOe R4KFAX24EPA0rAks26fmlz0rME1y6MhT3BiAkfBaYtUmx0REbWkCWq_wKNrhxUw8TDa.6CyKNiGE zwwq6WUuvoKm0byirSR45S4z7WIab600S4g26S944Frri2h_YM5OMye5Eu2r9VT.VECQqZCZdSrw GwZlrLlReMqXLgBe3wtu1YMayDv_05vHsPyNFWWUJAHxH9jbY1sOnRQSZPgDLiPj.k_kX8fK9kMW RwIclaN063IERvwF0ykFrnztJO1GhTGbq0u.5eNwpJYkdx6Lx5tenyJlSBOBkjFlGbgdXkXUTVHx lIjjMbccAThBSwzwBPlOHjGKmYHXUf0.W3u9f1M.fcZ9Xpiefcxo0TpDRdBhhXJ.SravQDLCUNs9 hWZwM5TS4iTyj28wuD.r56x_f4SpBK.Ld6ITYTkkA2znffrgc.1LLnlR40aPqa2C.DbCmuO4MTFd MWcSeP49wD5oJ8xy2MgkPzMSyW.p6zCVxfdh_f5nZh5k.Y77C3olyMnG5WuEpiGPWh4yn8lg2jyA 0pBQEznYg50lLcr3jQhMExPOI1HYNQ0v7MIlv2PyD0PqGZaelQuI_gHv2zJy8sZ4uTFeZ36p4BYP N_sM8o19R_aku20vOMTiTyQ79uvCoVS6eRP2IlefCfWD.M765mNI6n8BqCDSz3aAV4H.WgyPAdcT 2tB3HtlyKy8iNcdYSamvBsxmZgQb3WJgqsjJSkFat6Aa8uWFQeSPedTPtUoKURmdNcPh0iOhJhVI 6KtQ3viYOtQ_eDViTZMlJIC_5qt7jzuJdKTSTwi1OSARPNY7VCpMbaE_PK76oOGW2CqRBQhCLYzE IrTOgzoA2uSt2meJIfAK8hzhAA2YD.KDp9sgfqf9favdSGXN2NcB2NjUNZS2CRnLr39144i45gyd QG8Y75H8VNKGvPnFrZ1FFJNIWaa1sW4EtplTD3RUvmnrjZXES1Cz8IWZn90pyx9Uwqur4HZrMu3A YdeUNzlNt.fL5YrTXbBimbV2BlnrIwHE.cXBLLAdcWeDfRBj7PtNVdERHS6WSoG.TrikqsqtqCeW Gbz.XMt4u4HnjNcnnYBH6T3g3aABjJPneoDhT.FX_ES8a3tyqzo8I6XAVaVL.WupQXnoNfESeWfa WJv.FWh5uPFg0Yt.KfEUWBiVkQjYHVD4K929Blf9DkiEpC15FDG457HTd9ATJB0OQzGAqDQBP4yr jn39cOjOwpI5uWLWjL.Jiqz.ztn.4mGyOxiFOO0fXlEvc7QtMNwlmnyNcUbGr8I40xtNsxx1_A6p mJNDoxn0lMF.leBMMRoyiaxhuDHebJjRi22DEQnQwQEEFeqFyvckvK73Uj0n6OQ85yh6hDQEeUsH r5x30WaCi8dqiWfHtvjSiTrYa9pEQRRrAh2492Lx5jEsxDfCNDcRdj31KgHVs90xDDCd_rDkLQBx zgairD.5HVDlQFDELu5XV X-Sonic-MF: X-Sonic-ID: 7d2a47e1-e6f9-4211-8b57-43d6c95d5962 Received: from sonic.gate.mail.ne1.yahoo.com by sonic304.consmr.mail.ne1.yahoo.com with HTTP; Thu, 16 Oct 2025 12:45:58 +0000 Date: Thu, 16 Oct 2025 12:45:57 +0000 (UTC) From: Brian Crockard To: Pgsql-admin , mahamood hussain Message-ID: <1915052734.3603827.1760618757611@mail.yahoo.com> In-Reply-To: References: Subject: Re: Guidance Requested: Migrating Large-Scale DB2 Databases to PostgreSQL MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_3603826_1301813784.1760618757610" X-Mailer: WebService/1.1.24562 YMailNovation Content-Length: 7302 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk ------=_Part_3603826_1301813784.1760618757610 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable You may want to look into an IBM product called InfoSphere Data Replciatio= n (CDC) https://www.ibm.com/docs/nl/idr/11.4.0?topic=3Drequirements-supported-sourc= e-targets It will replicate data from DB2 to PostgreSQL. You can set it up to activel= y 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 w= ill then have all of your historical data in the new system. We used this o= n an extremely active system and it hard very few issues.=C2=A0 On Wednesday, October 15, 2025 at 05:15:00 PM EDT, mahamood hussain wrote: =20 =20 =20 Hi Team, We are in the process of migrating several DB2 databases to PostgreSQL, pri= marily to reduce the high licensing costs associated with DB2. These databa= ses support retail applications (e.g., supermarkets and stores), and during= peak hours, we anticipate over 100 concurrent connections. Current Database Profile: =20 - =20 Approximately 3,000 tables in total - =20 Around 100 tables contain active data - =20 Most tables have low data volume - =20 A few large tables range from 10 GB to 2 TB - =20 The largest table contains approximately 80 billion rows Migration Approach: =20 - =20 We are using Ispirer for code conversion (DB2 to PostgreSQL). - =20 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: =20 - =20 Is Fivetran a suitable option for migrating very large datasets (e.g., tabl= es with 80+ billion rows)? - =20 Are there any reliable open-source tools for DB2 to PostgreSQL data migrati= on that we can use internally, without needing to invest in a tool like Fiv= etran? - =20 Are there more scalable or efficient alternatives for both the initial load= and ongoing/incremental sync to PostgreSQL? Additional Input Requested: =20 - =20 What are the key best practices (Do=E2=80=99s and Don=E2=80=99ts) to keep i= n mind during a large-scale DB2 =E2=86=92 PostgreSQL migration? - =20 Are there specific PostgreSQL settings or configurations we should pay atte= ntion to for optimizing performance, especially for large datasets and DB2-= style workloads? We are keen to ensure performance, data integrity, and scalability througho= ut this migration. Any insights=E2=80=94particularly from those with experi= ence in similar large-scale PostgreSQL implementations=E2=80=94would be hig= hly appreciated. If this is not the right forum for these questions, please do let me know i= f there is a better place to seek this guidance. Thanks in advance for your support! =20 ------=_Part_3603826_1301813784.1760618757610 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
You may want to look into an= IBM product called InfoSphere Data Replciation (CDC)


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 cuto= ver at some point to the new system running against the new replicated data= base. 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. <= /div>

=20
=20
On Wednesday, October 15, 2025 at 05:15:00 PM EDT, maha= mood hussain <hussain.ieg@gmail.com> wrote:


=

Hi Team,

We are in the process o= f migrating several DB2 databases to PostgreSQL, primarily to reduce the hi= gh licensing costs associated with DB2. These databases support retail appl= ications (e.g., supermarkets and stores), and during peak hours, we anticip= ate 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 Wher= e 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!

------=_Part_3603826_1301813784.1760618757610--