The way of migrating database from DB2 to Oracle
Since PEGA 24 won't support DB2, we're trying to migrate our PEGA database from DB2 to Oracle.
And we've consoultanted the Oracle expoerts, got questions as below:
- Is there a recommended standard procedure for migrating the database? Whether the database should be decided at the beginning or can be changed after going live?
- Supportted Oracle database's version? Whether the CDB architecture is supported or not? If yes, which versin of CDB is supported?
- For the database objectes created by Paga, whether the data structure mapping between DB2 and ORACLE can be directly correlated by name. If not, is there a mapping table available?
Appreciate a lot if anyone can help.
Accepted Solution
Updated: 4 Sep 2025 21:21 EDT
HCA Healthcare
US
Mediatek Inc. China
CN
Thanks very much for you comments, it helps a lot.
We've successfully migrated our development environment from DB2 to Oracle.
Just as you've mentioned, we installed a Oracle version PEGA 23, and then copied the OOTB database objects (indexes, functions...). For our self-fined objects, we used piece of shell script to export the DDL and then copied to Oracle DB.
Currently, the only problem we're facing is the large volumn data of our production environment.
We have about 4TB data in our production environment, and we don't have enough downtime to do the data migration.
We probably will use database tools like GodenGate to do the data sync.
Thanks anyway for you help.
@GAVINHSU
plan the DB switch as part of your 24.x upgrade cutover, not after go-live; stand up Oracle to the exact versions listed in Pega’s Platform Support Guide for 24.2 (Oracle 19c is supported; check the guide for 21c/23ai), then create a PDB and the 3 Pega schemas rules, data, and CustomerData, which is Pega’s standard split-schema layout; install Pega into Oracle using Pega’s delivered DDL/scripts for Oracle rather than trying to “map” DB2 objects names often look similar but types, indexes, and constraints aren’t 1:1 and should come from the Oracle DDL; migrate data using Pega’s migration utilities or database tools (expdp/impdp) in the target PDB, then update JDBC settings, reindex search, and validate listeners/queue processors; yes, Oracle multitenant (CDB/PDB) is supported and preferred since Oracle 21c multitenant is the only architecture, deploy Pega into a PDB under your CDB; finally, run smoke/perf tests and fix any DB-specific SQL (Connect-SQL, reports) before opening traffic. For the authoritative support matrix and any 24.x notes, see the Pega Platform Support Guide and install docs; for multitenant requirements, see Oracle’s CDB/PDB guidance.