This content has been marked as final. Show 5 replies
You are correct, it turns out it is a known bug, # 1390274.
The work around supplied by Oracle Support ends up being very simple:
* Rename %ORACLE_HOME%\OPatch\jlib\oracle.opatch.classpath.jar to %ORACLE_HOME%\OPatch\jlib\oracle.opatch.classpath1.jar
* Apply the patch
* Undo the renaming of the file
I'm just now going to apply the patch and will report back!
One just wonders when this will ever corrected...