SUM process stopped with error Upgrade NW 7.3 to NW 7.3 EHP 1

[Former Member]

Hey,

i am trying to upgrade NetWeaver 7.3 to NetWeaver 7.3 EHP 1 with Solution Manager.

Although i restarted instance and oracle database "shutdown & startup" the deployment doesn't run.

This task stopped with error in SUM process report.

Errors

Log event ID: 6501 Error message: May 6, 2013 8:28:24 AM [Error ]: The following problem has occurred during step execution: com.sap.sdt.jspm.service.JspmServiceException: Could not update components. Deployment of queue Queue_2013.05.02 at 15:50:35 completed with error Could not connect to Deploy Controller. Make sure that AS Java and Deploy Controller service are running. com.sap.engine.services.dc.api.ConnectionException: [ERROR CODE DPL.DCAPI.1144] Could not establish connection to AS Java on [MEQAPP02:50004]. Cannot establish connection with any of the available profiles:

log file: C:\Temp\SUM\sdt\log\SUM\DEPLOY-COMPONENTS_NN.LOG

Explanation: One possible reason for this error is that the SAP software component(s) com.sap.engine are missing.

SAP System: Java only

Database: Oracle 11.2.0.1.0

Thanks for help,

Markus

[sergiy_katerinich · Accepted solution]

Hi Markus,

I would try deploying via NW Console ...\j2ee\console\guiconsole.bat.

And checking the status of Deploy Controller service as suggested by the error message is a good idea.

Regards,

Sergiy

[Former Member · Accepted solution]

Hey Sergiy,

thanks i will check the status of Deploy Controller service.

Here are more informations about sapmmc

and the developer trace

---------------------------------------------------

trc file: "dev_jstart.3152", trc level: 1, release: "720"

---------------------------------------------------

---------------------------------------------------

trc file: "dev_jstart.new", trc level: 1, release: "720"

---------------------------------------------------

sysno 00

sid MEQ

systemid 562 (PC with Windows NT)

relno 7200

patchlevel 0

patchno 63

intno 20020600

make multithreaded, Unicode, 64 bit, optimized

profile \\EJMEAPP2\sapmnt\MEQ\SYS\profile\MEQ_J00_EJMEAPP2

pid 3152

*

* ACTIVE TRACE LEVEL 1

* ACTIVE TRACE COMPONENTS All, egi

*

Mon May 06 11:45:10 2013

*

* trace logging activated, max size = 52428800 bytes, 2 versions

*

arguments :

arg[ 0] : C:\usr\sap\MEQ\J00\exe\jstart.EXE

arg[ 1] : pf=\\EJMEAPP2\sapmnt\MEQ\SYS\profile\MEQ_J00_EJMEAPP2

F

F Mon May 06 11:45:10 2013

F ********************************************************************************

F Java environment properties (C:\usr\sap\MEQ\J00\work\jstart.jvm)

F root directory : C:\usr\sap\MEQ\J00\exe\sapjvm_6

F vendor : SAP AG

F version : 1.6.0_45

F cpu : amd64

F java vm type : server

F java vm version : 6.1.049 23.5-b05

F jvm library name : jvm.dll

F library path : C:\usr\sap\MEQ\J00\exe\sapjvm_6\jre\bin\server;C:\usr\sap\MEQ\J00\exe\sapjvm_6\jre\bin

F executable path : C:\usr\sap\MEQ\J00\exe\sapjvm_6\bin

F ********************************************************************************

F SAP extensions : available

F ********************************************************************************

I

I [Thr 6040] Mon May 06 11:45:11 2013

I [Thr 6040] MtxInit: 30002 0 2

---------------------------------------------------

trc file: "dev_jstart", trc level: 1, release: "720"

---------------------------------------------------

*

* ACTIVE TRACE LEVEL 1

* ACTIVE TRACE COMPONENTS All, egi

*

F [Thr 6040] *** LOG => connected to Enqueue Server.

F [Thr 6040] *** LOG => connected to Message Server.

F [Thr 6040] *** LOG => Starting run level 1.

F ********************************************************************************

F Java process [deployment] properties:

F section name : deployment

F config file : C:\usr\sap\MEQ\J00\exe\startup.properties

F node name : Deploy_offline

F home directory : C:\usr\sap\MEQ\J00\j2ee\cluster

F shutdown timeout : 136000 ms

F exit timeout : 7000 ms

F debuggable : false

F debugger active : false

F ********************************************************************************

F [Thr 6040] *** LOG => Instance state is "Deploying offline components" (STARTING @ 0, INACTIVE).

F [Thr 6040] *** LOG => Starting nodes: runlevel 1.

F ********************************************************************************

F Starting process: C:\usr\sap\MEQ\J00\exe\jstart.EXE

F arg[ 1] = -nodeId=0

F arg[ 2] = pf=\\EJMEAPP2\sapmnt\MEQ\SYS\profile\MEQ_J00_EJMEAPP2

F arg[ 3] = -hostvm

F arg[ 4] = -nodeName=deployment

F arg[ 5] = -file=C:\usr\sap\MEQ\J00\exe\startup.properties

F arg[ 6] = -jvmFile=C:\usr\sap\MEQ\J00\work\jstart.jvm

F arg[ 7] = -traceFile=C:\usr\sap\MEQ\J00\work\dev_deployment

F arg[ 8] = -javaOutFile=C:\usr\sap\MEQ\J00\work\jvm_deployment.out

F env : NODNSSAPTRANSHOST=1

F exePath : PATH=C:\usr\sap\MEQ\J00\exe\sapjvm_6\bin;C:\usr\sap\MEQ\J00\exe;C:\oracle\product\11.2.0\dbhome_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\usr\sap\MEQ\SYS\exe\uc\NTAMD64

F libPath : PATH=C:\usr\sap\MEQ\J00\exe\sapjvm_6\jre\bin\server;C:\usr\sap\MEQ\J00\exe\sapjvm_6\jre\bin;C:\usr\sap\MEQ\J00\j2ee\os_libs;C:\usr\sap\MEQ\J00\exe\sapjvm_6\bin;C:\usr\sap\MEQ\J00\exe;C:\oracle\product\11.2.0\dbhome_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\usr\sap\MEQ\SYS\exe\uc\NTAMD64

F stdout : C:\usr\sap\MEQ\J00\work\std_deployment.out

F stderr : C:\usr\sap\MEQ\J00\work\std_deployment.out

F console : no

F debugger: no

F nice : no

F ********************************************************************************

F Process Deploy_offline started with pid 5928

F ********************************************************************************

F [Thr 6040] *** LOG => Process deployment started (pid 5928).

F

F [Thr 6040] Mon May 06 11:45:13 2013

F [Thr 6040] *** LOG => Process deployment running (pid 5928).

F [Thr 6040] *** LOG => Instance state is "Deploying offline components" (RUNNING @ 0, INACTIVE).

F

F [Thr 6040] Mon May 06 11:45:16 2013

F [Thr 6040] *** LOG => Process deployment stopping (pid 5928).

F

F [Thr 5936] Mon May 06 11:45:16 2013

F [Thr 5936] *** LOG => Signal 13 SIGCHLD.

F [Thr 6040] *** LOG => Process deployment stopped (pid 5928).

F [Thr 6040] *** WARNING => Node deployment failed: result 1, exit code 66. [sfxxnode.hpp 1024]

F ********************************************************************************

F Native process [snapshot] properties:

F section name : snapshot

F config file : C:\usr\sap\MEQ\J00\exe\startup.properties

F node name : snapshot

F home directory : C:\usr\sap\MEQ\J00\work

F shutdown timeout : 122000 ms

F sf support : false

F ********************************************************************************

F ********************************************************************************

F Starting process: C:\usr\sap\MEQ\J00\exe\sapcontrol.EXE

F arg[ 1] = -prot

F arg[ 2] = PIPE

F arg[ 3] = -nr

F arg[ 4] = 00

F arg[ 5] = -function

F arg[ 6] = CreateSnapshot

F arg[ 7] = Servercrash

F arg[ 8] = postmortem?node=deployment&exitcode=66

F arg[ 9] = 1

F arg[10] = 10000

F arg[11] = ""

F arg[12] = ""

F arg[13] = DEFAULT

F env : NODNSSAPTRANSHOST=1

F exePath : PATH=C:\usr\sap\MEQ\J00\exe;C:\oracle\product\11.2.0\dbhome_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\usr\sap\MEQ\SYS\exe\uc\NTAMD64

F libPath : PATH=C:\usr\sap\MEQ\J00\exe;C:\oracle\product\11.2.0\dbhome_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\usr\sap\MEQ\SYS\exe\uc\NTAMD64

F stdout : C:\usr\sap\MEQ\J00\work\std_snapshot.out

F stderr : C:\usr\sap\MEQ\J00\work\std_snapshot.out

F console : no

F debugger: no

F nice : no

F ********************************************************************************

F Process snapshot started with pid 5976

F ********************************************************************************

F [Thr 6040] *** LOG => Process snapshot started (pid 5976).

F [Thr 6040] *** LOG => Process snapshot running (pid 5976).

F [Thr 6040] *** LOG => SAP Start Service (pid 6024) connected.

F [Thr 6040] *** LOG => SAP Start Service (pid 6024) disconnected.

F

F [Thr 1696] Mon May 06 11:45:27 2013

F [Thr 1696] *** LOG => Signal 13 SIGCHLD.

F

F [Thr 6040] Mon May 06 11:45:27 2013

F [Thr 6040] *** LOG => Process snapshot stopped (pid 5976).

F [Thr 6040] *** LOG => Instance state is "Deploying offline components" (STOPPING @ 0, INACTIVE).

F [Thr 6040] *** LOG => Run level 1 completed.

F [Thr 6040] *** LOG => Instance state is "Some processes failed" (STOPPED @ 0, INACTIVE).

I [Thr 6040] MPI: dynamic quotas disabled.

I [Thr 6040] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%

F

F ********************************************************************************

F *** ERROR => Node 'deployment' failed with exit code 66.

F ***

F *** Please see section 'Failures in the 'deploying offline components' phase'

F *** in SAP Note 1316652 for additional information and trouble shooting advice.

F ********************************************************************************

F

F [Thr 6040] *** LOG => exiting (exitcode 22002, retcode 1).

Thanks,

Markus

[Former Member · Accepted solution]

Hi Sergiy,

i checked NW Console but can't connect to http://EJMEAPP2:50004 because the instance stopped with error after 18 seconds

F [Thr 6040] Mon May 06 11:45:27 2013

F [Thr 6040] *** LOG => Process snapshot stopped (pid 5976).

F [Thr 6040] *** LOG => Instance state is "Deploying offline components" (STOPPING @ 0, INACTIVE).

F [Thr 6040] *** LOG => Run level 1 completed.

F [Thr 6040] *** LOG => Instance state is "Some processes failed" (STOPPED @ 0, INACTIVE).

I [Thr 6040] MPI: dynamic quotas disabled.

I [Thr 6040] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%

Do i have to reinstall the instance?

My central issue is to start instance in sapmmc.

Regards,

Markus

[sergiy_katerinich · Accepted solution]

Hi Markus,

As you can see, your instance failed to start because of a crash of deployment.

It's worth examining deploy*.* and *deployment*.* files under /work folder for a specific error message which can point to the root cause.

Or reinstalling the instance...

Regards,

Sergiy

[Former Member · Accepted solution]

Hi Sergiy,

here the message in log jvm_deployment

   INFO: Loading tool launcher...

   INFO: [OS: Windows Server 2008 R2] [VM vendor: SAP AG] [VM version: 1.6.0_45] [VM type: SAP Java Server VM]

   INFO: Main class to start: "com.sap.engine.services.dc.cm.offline_phase.Runner"

   INFO: Loading 21 JAR files: [C:\usr\sap\MEQ\SYS\global\security\lib\tools\iaik_jce.jar, C:\usr\sap\MEQ\SYS\global\security\lib\tools\iaik_jsse.jar, C:\usr\sap\MEQ\SYS\global\security\lib\tools\iaik_smime.jar, C:\usr\sap\MEQ\SYS\global\security\lib\tools\w3c_http.jar, C:\usr\sap\MEQ\SYS\global\security\lib\tools\iaik_ssl.jar, .\bootstrap\jdbc.jar, .\bootstrap\jperflib.jar, .\bootstrap\sap.com~tc~bl~config~impl.jar, .\bootstrap\sap.com~tc~bl~deploy~offline~impl.jar, .\bootstrap\sap.com~tc~bl~iqlib~impl.jar, .\bootstrap\sap.com~tc~bl~jdsr~jdsr.jar, .\bootstrap\sap.com~tc~bl~offline_launcher~impl.jar, .\bootstrap\sap.com~tc~bl~opensql~implStandalone.jar, .\bootstrap\sap.com~tc~exception~impl.jar, .\bootstrap\sap.com~tc~je~bootstrap~impl.jar, .\bootstrap\sap.com~tc~je~cfs~container~standalone_impl.jar, .\bootstrap\sap.com~tc~je~datacollector.jar, .\bootstrap\sap.com~tc~je~extramile.jar, .\bootstrap\sap.com~tc~je~offlineconfiguration~impl.jar, .\bootstrap\sap.com~tc~logging~java~impl.jar, .\bootstrap\sap.com~tc~sec~secstorefs~java~core.jar]

   INFO: Start

com.sap.engine.services.dc.cm.offline_phase.OfflinePhaseProcessException: <--Localization failed: ResourceBundle='com.sap.engine.services.dc.util.exception.resources.ResourceBundle', ID='dc_2115', Arguments: ['ASJ.dpl_dc.003119 An error occurred while getting ConfigurationHandlerFactory from the Deploy Controller Offline Processor.']--> : Can't find resource for bundle java.util.PropertyResourceBundle, key dc_2115

at com.sap.engine.services.dc.cm.offline_phase.Runner.run(Runner.java:43)

at com.sap.engine.services.dc.cm.offline_phase.Runner.main(Runner.java:78)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:162)

Caused by: com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.

at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPoolImpl.createConnection(DBConnectionPoolImpl.java:496)

at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPoolImpl.<init>(DBConnectionPoolImpl.java:197)

at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandlerImpl.<init>(PersistenceHandlerImpl.java:50)

at com.sap.engine.core.configuration.impl.cache.ConfigurationController.<init>(ConfigurationController.java:139)

at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:309)

at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:59)

at com.sap.engine.services.dc.cm.offline_phase.Runner.run(Runner.java:40)

... 6 more

Caused by: com.sap.sql.log.OpenSQLException: Exception of type com.sap.sql.log.OpenSQLException caught: JDBC driver not supported for ORACLE database..

at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104)

at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143)

at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl.java:284)

at com.sap.sql.connect.datasource.DBDataSourceImpl.getPooledConnection(DBDataSourceImpl.java:179)

at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:213)

at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPoolImpl.createConnection(DBConnectionPoolImpl.java:482)

... 12 more

Caused by: com.sap.sql.log.OpenSQLException: JDBC driver not supported for ORACLE database.

at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104)

at com.sap.sql.jdbc.direct.DirectConnectionFactory.createPooledConnection(DirectConnectionFactory.java:491)

at com.sap.sql.jdbc.direct.DirectConnectionFactory.createDirectPooledConnection(DirectConnectionFactory.java:157)

at com.sap.sql.jdbc.direct.DirectConnectionFactory.createDirectPooledConnection(DirectConnectionFactory.java:117)

at com.sap.sql.connect.factory.PooledConnectionFactory.createPooledConnection(PooledConnectionFactory.java:119)

at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledConnection(DriverPooledConnectionFactory.java:38)

at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnection(DBDataSourceImpl.java:651)

at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceImpl.java:995)

at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceImpl.java:43)

at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool.java:95)

at com.sap.sql.connect.pool.Pool.get(Pool.java:707)

at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl.java:261)

... 15 more

Caused by: com.sap.sql.log.OpenSQLException: JDBC driver not supported for ORACLE database.

at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:83)

at com.sap.sql.jdbc.direct.DirectConnectionFactory.createPooledConnection(DirectConnectionFactory.java:483)

I use driver ojdbc6.jar

Which driver i need and how can i change it to fix the error?

Regards,

Markus

[sergiy_katerinich · Accepted solution]

Hi Markus,

I would suggest submitting a support ticket to BC-EHP-INS component.

But if you want to fight with this issue yourself, you can try searching SAP Notes for "JDBC driver not supported for ORACLE database" - it will give you, for example, SAP Note 1161052 referencing to SAP Note 867976.

Regards,

Sergiy

[Former Member · Accepted solution]

hey all,

i replace the oracle client driver in C:\usr\sap\<instance>\SYS\exe\uc\NTAMD64

the sap notes SAP Note: 998004 & 997848 fix the problem.

Thanks!

Regards,

Markus

[Former Member · Accepted solution]

Hi guys,

The solution to the disp+work not starting up on the instance.

Stop the instance and the sapsid_xx service

copy the sapstartsrv.exe and sapstartsrv.exe.new files from the kernel directory - usr\sap\SID\SYS\uc\NTADM64\exe to the all exe directories.

Start the services and than start the instance

Regards,

Vikesh Jackison

Snr SAP Basis Administrator

+27 72 482 6240

vjackison@gmail.com