Running OEM 13.2 on SLES 11SP4 64-bit Linux. Yesterday I upgraded several plugins to the latest release: Oracle Cloud Framework to 13.2.2, Oracle Database to 13.2.2, Oracle Exadata to 13.2.2, Oracle Fusion Middleware to 13.2.2, Systems Infrastructure to 13.2.2. I applied all plugin upgrades to the management server and deployed them to the appropriate agents.
Since upgrading these plugins, the OMSPatcher and OPatch tools in the EM13cR2 middleware home no longer work. Every command attempted, other than a version check, fails.
oracle@r1oemdb1:~> export ORACLE_HOME=$MW_HOME
oracle@r1oemdb1:~> $MW_HOME/OPatch/opatch version
OPatch Version: 13.9.1.0.0
OPatch succeeded.
oracle@r1oemdb1:~> $MW_HOME/OMSPatcher/omspatcher version
OMSPatcher Version: 13.8.0.0.1
OPlan Version: 12.2.0.1.6
OsysModel build: Tue Nov 08 17:52:30 PST 2016
OMSPatcher succeeded.
Attempting to list patches:
oracle@r1oemdb1:~> $MW_HOME/OPatch/opatch lsinv -oh $ORACLE_HOME
OPatch failed with error code 255
oracle@r1oemdb1:~> $MW_HOME/OMSPatcher/omspatcher lspatches -oh $ORACLE_HOME
Exception in thread "main" java.lang.NoClassDefFoundError: com/oracle/cie/common/dao/DataHandlerException
at oracle.sysman.oii.oiix.OiixPlatform.<clinit>(OiixPlatform.java:457)
at oracle.opatchauto.oms.OUIReplacer$Platform.getCurrentPlatformDirectoryName(OUIReplacer.java:65)
at oracle.opatchauto.oms.OPatchAuto.checkJDKCompatibleOUI(OPatchAuto.java:333)
at oracle.opatchauto.oms.OPatchAuto.main(OPatchAuto.java:711)
Caused by: java.lang.ClassNotFoundException: com.oracle.cie.common.dao.DataHandlerException
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
... 4 more
OMSPatcher failed with error code 1
Even calling the help verb fails the same way:
oracle@r1oemdb1:~> $MW_HOME/OPatch/opatch help
OPatch failed with error code 255
oracle@r1oemdb1:~> $MW_HOME/OMSPatcher/omspatcher help
Exception in thread "main" java.lang.NoClassDefFoundError: com/oracle/cie/common/dao/DataHandlerException
at oracle.sysman.oii.oiix.OiixPlatform.<clinit>(OiixPlatform.java:457)
at oracle.opatchauto.oms.OUIReplacer$Platform.getCurrentPlatformDirectoryName(OUIReplacer.java:65)
at oracle.opatchauto.oms.OPatchAuto.checkJDKCompatibleOUI(OPatchAuto.java:333)
at oracle.opatchauto.oms.OPatchAuto.main(OPatchAuto.java:711)
Caused by: java.lang.ClassNotFoundException: com.oracle.cie.common.dao.DataHandlerException
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
... 4 more
I have also tried this using the latest 13.9.1.3.0 release of OPatch with no change in behavior.
OPatch debugging output does not seem to provide any useful information:
oracle@r1oemdb1:~> OPATCH_DEBUG=TRUE $MW_HOME/OPatch/opatch help
OPatch was not able to set FMW_COMPONENT_HOME by itself.
- Detect the option -jre/-jdk ? 0
- Start JVM Discovery ...
Looking for java using /oracle/oem/Middleware13cR2/oui/bin/getVariable.sh
Setting java to /oracle/oem/Middleware13cR2/oracle_common/jdk/bin/java
Looking for -d64 option using /oracle/oem/Middleware13cR2/oui/bin/getVariable.sh
Setting JVM_64 to
CAS jars exist ? 0 [/oracle/oem/Middleware13cR2/OPatch/jlib/com.oracle.glcm.patch.content-store_12.2.0.1.3.jar]
JAVA version : 7 [/oracle/oem/Middleware13cR2/oracle_common/jdk]
Can Use JAVA ? 1
Machine Info: Linux r1oemdb1 3.0.101-77-default #1 SMP Tue Jun 14 20:33:58 UTC 2016 (a082ea6) x86_64 x86_64 x86_64 GNU/Linux
_osArch is amd64
_javaVMSpecVersion is 1.7
_javaVMSpecVendor is Oracle Corporation
_javaVMSpecName is Java Virtual Machine Specification
_javaVMVendor is Oracle Corporation
_javaJRESpecVersion is 1.7
_javaJRESpecVendor is Oracle Corporation
_javaJRESpecName is Java Platform API Specification
_javaSupportedClassVersion is 51.0
OPatch compiled with major version: 49, minor version: 0
Looking for -d64 option using /oracle/oem/Middleware13cR2/oui/bin/getVariable.sh
Setting JVM_64 to
JRE_MEMORY_OPTIONS are -Xmx3072m -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/oracle/oem/Middleware13cR2/cfgtoollogs/opatch
_osArch (from OCM API) is
/oracle/oem/Middleware13cR2/oracle_common/jdk/bin/java -Xmx3072m -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/oracle/oem/Middleware13cR2/cfgtoollogs/opatch -cp /oracle/oem/Middleware13cR2/oui/modules/OraInstaller.jar:/oracle/oem/Middleware13cR2/OPatch/jlib/oracle.opatch.classpath.jar:/oracle/oem/Middleware13cR2/OPatch/auto/core/modules/features/oracle.glcm.oplan.core.classpath.jar:/oracle/oem/Middleware13cR2/OPatch/auto/core/modules/features/oracle.glcm.osys.core.classpath.jar:/oracle/oem/Middleware13cR2/OPatch/../oui/modules/installer-launch.jar -DOPatch.ORACLE_HOME=/oracle/oem/Middleware13cR2 -DOPatch.DEBUG=true -DOPatch.MAKE=false -DOPatch.RUNNING_DIR=/oracle/oem/Middleware13cR2/OPatch -DOPatch.MW_HOME=/oracle/oem/Middleware13cR2 -DOPatch.WL_HOME= -DOPatch.COMMON_COMPONENTS_HOME= -DOPatch.OUI_LOCATION=/oracle/oem/Middleware13cR2/oui -DOPatch.FMW_COMPONENT_HOME= -DOPatch.OPATCH_CLASSPATH= -DOPatch.WEBLOGIC_CLASSPATH= -DOPatch.SKIP_OUI_VERSION_CHECK= -DOPatch.PARALLEL_ON_FMW_OH= oracle/opatch/OPatch help -invPtrLoc /oracle/oem/Middleware13cR2/oraInst.loc
OPatch failed with error code 255
I asked around on Twitter and confirmed that at least one other person has seen this same behavior. Both OMSPatcher and OPatch worked as expected prior to applying these plugin updates. I have run opatchdiag from note 1430571.1 and saved the output, but did not find anything useful.
Have any of you already filed a service request for this issue or found a workaround?
Thanks!
-Brian