We are upgrading PRPC 6.2 to 7.3.1. Upgrade utilities runs for 7 hours. We have all configurations like JVM, system disk space and RAM all as per recommendation. Still its taking 7 hours. No DB2 issues while upgrade of rules is running.
Is 7 hours expected time ? or any tuning opportunities. If this install takes 7 hours, then we have other framework, DBA activities on top of it which will make more PROD down time. we don't want to think about split schema at this time based on pros and cons of it.
Can some one suggest , is there a way to run/install/upgrade 7.3.1 with nominal timing ?? and not 7 Hours
you can use any database tools for migrating the schema from one environment to other environment.
There is no rollback mechansim available. You have to take the backup of your existing production system before doing the upgrade and if something goes terrible wrong you need to restore it. We have not seen any scenario on customers did the rollback as these upgrade process is tested very well in all the lower environments.
can someone share the best practices that are used in testing for Pega 6.2 to to 7.3.1 Upgrade?
We have automated test with selenium for UI with pega 6.2 - however, this is time consuming to change the script to match the changes that came as part of upgrade and also may not cover complete rules and would like to the best practices followed in testing.