An existing interim patch is incompatible with the new bundle, causing the "exclusive" session to abort.

Running the command as the wrong user (e.g., oracle instead of root ) or having incorrect permissions on the /tmp directory or inventory.

Note: After applying with -binary, you must manually start the stack and run any required SQL scripts (like datapatch).

This specific error typically occurs when the orchestration engine fails to validate the environment or execute the required shutdown/startup sequences necessary for a non-rolling patch application. What is Non-Rolling Mode?