If there is any hung shareplex oracle sessions by defunct processes, this may cause post to encounter lock issues in the database. Lock may or may not be returned in queries.
(e.g. select * from v$lock where sid = 68; *** for SID 68, in this case)
Runaway process may hold lock on a table (this was noticed in Peoplesoft application in place). It appears that the lock itself does not show up in any query to identify such. PID of the lock holding session does not show up, but it does in the event_lo
It may be necessary to stop shareplex, kill all of the OS processes attached to shareplex, restart shareplex and post if not started.
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center