Related content:

Discussion db2 sql error sqlcode=-614, sqlstate=54008 during upgrade Question Obj-Browse SQL query: Error sqlcode=-302 sqlstate=22001 Question Rules Upgrade - Failed with NoClassDefError - DirectStreamEnvironmentAdapter Discussion Upgrade from prpc 6.2 sp2 to prpc 718 - DB2 SQL Error: SQLCODE=-803, SQLSTATE=23505, SQLERRMC=1; PR_SYS_APP_HIERARCHY_FLAT Discussion Upgrade FSIF 7.1.5 failed Question SQLState 57014, Error code -952: com.ibm.db2.jcc.b.SqlException: DB2 SQL error: SQLCODE: -952, SQLSTATE: 57014, SQLERRMC: null Discussion Rule Migration failed with parsing error during Pega7 upgrade Discussion Rules Upgrade Failed With Deadlock Issue in MS SQL Server Discussion Upgrade Failed with Network Adapter could not establish connection error Question Library Compilation Fails After Upgrade
Contact a Moderator

Discussion

1
Replies
220
Views
sudharsan Member since 2013 14 posts
PEGA
Posted: 5 years ago
Last activity: 5 years 3 months ago
Closed

Upgrade failed with sqlcode=-433 sqlstate=22--1

Hi,

Upgrade failed with insetion error. DB2 SQL Error: SQLCODE=-433, SQLSTATE=22001

What can be the issue ?

**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.

Low-Code App Development Upgrades
Close popover
Moderation Team has archived post
Posted: 5 years ago

One of the possible reasons can be customizations in rule tables. Since new rule tables have been added in 7.1, the customizations in old rule tables should be applied to the new tables as well.


This issue can be resolved by carrying out upgrade in a multi-step process.

1. Use generateDDL.sh to create the upgrade DDLs

2. Apply the DDLs in the new schema

3. Identify customizations done on the rule tables like pylabel changes or pzpvstream changes

4. Reapply the customizations in newly created rule tables like PR4_RULE_RULESET, PR4_RULE_DECLAREPAGES etc.

5. Run upgrade.sh by setting bypass.schema.generation to true

 
Share this page LinkedIn
Copied!