Oracle Weblogic Upgrade from 10.3.5 to 10.3.6

As we know that Oracle Weblogic 10.3.5 is now out of support by Oracle. So in this post we shall see up gradation of weblogic from 10.3.5 to 10.3.6.

Pre Upgrade Steps:

Step 1) Download the upgrade patch from metalink. The patch number is p13529623_1036_Generic.

Step 2) Unzip the downloaded file.The resultant file would be wls1036_upgrade_generic.jar file.

Step 3) Backup MW folder and Inventory directory.

Step 4) Shutdown below services:

            Admin Server , All Manage server and Node Manager.

Upgrade Steps:

Step 1) Invoke the upgrade installer as below :

 java -d64 -jar wls1036_upgrade_generic.jar

 

Step 2) Upon execution, the installer starts preparing the OUI install program. Click Next.

Step 3) On Choose Middleware Home Directory, select radio button "Use an existing Middleware home" you wish to upgrade and click Next

 

Step 4) On Register for Security Updates, the Email address and/or the My Oracle Support Password fields as applicable and click Next.

 

Step 5) On Choose Products and Components, verify the components and click Next

 

Step 6) On Choose Product Installation Directories, verify the directory locations for the previously selected products and components and click Next



Step 7) OUI begins copying the files and performs the upgrade. It takes approximately 10-15 mins for upgrade to complete. Uncheck checkbox "Run QuickStart" and click Done.

Verification Process:

Step 1) Execute "setWLSEnv.sh" from $WL_HOME/server/bin

 

Step 2) Login to Weblogic console and check version
http://hostname:Port/console

Issues and Solution:

 Issue: 

1) After starting Admin server below error was observed:

<<
<Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.AssertionError: java.lang.ClassNotFoundException: weblogic.jndi.internal.ServerNamingNode_1035_WLStub
java.lang.AssertionError: java.lang.ClassNotFoundException: weblogic.jndi.internal.ServerNamingNode_1035_WLStub
at weblogic.jndi.WLInitialContextFactoryDelegate.newRootNamingNodeStub(WLInitialContextFactoryDelegate.java:610)
at weblogic.jndi.WLInitialContextFactoryDelegate.newRemoteContext(WLInitialContextFactoryDelegate.java:577)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:482)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:376)
at weblogic.jndi.Environment.getContext(Environment.java:315)
Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: weblogic.jndi.internal.ServerNamingNode_1035_WLStub
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
Truncated. see log file for complete stacktrace
>

Exception in thread "main" java.lang.AssertionError: Failed to load stub for class class weblogic.server.RemoteLifeCycleOperationsImpl 

>>

Solution:

Step 1) We saw that there is still reference to weblogic.server.modules_10.3.5.0.jar at location $MW_HOME/modules/features/weblogic.server.modules_10.3.5.0.jar

Step 2) Replace that weblogic.server.modules_10.3.5.0.jar with weblogic.server.modules_10.3.6.0.jar

Step 3) Clean tmp,cache,data and log folder under $DOMAIN_HOME/servers/AdminServer

Step 4) Restart  Admin server

Step 5) Start Node Manager and all manage server (clear tmp,cache,data,log for all manage server).