Discussion
Accenture Services Pvt Ltd
IN
Last activity: 6 Apr 2018 19:26 EDT
Upgrade from PRPC 6.3 to PRPC 7.1.8
We are upgrading Pega platform from PRPC6.3 SP1 to PRPC 7.1.8. In one environment we successfully completed upgrade from PRPC6.1 SP1 single schema to PRPC7.1.8 split schema.
In order to update another environment we imported the previously upgraded PEGARULES schema and upgraded only the PRPCDATA one with dataOnly set to true.
We have performaed the below steps
1. created PRPCRULES schema in the second environment by importing the PEGARULES schema dump from previously upgraded environment.
2. created PRPCDATA schema in the second environment by importing the dump of PRPC6.3 SP1 which contains both data and rules.
3. configured the setupDatabase.properties files like below
pega.jdbc.driver.jar=/data01/app/oracle/product/11.2.0/db_1/jdbc/lib/ojdbc6.jar
pega.jdbc.driver.class=oracle.jdbc.OracleDriver
pega.database.type=oracledate
pega.jdbc.url=jdbc:oracle:thin:@x.x.x.x:1521/prpcprod
pega.jdbc.username=prpcdata
pega.jdbc.password=xxxxxx
rules.schema.name=prpcrules
data.schema.name=prpcdata
4. executing the upgrade script with --dataOnly true
The process fails with the below error
Caused by: java.sql.BatchUpdateException: ORA-00001: unique constraint (PRPCRULES.PR_DATA_RESTORE_PK) violated
Please suggest.
**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.
Pegasystems Inc.
IN
Hi,
Truncate the PR_DATA_RESTORE table and try with the data upgrade.
PR_DATA_RESTORE table is used for reversing an update and this feature is introduced in Pega 7.1.7 onwards. This table captures all the data instances which got imported during the Data Upgrade process.
When we perform the reversibility then it gets all the records from this table and removes from the Data schema. Reversibility is only supported if you are already on Pega7.1.x and doing an update to Pega 7.1.y.
As you are performing the data upgrade second time it is trying to capture all the data instances one more time in the PR_DATA_RESTORE table and failing with unique constraint violation error.
Thanks,
Dhev
Accenture Services Pvt Ltd
IN
Hi Dhevendra,
Not sure if my explanation was clear enough. Just to clarify once again, we are not upgrading data second time, it's a diffetent environment where we are upgrading data.
Step 1. In one environment (development) we have upgraded successfully from single schema PRPC6.3 SP1 to split schema PRPC 7.1.8.
Step 2. Now in another environment (TEST), we have created one schema (PRPCRULES) and imported the upgraded 7.1.8 Rules schema (export taken from upgraded 7.1.8 development environment as mentioned in step1) to TEST environment. After that we are running --dataOnly upgrade in the PRPC 6.3 original schema of TEST environment which has both data and rules to upgrade the data.
So kindly confirm, in this scenario we have to do the same steps that you suggested (truncate of PR_DATA_RESTORE)?
Pegasystems Inc.
IN
Yes you right. when you have performed DataOnlyUpgrade on first environemnt it is populated the data instances inthe PR_DATA_RESTORE table and when you are performing the Data Only Upgrade on second enviornment pointing to same RULES SCHEMA which got upgraded in first environemnt it is trying to insert same data instnaces and failing with unique key error.
Thanks,
Dhev
Pegasystems Inc.
IN
apart from PR_DATA_RESTORE table you also need to truncate the PR_DATA_PRODUCTS table. PR_DATA_PRODUCTS tabel is also capturing the ML reversibility information which need to be truncated.
Thanks,
Dhev
Cognizant
IN
Could you please explain the purpose of PR_DATA_PRODUCTS. How does it come into picture during an upgrade ?
NIIT Technologies Limited
AU
From 7.1.7, PRPC updates(not upgrade) are reversible. Both update and upgrade collects metadata about new/updated rules to support reversibility. PRPC uses PR_DATA_PRODUCTS and PR_DATA_RESTORE tables to store this metadata.
Unique constraint error appears as same data is being inserted into PR_DATA_PRODUCTS during second upgrade, so it needs to be truncated.