Discussion
Pegasystems Inc.
IN
Last activity: 6 Apr 2018 19:26 EDT
ORA-12899: value too large for column length while performing rules Upgrade (Step after rules migration).
Rules upgrade failed with below error while upgrading from PRPC 61 SP1 >> Pega 719
Log:
[java] Caused by: com.pega.pegarules.pub.database.DatabaseException: Database-General There was a problem getting a list 12899 72000 ORA-12899: value too large for column "RBSI_RULES"."PR4_RULE_RULESET"."PYLABEL" (actual: 67, maximum: 64)
[java]
[java] From: (A9892FDA977B1BDD156DD46C0F44BA93B)
[java] SQL: INSERT INTO RBSI_RULES.pr4_rule_ruleset (PXCREATEDATETIME , PXCREATEOPERATOR , PXCREATEOPNAME , PXCREATESYSTEMID , PXHOSTID , PXINSID , PXINSNAME , PXOBJCLASS , PXSAVEDATETIME , PXUPDATEDATETIME , PXUPDATEOPERATOR , PXUPDATEOPNAME , PXUPDATESYSTEMID , PYLABEL , PYRULENAME , PYRULESET , PYRULESETNAME , PYRULESETTYPE , PYRULESETVERSIONID , PYVERSIONSECURE , PZCHECKSUM , PZINSKEY , PZPVSTREAM , pxCommitDateTime) SELECT PXCREATEDATETIME , PXCREATEOPERATOR , PXCREATEOPNAME , PXCREATESYSTEMID , PXHOSTID , PXINSID , PXINSNAME , PXOBJCLASS , PXSAVEDATETIME , PXUPDATEDATETIME , PXUPDATEOPERATOR , PXUPDATEOPNAME , PXUPDATESYSTEMID , PYLABEL , PYRULENAME , PYRULESET , PYRULESETNAME , PYRULESETTYPE , PYRULESETVERSIONID , PYVERSIONSECURE , PZCHECKSUM , PZINSKEY , PZPVSTREAM , CURRENT_TIMESTAMP FROM RBSI_RULES.pr4_rule WHERE pxObjClass IN ('Rule-RuleSet-Version') AND pzInsKey NOT IN (SELECT pzInsKey FROM RBSI_RULES.pr4_rule_ruleset)
[java] SQL Inserts:
[java]
[java] Caused by SQL Problems.
[java] Problem #1, SQLState 72000, Error code 12899: java.sql.SQLException: ORA-12899: value too large for column "RBSI_RULES"."PR4_RULE_RULESET"."PYLABEL" (actual: 67, maximum: 64)
[java]
[java] at com.pega.pegarules.data.internal.access.ExceptionInformation.createExceptionDueToDBFailure(ExceptionInformation.java:262)
[java] at com.pega.pegarules.data.internal.access.DatabaseImpl.list(DatabaseImpl.java:6283)
[java] at com.pega.pegarules.data.internal.access.DatabaseImpl.executeRDB(DatabaseImpl.java:6676)
[java] at com.pega.pegarules.data.internal.access.DatabaseImpl.executeRDB(DatabaseImpl.java:6632)
[java] at com.pega.pegarules.data.internal.access.DatabaseImpl.executeRDB(DatabaseImpl.java:6613)
[java] at com.pega.pegarules.data.internal.access.Migrator.migrateClassInstances(Migrator.java:83)
[java] ... 33 more
[java] Caused by: java.sql.SQLException: ORA-12899: value too large for column "RBSI_RULES"."PR4_RULE_RULESET"."PYLABEL" (actual: 67, maximum: 64)
[java]
**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
As there is known issue in resume option of upgrade utility in ML 9, we will not be able to apply the fix and re initiate the rules upgrade over the same schema when we see error.
In order to bypass the resuming upgrade using resume.sh, we have followed below steps
- Generated DDL for Upgrade using command ( --generateddl --action upgrade)
- Apply the DDL manually in rule schema
- Apply alter statement over table column for fixing specific issue before running upgrade utility
ALTER TABLE RABO_RULES.PR4_RULE_RULESET MODIFY PYLABEL VARCHAR(128);
- Run Upgrade utility (upgrade.sh) with option to bypassing schema changes since we applied DDL manually( bypass.pega.schema=true )