Question
Accenture
SG
Last activity: 7 Aug 2023 10:34 EDT
Pega 8.6: Post upgrade existing SQL query results in pyCommitError
|
FAIL |
|
|
Step Status Info |
Problem saving instance of class : code: -907 SQLState: 27000 Message: An attempt was made to modify the target table, "ABC", of the MERGE statement by constraint or trigger "RESET_CASECOUNT_INSERT".. SQLCODE=-907, SQLSTATE=27000, DRIVER=4.26.14 |
Instead of INSERT and UPDATE statements in PRPC 6, Pega 8.6 is now generating MERGE statements which displays pyCommitError in many places in the system after upgrade.
The other article suggest to edit prconfig file. But how to maintain in DSS. Means what should be the configuration of DSS.
<env name="classmap/usemergestatement" value ="false" /> <env name="database/batchupdates" value="-1" />
Related article: https://community.pega.com/support/support-articles/post-upgrade-existing-sql-query-results-pycommiterror
|
|
|
|
Accepted Solution
Updated: 26 Aug 2021 0:07 EDT
Accenture
SG
Hi Vikash,
Thanks for the answer. After adding the DSS setting and later restarting the server, the query is working fine.
Now I am able to get the INSERT query for new addition.
Thanks again :)
Updated: 20 Aug 2021 0:53 EDT
Blue Rose Technologies
NL
@Yasmin Tarannum Below is the DSS setting for the prconfig you are looking for:
Owing Ruleset: Pega-Engine
Setting purpose: prconfig/classmap/usemergestatement/default
Value: false
Accepted Solution
Updated: 26 Aug 2021 0:07 EDT
Accenture
SG
Hi Vikash,
Thanks for the answer. After adding the DSS setting and later restarting the server, the query is working fine.
Now I am able to get the INSERT query for new addition.
Thanks again :)
Pegasystems Inc.
US
@Yasmin Tarannum Shutting off merge is NOT something that you should be doing or at least not doing without serious consideration and testing. You are shutting it off for your entire environment and it will have a significant performance impact that you need to be thinking about. That article was written for 7.1.7 with regards to an issue with foreign keys and there are other options in later versions of pega to deal with issues like that. You need to consider context when looking at solutions.