Upgrade from prpc 6.2 sp2 to prpc 718 - DB2 SQL Error: SQLCODE=-803, SQLSTATE=23505, SQLERRMC=1; PR_SYS_APP_HIERARCHY_FLAT
Has anyone encountered the following error during an upgrade. This occurs when it i attempting to load data into the new rules table that it created. It loaded all the
data from the old to the new schema
DB2 SQL Error: SQLCODE=-803, SQLSTATE=23505, SQLERRMC=1;PEGARULES.PR_SYS_APP_HIERARCHY_FLAT, DRIVER..
**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.
Paypal Inc
IN
Hi,
I assume this error occured during rules migration. Can you please check whether the metadata of the original table and the new table is same ?
Tata Consultancy Services
IN
Hi Rafael. Is the data loaded successfully? Or is the data load not done because of this error? Also, did you encounter any other error during the upgrade process?
New York Life Ins. Co
US
Hi,
No it did not.. We have done the upgrade within all the lower life cycles. It was successful. We are now attempting to upgrade production with has a lot more data..
It did load all the data from current ZZZ.PR_SYS_APP_HIERARCHY_FLAT to the new split schema YYY.PR_SYS_APP_HIERARCHY_FLAT. I am assuming it duplicate key issue is when it attempt to load a new record from the upgrade process. I am not familiar with the internal of the additional records it loads. But I have notices that all the other tables that get split do have additional records inserts.
Thanks, RV
AIG
US
Assuming migrate script execution is going on first time on empty schema. We came across with similar due to page size. Please confirm following are setup as per guide-
1. DB2 databases, the default page size is recommended to be set at 32K.
2. Database users performing the upgrade must have “UNLIMITED TABLESPACE” privileges provided to them.
New York Life Ins. Co
US
Hi,
Yes we have made the those changes. We have done the upgrade within all the lower life cycles. It was successful. We are now attempting to upgrade production with has a lot more data..
It did load all the data from current ZZZ.PR_SYS_APP_HIERARCHY_FLAT to the new split schema YYY.PR_SYS_APP_HIERARCHY_FLAT. I am assuming it duplicate key issue is when it attempt to load a new record from the upgrade process. I am not familiar with the internal of the additional records it loads. But I have notices that all the other tables that get split do have additional records inserts.
Thanks, RV
Cognizant Technology Solutions
US
Below are the only tables will get migrated when you do an upgarde from 62sp2 to pega718.This is a new table in pega 718 PR_SYS_APP_HIERARCHY_FLAT.Your rulebase upgrade may failed at some point.On which step are you getting this error?
PC_INDEX_FLOWREF
PR4_BASE
PR4_FIELDVALUE
PR4_RULE
PR4_RULE_AUTOTEST
PR4_RULE_FILE
PR4_RULE_FLOW
PR4_RULE_PROPERTY
PR4_RULE_RULESET
PR4_RULE_SYSGEN
PR4_RULE_VW
PR_APP_BRANCH_IDX
PR_CHANGELOG
PR_DATA_ADMIN
PR_ENGINECLASSES
PR_INDEX_CIRCUMSTANCE_DEF
PR_INDEX_CSS
PR_INDEX_CUSTOMFIELDS
PR_INDEX_REFERENCE
PR_INDEX_WARNINGS
PR_LINK_USECASE
PR_SYS_CONTEXT
PR_SYS_DECCHG