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

SMS records not getting deleted from PR_DATA_CORR_SMS table

SA-9256

Summary



User has tried to insert the data for OutboundSMS in PR_DATA_CORR_SMS table while running a Program by using “write now” in “PrepareSMS” Activity to test it temporarily as the commit was not happening currently. The SMS record was written in the PR_DATA_CORR_SMS table. It’s getting picked up and sent, but the record was not getting deleted from PR_DATA_CORR_SMS table as a result its sending the same SMS continuously. May be the status was not getting updated in the PR_DATA_CORR_SMS table for the records to be deleted.

Error Messages



There were no error messages, same SMS were being sent by the agent infinite times.

Steps to Reproduce



Create a Split schema setup for Pega 7.1.6 with NBAM v7.1.1 with Oracle database and Weblogic application server
Configure for the SMS server and create an Offer flow with send SMS shape
Run the Offer flow


Root Cause



The entry under the table PR_DATA_CORR_SMS was not getting deleted due to the delete query from sendSMSBatch activity was being failed to execute on the DATA schema.

Resolution



User have a local change in place under SendSMSBatch by explicitly mentioning the PegaDATA schema alias to the DB queries (delete and update) being triggered.
Suggest Edit

Published January 31, 2016 - Updated December 2, 2021

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