Is Pega reinstallation required when we migrate the DB from DB2 to PostgreSQL

General
, ,
1

We have recently migrated our Pega application Database (Pega Infinity 24.1.1) from DB2 to PostgreSQL without reinstalling Pega. We used the generateDDL.sh script from the current Pega installation directory to generate DDL for the Pega system DB objects, created these objects in PostgreSQL using those DDLs, and migrated the data for these Pega system tables from DB2 to PostgreSQL.

We then updated the database properties file with PostgreSQL database details, made required database changes in the webfarm configuration, and after redeploying the application, successfully connected to the new PostgreSQL database from Pega. The application functionalities are working fine.

However, we would like to know if there are any potential risks or issues with this approach, given that we skipped the fresh Pega installation for this database migration, or if the approach we have followed is sufficient for the DB migration, as we have not observed any issues so far.

2

No, a full Pega reinstallation is usually not required just because the database moved from DB2 to PostgreSQL, as long as the target PostgreSQL version is supported and the new schema was created correctly with Pega-generated DDL. What matters is that the migrated database matches Pega’s expected structure and that all database-specific objects, indexes, functions, and validations are completed properly. Since your application is already connecting and working after updating the datasource and redeploying, your approach is generally valid. The real risk is not skipping a reinstall, but missing any PostgreSQL-specific schema object or post-migration validation step that may cause issues later in reporting, search, or performance. So treat this as a database migration validation task, not an application reinstall task.