Question
Capgemini, Sweden
SE
Last activity: 6 Apr 2018 19:26 EDT
Error while executing alter scripts to upgrade oracle database to 6.3 SP1 from 5.5 SP1
Hi All,
Before anyone will ask, I want to tell you all that version 6.3 SP1 was choosen by my client instead of Pega 7.
When we are executing alter script to upgrade database it fails to update 2 tables 'pr4_fieldvalue' and 'pr4_rule' throwing below error for columns 'pzrulesetversionmajor', 'pzrulesetversionminor' and 'pzrulesetversionpatch'.
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at "PEGA_XX.TRPR4_FIELD_VW_UPD",
line 67 ORA-04088: error during execution of trigger 'PEGA_XX.TRPR4_FIELD_VW_UPD'
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at "PEGA_XX.TRPR4_RULE_VW_UPD",
line 67 ORA-04088: error during execution of trigger 'PEGA_XX.TRPR4_RULE_VW_UPD'
Kindly suggest how to fix it.
Thanks,
Kausar
**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.
Accepted Solution
Pegasystems Inc.
IN
We do not recomend to use the Pega 6.3 upgrade.
However this issue looks like you have customized the column sizes for Pega Rules tables and the trigger is using the default column sizes which is causing this issue.
To overcome this issue you have to manually find the rule table customizations and update the triggers with the appropriate column sizes.
Cognizant
IN
Please inform the client that there are no browsers available in the market that can support an application running on PRPC 6.3SP1. As such upgrading to Pega7 is the only option we have.
Right now Microsoft supports only IE11 / EDGE. Both of them are not suitable for 6.3SP1 applications.
https://pdn.pega.com/prpc-and-pega-7-platform-internet-explorer-compatibility-matrix
Accepted Solution
Pegasystems Inc.
IN
We do not recomend to use the Pega 6.3 upgrade.
However this issue looks like you have customized the column sizes for Pega Rules tables and the trigger is using the default column sizes which is causing this issue.
To overcome this issue you have to manually find the rule table customizations and update the triggers with the appropriate column sizes.
Tata Consultancy Services
IN
Hi Dhev,
Thanks for the suggestions. The issue has been fixed now. We will connect with you when we need further guidance.
Regards,
Sumeet