My Oracle Support Banner

After upgrading from OAS 5.5 to 5.9 START.CMD fails to start the OAS stack (Doc ID 2772063.1)

Last updated on AUGUST 20, 2021

Applies to:

Oracle Analytics Server - Version 5.9.0 and later
Information in this document applies to any platform.

Symptoms

 After upgrading from OAS 5.5 to 5.9 START.CMD fails to start the OAS stack.

You may see errors similar to in your start.cmd log file

 

<Info> <Security> <BEA-090909> <Using the configured custom SSL Hostname Verifier implementation: weblogic.security.utils.SSLWLSHostnameVerifier$NullHostnameVerifier.>
Node manager not running. Starting it...
NMProcess: NODEMGR_HOME is already set to C:\ora\oas\USER_P~1\domains\esms\NODEMA~1
NMProcess: CLASSPATH=.;C:\PROGRA~1\Java\JDK18~1.0_2\lib\tools.jar;c:\ora\oas\wlserver\server\lib\weblogic.jar;c:\ora\oas\oracle_common\modules\thirdparty\ant-contrib-1.0b3.jar;c:\ora\oas\wlserver\modules\features\oracle.wls.common.nodemanager.jar;C:\PROGRA~1\Java\JDK18~1.0_2\lib\tools.jar;c:\ora\oas\wlserver\modules\features\WLSTWL~1.JAR;c:\ora\oas\wlserver\modules\features\oracle.wls.common.grizzly.jar;C:\ora\oas\oracle_common\modules\oracle.jps\jps-manifest.jar
NMProcess:
NMProcess: C:\ora\oas\USER_P~1\domains\esms\NODEMA~1>"C:\PROGRA~1\Java\JDK18~1.0_2\bin\java.exe" -server -Xms32m -Xmx200m -Djdk.tls.ephemeralDHKeySize=2048 -Dcoherence.home=c:\ora\oas\coherence -Dbea.home=c:\ora\oas -DNodeManagerHome=c:\ora\oas\user_projects\domains\esms\nodemanager -DLogToStderr=false -DQuitEnabled=true -Dweblogic.RootDirectory=c:\ora\oas\user_projects\domains\esms -Doracle.security.jps.config=c:\ora\oas\user_projects\domains\esms\config\fmwconfig\jps-config-jse.xml -Dcommon.components.home=C:\ora\oas\oracle_common -Dopss.version=12.2.1.3 -Dweblogic.RootDirectory=C:\ora\oas\USER_P~1\domains\esms -Doracle.bi.home.dir=C:\ora\oas\bi -Doracle.bi.config.dir=c:\ora\oas\user_projects\domains\esms\config\fmwconfig\biconfig -Doracle.bi.environment.dir=c:\ora\oas\user_projects\domains\esms\config\fmwconfig\bienv -Doracle.bi.12c=true -Ddomain.home=C:\ora\oas\USER_P~1\domains\esms -Dfile.encoding=utf-8 -Djava.system.class.loader=com.oracle.classloader.weblogic.LaunchClassLoader "-Djava.security.policy=c:\ora\oas\wlserver\server\lib\weblogic.policy" "-Dweblogic.nodemanager.JavaHome=C:\PROGRA~1\Java\JDK18~1.0_2" weblogic.NodeManager -v
NMProcess: Apr 14, 2021 9:24:41 AM oracle.security.jps.internal.config.xml.XmlConfigurationFactory validateFileLocation
NMProcess: INFO: JPS Config: c:\ora\oas\user_projects\domains\esms\config\fmwconfig\jps-config-jse.xml
NMProcess: Apr 14, 2021 9:24:42 AM oracle.security.jps.internal.credstore.ssp.CsfWalletManager openWallet
NMProcess: WARNING: Opening of wallet based credential store failed. Reason java.io.IOException: Failed to lock...
NMProcess: attempt 1: java.io.FileNotFoundException: C:\ora\oas\user_projects\domains\esms\config\fmwconfig\bootstrap\cwallet.sso.lck (Access is denied)
NMProcess: attempt 2: java.io.FileNotFoundException: C:\Users\ESMS~1.ICS\AppData\Local\Temp\pki_data12345678.lck (The system cannot find the file specified)
NMProcess: Apr 14, 2021 9:24:42 AM oracle.security.jps.internal.config.OpssCommonStartup preStart
NMProcess: INFO: Jps startup failed.
NMProcess: ( was unexpected at this time.
NMProcess: Stopped draining NMProcess
NMProcess: Stopped draining NMProcess
Failed to start node manager after a timeout of 600000 millisecs. Final exception: Error occurred while performing nmConnect : Cannot connect to Node Manager. : Connection refused: connect. Could not connect to NodeManager. Check that it is running at TestExample.Oracle.com/10.10.10.10:9506.
Use dumpStack() to view the full stacktrace :
Unable to connect to NodeManager on host: TestExample, due to Error occurred while performing nmConnect : Cannot connect to Node Manager. : Connection refused: connect. Could not connect to NodeManager. Check that it is running at TestExample.Oracle.com/10.10.10.10.10:9506.
Use dumpStack() to view the full stacktrace :

Fatal: Failed to start one or more Servers (return 3)

 

Changes

 Upgrade from OAS 5.5 to 5.9

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.