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.

Discussion

 Anand Chouti (anandchouti) PEGA Lead System Architect
Pegasystems Inc.
US
anandchouti Member since 2014 14 posts
PEGA
Posted: Apr 18, 2016
Last activity: Apr 6, 2018
Posted: 18 Apr 2016 9:05 EDT
Last activity: 6 Apr 2018 19:26 EDT
Closed

DB Table check list for successful migration

I am upgrading to Pega 7 from prpc6. I am using the split schema approach to divide all the tables into Rules and Data Schema. Once the upgrade is complete using the Command line tools, I need a way to know if the upgrade was successful. I want to know if the right tables with right columns were present in both the Rules and Data Schema. Please let me know if there are any checklists that tell us this.



**Moderation Team has archived post**


This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

To see attachments, please log in.
Updates

Posted: 8 years ago
Posted: 22 Apr 2016 10:02 EDT
Dhevendra Earva (earvd) PEGA Senior Director of Cloud Engineering
Pegasystems Inc.
IN

OOTB there is no such utility exists, please check for the upgrade logs to make sure that upgrade is successful.

You need to run the Optimize schema wizard for clean up of unused tables on both PegaDATA an PegaRULES schema. Upgrade process will automtically moving the right tables to right schema and there is no explict check required.

To see attachments, please log in.
Posted: 8 years ago
Updated: 8 years ago
Posted: 26 Apr 2016 2:28 EDT
Updated: 26 Apr 2016 2:33 EDT
Vigneshwaran Aravindhan (VigneshAravind) Cognizant Senior Technology Architect
Cognizant
IN

Assuming you have not done any DB customizations in V6; you could try a manual comparison between ...

Upgraded P7 App's rules/data schema (Vs) Freshly Installed P7 App's rules/data schema.

ML of the fresh install should be same as the ML of your upgraded application; that is we should not be comparing a 7.1.7 with 7.2.0
Do a cross check randomly on various rule/data tables.

Few tips that might help ...

Three V6 rule tables have been dropped in V7

  1. pr4_history_rule
  2. pr4_log_rule_usage
  3. pr4_log_rule_usage_details

Three new columns have been added to all the V7 rule tables. These are not the only columns; some tables could have more additions.

  1. PZCHECKSUM
  2. PXCOMMITDATETIME
  3. PXSAVEDATETIME

The following rule tables were newly added in V7

  1. pr4_rule_file_binary
  2. pr4_rule_requirement
  3. pr4_rule_ruleset
  4. pr4_rule_library
  5. pr4_rule_message
  6. pr4_rule_testcase
  7. pr4_rule_usecase
  8. pr4_rule_declarepages
  9. pr4_rule_delegationconfig
To see attachments, please log in.

Related content:

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