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

Need assistance restoring and verifying broken work objects

SA-513

Summary



Due to an issue with the environment several Work Object blobs were corrupted in the database.  Need to be able to restore the corrupted blobs from a database backup.

Error Messages



ORA-29532: Java call terminated by uncaught Java exception:
com.pega.pegarules.data.internal.clipboard.directstream.BadStreamDataException:
Truncated binary stream encountered; expected decompressed size of 2370997, but
actually got 1410181

Steps to Reproduce



Unknown


Root Cause



Not Applicable 


Resolution



In this case there was a parent WO P- which covers a child PH- WO which covers a T- WO.  


In general, this is the procedure to follow:

1.  Create source system pointing to DB backup from closest point prior to the corruption.  
2.  Login to source system and use PRPC to create RAP for broken WO and its covered WO(s) only.  That is, if PH- level corrupt then include PH- and P- in RAP.  If P- corrupt only include P-.  If there was a T- corrupt then include T-, PH-, and P-.  In the source system create a new Product rule.  Under "Individual Instances to Include" list the pzInskey of the appropriate WOs, save the rule and then click on the "Create Product File" button to create the RAP file.
3.  In target system import the RAP file.  Cleanup any broken assignments and then progress WOs from restored state to point of failure using history audit trail. 
 
Suggest Edit

Published March 27, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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