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

SPI Proc is not running even after restarted



From the server side the SPI proc is up and running (count was 2) but from admin console it is not up and from database side also not processing any campaigns. When the user restart from server side the service is up at admin console side. Also the count has changed from 2 to 3 after restarted from server. But the client complained that the campaigns are still not started or running at database level.

Customer not able to restart from Admin console as well.

Error Messages

Scheduled components not starting due to oracle error “ORA-03114 not connected to ORACLE”

Steps to Reproduce

Scheduled components to run

Root Cause

CMD schema account was locked at database level


Reported issue resolved after unlocking CMD schema account at database level

Published February 21, 2017 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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