Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Error installing Smart Dispute v7.12 on new PRPC 7.1.7 system

SA-7489

Summary



Using Oracle and a split schema configuration, developers received errors while Importing SmartDisputeBase_07a_rules.jar from SmartDisputeBase_v712.jar

Error Messages



RULE-OBJ-PROPERTY PEGACARD-SD-DEBIT CUSTOMERSLOCATION #20141111T074109.701 GMT Save Failed: Database-General Problem writing an instance to the database 12899 72000 ORA-12899: value too large for column "PEGARULES"."PR4_RULE_PROPERTY"."PYLABEL" (actual: 65, maximum: 64)

RULE-OBJ-PROPERTY PEGACARD-SD-DEBIT DETAILSFORCUSTOMERSLOCATION #20141111T074109.982 GMT Save Failed: Database-General Problem writing an instance to the database 12899 72000 ORA-12899: value too large for column "PEGARULES"."PR4_RULE_PROPERTY"."PYLABEL" (actual: 65, maximum: 64)


Steps to Reproduce



1) Attempt to import SmartDisputeBase_v712.jar

Root Cause



The root cause of this problem is a defect in Pegasystems’ code/rules. Several columns are not large enough to handle the values being inserted by this jar file.


Resolution



In order to correct this issue, please shut down the instance and perform the following database operations:

(If a split schema configuration is in use, these tables should be under the Rules schema.)

alter table PEGARULES.pr_index_reference modify (pxreferencingdescription varchar2(128));
alter table PEGARULES.pr4_rule modify (pyLabel varchar2(128));
alter table PEGARULES.pr4_rule_vw modify (pyLabel varchar2(128));
alter table PEGARULES.pr4_rule_property modify (pyLabel varchar2(128));
alter table PEGARULES.pr4_fieldvalue modify (pyLabel varchar2(128));

In the following DB triggers please change SPtpyLabel VARCHAR (64) to SPtpyLabel VARCHAR (128) and recompile the trigger:

trpr4_rule_vw_upd
trpr4_rule_prop_vw_upd
tr4_field_vw_upd

After doing this, please start the instance. The jar file should now import without issue.

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community 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
Contact us