BEA-000286 Failed to invoke startup class "JRF Startup Class" ADF ManagedServer

Version:

WLS 10.3.6 and ADR 11.1.1.7.0 on Windows

Issue:

Getting errors when Managed Server was tried to start from weblogic console URL. Nodemanager was up and its status in console was Active. The same Managed Server can be started up using startManagedserver.cmd

Error:

<Dec 15, 2014 11:28:03 PM MST> <Critical> <WebLogicServer> <BEA-000286> <Failed to invoke startup class "JRF Startup Class", java.lang.ClassNotFoundException: oracle.jrf.wls.JRFStartup
java.lang.ClassNotFoundException: oracle.jrf.wls.JRFStartup
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)
Truncated. see log file for complete stacktrace

Reason:

From logs it was clear that issue is because of missing JRF classes in CLASSPATH.

JRF(Java Required Files) includes important libraries and capabilities that provides APIs that many OC4J (Oracle Container for Java, Oracle’s old JVM) applications depend upon.  JRF comes (under $MW_HOME/oracle_common) when you install Fusion Middleware component like ADF, SOA, WebCenter or Identity Management. 

Solution:

This class (JRF Startup) is in $MW_HOME\modules\oracle.jrf_11.1.1\jrf.jar

1) Add this path as part of WEBLOGIC CLASSPATH in commEnv.cmd

Class Path for Service is defined in $WLS_HOME\common\bin\commEnv.cmd (Eg: C:\Middleware\wlserver_10.3\common\bin). Add the entry $MW_HOME\modules\oracle.jrf_11.1.1\jrf.jar in WEBLOGIC_CLASSPATH in commEnv.cmd file under "set WEBLOGIC_CLASSPATH=" section


2) Restart the Managed Server.

PolicySet Invalid: WSM-06102 PolicyReference for 12c Enterprise Manager Cloud control

Version: 

OEM 12c Cloud control


Issue:

Standby DB creation is tried from EM using Availability - Add Standby Database.

On the submission of the job, it hangs and then fails on preparation phase.

The error received was 

PolicySet Invalid: WSM-06102 PolicyReference The policy reference URI "oracle/wss_username_token_client_policy" is not valid.


The error can be found from the emoms_pbs.trc files available under <OMS_Instance_Home>/em/<oms_name>/sysman/log directory.


Reason:

The weblogic and nodemanager credentails for the EM was reset recently. But few of the steps as part of password change was not done. 

Because of this even if we were able to  work with EM, the submission of jobs always failed or hung.

Solution:

Followed the Support Doc ID. 1450798.1. Redid all the steps exactly as mentioned in the document.

Reset the passwords back to the existing changed value.  After completion of all the above steps, tried the standby DB creation and it was successful.

Weblogic 10.3.6: java.io.IOException: Unable to backup file "weblogic-domain-binding.jar" during patching

Version:

Weblogic Server 10.3.6 in Windows 2008

Issue:

The bsu command to apply patch errors out

Patch applied was 18040640 (Patch Set Update 10.3.6.0.8).

Error:

Installing Patch ID: T5F1..Result: Failure
java.io.IOException: Unable to backup file C:\Middleware\wlserver_10.3\server\lib\schema\
weblogic-domain-binding.jar to C:\Middleware\wlserver_10.3\server\lib\schema\weblogic-dom
ain-binding.jar19755.bak

Reason: 

Few of the WLS files were already active during patching.

Patch was tried  straight after WLS installation. Nodemanager  was enabled as a service during installation and it was running.  Due to this the patching failed.

Action:

Stopped the nodemanager service from services.msc. Verified that no DLLs and files from the WLS Home is active using processExplorer tool. Reapplied the patch.