System lock semop failure - Batch Server Startup Stalls

This one associated with messaging and was preventing the PSUNX batch server from starting up properly, after a batch job may have taken down the process scheduler.    After taking the usual steps of clearing cache and cleaning IPC resources through the psadmin menu, found this message in each attempt to start.  The "System lock semop failure" message appears in the Tuxlog, along with the reference to message failed. The process scheduler would go through nearly all the start up steps before stalling on a step using messaging.    Turns out the job that was cancelled had an Oracle table lock on