Support Article
SPI Proc is not running even after restarted
SA-32159
Summary
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
Resolution
Reported issue resolved after unlocking CMD schema account at database level
Published February 21, 2017 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.