Skip to main content

Popular posts from this blog

Weblogic upgrade server from 10.1.3.4 to 10.3.6

Important points: Different weblogic servers and supported java versions : Oracle WebLogic 10.3.5.0 supports Sun JDK 1.6.0_24. Oracle WebLogic 10.3.6.0, supports the Oracle JDK 1.7.0 Oracle WebLogic 12.1.3 supports Oracle JDK 1.7.0_55+ (1.7.0_67) Oracle WebLogic 12.2.1 (12R2) supports JDK 1.8 Upgrade Weblogic server from 10.1.3.4 to 10.3.6 by applying the Patch: 13529623. step.1 Shut down all WebLogic processes you want to upgrade such as: Node Manager Admin Server All Managed Servers step.2 Download and installed a new version of JDK 1.7+. After installing Verifying the JDK Version java –version Note: A plus sign '+' after the version number indicates that this and its subsequent versions are supported. step.3 Download this patch set for Oracle WebLogic 10.3.6.0: Patch 13529623 (p13529623_1036_Generic.zip) Unzip the file in a temporary location and confirm the extracted contains this file: wls1036_upgrade_generic.jar step.4 Running OUI to Upgrade an Existing WebLogic Server to...

Server subsystem failed. Reason: java.lang.NumberFormatException: null java.lang.NumberFormatException: null

<BEA-000386> Server subsystem failed. Reason: java.lang.NumberFormatException: null java.lang.NumberFormatException: null         at java.lang.Integer.parseInt(Integer.java:417)         at java.lang.Integer.parseInt(Integer.java:499)         at weblogic.ldap.EmbeddedLDAP.validateVDEDirectories(EmbeddedLDAP.java:1097)         at weblogic.ldap.EmbeddedLDAP.start(EmbeddedLDAP.java:242)         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)         at weblogic.work.ExecuteThread.run(ExecuteThread.java:176) This mostly happens when LDAP files are corrupted under the ../domain-name/server/AdminServer/data/ldap/ directory. A possible cause of corruption is when space on server is full. When the associated volume is full (100%)...

Error: unable to obtain lock file

<Server failed. Reason: There are 1 nested errors: weblogic.management.ManagementException: Unable to obtain lock on C:\bea10.3\user_projects\domains\sherkhan\servers\AdminServer\tmp\AdminServer.lok. Server may already be running         at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.java:159)         at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.java:58)         at weblogic.management.internal.DomainDirectoryService.start(DomainDirectoryService.java:73)         at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:459)         at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:164)         at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:711)         at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:482)       ...