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

Sybase external database update not consistent.



After user upgrade to PEGA 7.2 from PRPC 6.2, the external Sybase database stored proc is not getting executed in RDB-SAVE to update values consistently. There is no failure in Pega but the database update is not always being done.

Error Messages

Not applicable.

Steps to Reproduce

Calling Sybase database stored proc to update table rows through RDB-SAVE.

Root Cause

This is attributable to the setup of the data source resource in the application server. When the stored procedure involves cursors, special handling comes into play for unprocessed results. In this case, WebSphere Admin console needs to specify a custom property to handle this. 


Add custom property "skipCheckForUnprocessedResults=true" to the data source.


Suggest Edit

Published August 14, 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