Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Sudhaharan Rajendran (sudhaharr)
GDIT

GDIT
US
sudhaharr Member since 2008 16 posts
GDIT
Posted: Mar 24, 2018
Last activity: Aug 7, 2018
Posted: 24 Mar 2018 23:30 EDT
Last activity: 7 Aug 2018 0:31 EDT
Closed

PRPC 6.2 SP1 to 7.3.1 Upgrade takes 7 hours

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

To see attachments, please log in.
Updates

Posted: 7 years ago
Posted: 13 Apr 2018 2:59 EDT
Dhevendra Earva (earvd)
PEGA
Senior Director of Cloud Engineering
Pegasystems Inc.
IN

You can use the split schema upgrade process to reduce the production downtime. The best approach will be use the lift and shift approach.

  1. do the out of place split schema upgrade in pre-prod envionemnt
  2. take a database dump of rules schema
  3. lock your production rule sets and take a back of the production ruelesets
  4.  Copy the pre-prod rules schema to production
  5.  run generate rules schema objects and data only upgrade steps in prduction 
  6.  import all your upgrade fixes rulesets including production rulesets

this approach should reduce your upgrade time to less than 1 hour.

 

To see attachments, please log in.
Posted: 7 years ago
Posted: 16 Apr 2018 8:46 EDT
Sudhaharan Rajendran (sudhaharr)
GDIT

GDIT
US

Thanks for your response.  Great to know upgrade takes less than hour.

Step 2, 4, 5 - what is the Database used with this approach ?

How about fallback - in case we need to backout the upgrade and switch back to original version of pega 6.2 ?

 

To see attachments, please log in.
Posted: 7 years ago
Posted: 17 Apr 2018 1:29 EDT
Dhevendra Earva (earvd)
PEGA
Senior Director of Cloud Engineering
Pegasystems Inc.
IN

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.

To see attachments, please log in.
Posted: 7 years ago
Posted: 7 Aug 2018 0:03 EDT
Priya Kanagaraj (PriyaK4460)
AIG Inc

AIG Inc
US

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.

Thanks in advance.

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice