Trying to change a Requisition's status from Released back to Planned (to allow deleting it) via the right-click 'Change to Planned' option fails with 'The object is locked by another user,' and attempting to manually lock the record for inspection throws an Oracle error instead of clarifying who's holding the lock.

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

As a last resort when a record is genuinely stuck locked and there's no other session actively using it, use the Database Sessions administration window to find and kill the session actually holding the lock — this clears the stale lock so the status change can proceed. This is a blunt, session-killing fix rather than a root-cause diagnosis, so it's best reserved for cases where the lock is clearly stale (no legitimate concurrent user activity) rather than used routinely.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions