This post is also available in:
Português (Portuguese (Brazil))
When running opatchauto with the out-of-place option, the process fails reporting a previous session was not completed:
OPATCHAUTO-72115: Out of place patching apply session cannot be performed.
OPATCHAUTO-72115: Previous apply session is not completed on node hostname.
OPATCHAUTO-72115: Please complete the previous apply session across all nodes to perform apply session.
opatchauto failed with error code 42The opatchauto found a checkpoint from a previous session and refuses to start a new one.
Why It Happens
The opatchauto saves execution state in a checkpoint file (oopsessioninfo.ser) so it can resume in case of failure. If the previous session was interrupted — by Ctrl+C, server reboot, timeout, or unexpected error — the checkpoint becomes orphaned and blocks new executions.
Solution
1. Verify NO session is currently running
Before clearing the checkpoint, confirm no other DBA is running opatchauto:
ps -ef | grep opatchauto | grep -v grepIf it returns empty, it’s safe to proceed.
2. Locate and remove the checkpoint file
cd $ORACLE_HOME/.opatchauto_storage/$(hostname)
ls -la oopsessioninfo.ser
rm oopsessioninfo.serIn RAC environments: The checkpoint may exist on all nodes. Check and remove on each one:
for node in node1 node2; do
echo "=== $node ==="
ssh $node "ls -la $ORACLE_HOME/.opatchauto_storage/\$(hostname)/oopsessioninfo.ser 2>/dev/null || echo 'Clean'"
done3. Re-run opatchauto
sudo $ORACLE_HOME/OPatch/opatchauto apply ${PATCH_TOP} -outofplace -silent ./clone.propertiesQuick Checklist
ps -ef | grep opatchauto | grep -v grep
ls -la $ORACLE_HOME/.opatchauto_storage/$(hostname)/oopsessioninfo.ser
rm $ORACLE_HOME/.opatchauto_storage/$(hostname)/oopsessioninfo.ser
ssh node2 "ls -la $ORACLE_HOME/.opatchauto_storage/\$(hostname)/oopsessioninfo.ser"
sudo $ORACLE_HOME/OPatch/opatchauto apply ${PATCH_TOP} -outofplace -silent ./clone.properties