cancel
Showing results for 
Search instead for 
Did you mean: 

Software Update Manager error - Could not detect SAP JVM on system

0 Kudos

Dear Experts

I am trying to upgrade Solution Manager 7.1 from SPS04 to SPS07.

I am receiving this problem when it fails with the error below. My profile parameters point to the correct location where the SAPJVM 4.1.026 is but still the SUM insists on looking for 4.1.016. From where could it be getting this parameter?

Could not detect system components. Could not detect SAP JVM on the system. com.sap.sdt.j2ee.tools.sapjvm.SapJvmException: Profile parameter DIR_CT_SAPJVM points to directory /usr/sap/SMQ/SYS/exe/jvm/linuxx86_64/sapjvm_4.1.016 but it does not exist

Feb 3, 2013 9:29:27 AM [Error ]: The following problem has occurred during step execution: com.sap.sdt.jspm.gui.SystemDetectionException: Could not detect system components.

Could not detect SAP JVM on the system.

com.sap.sdt.j2ee.tools.sapjvm.SapJvmException: Profile parameter DIR_CT_SAPJVM points to directory /usr/sap/SMQ/SYS/exe/jvm/linuxx86_64/sapjvm_4.1.016 but it does not exist.

Feb 5, 2013 10:26:48 AM [Info  ]: Number of source deployed components detected from components provider: 26

Feb 5, 2013 10:26:55 AM [Error ]: The following problem has occurred during step execution: com.sap.sdt.jspm.gui.SystemDetectionException: Could not detect system components.

Could not detect SAP JVM on the system.

com.sap.sdt.j2ee.tools.sapjvm.SapJvmException: Profile parameter DIR_CT_SAPJVM points to directory /usr/sap/SMQ/SYS/exe/jvm/linuxx86_64/sapjvm_4.1.016 but it does not exist.

com.sap.sdt.j2ee.tools.sapjvm.SapJvmException: Profile parameter DIR_CT_SAPJVM points to directory /usr/sap/SMQ/SYS/exe/jvm/linuxx86_64/sapjvm_4.1.016 but it does not exist.

Profile parameter for DVEBMGS00

SAPSYSTEMNAME = SMQ

SAPSYSTEM = 00

INSTANCE_NAME = DVEBMGS00

DIR_CT_RUN = $(DIR_EXE_ROOT)/run

DIR_EXECUTABLE = $(DIR_INSTANCE)/exe

#DIR_SAPJVM = $(DIR_EXECUTABLE)$(DIR_SEP)sapjvm_4

DIR_SAPJVM = /sapmnt/SMQ/exe/jvm/linuxx86_64/sapjvm_4.1.026

DIR_CT_SAPJVM = /sapmnt/SMQ/exe/jvm/linuxx86_64/sapjvm_4.1.026

jstartup/vm/home = $(DIR_SAPJVM)

FN_JSTART = jcontrol$(FT_EXE)

jstartup/trimming_properties = off

jstartup/protocol = on

jstartup/max_caches = 500

jstartup/release = 700

jstartup/instance_properties = $(jstartup/j2ee_properties):$(jstartup/sdm_properties)

j2ee/dbdriver = $(DIR_EXECUTABLE)/db2jcc.jar:$(DIR_EXECUTABLE)/db2jcc_license_cu.jar

exe/saposcol = $(DIR_CT_RUN)/saposcol

ssf/name = SAPSECULIB

sec/libsapsecu = $(DIR_EXECUTABLE)$(DIR_SEP)$(FT_DLL_PREFIX)sapsecu$(FT_DLL)

ssf/ssfapi_lib = $(sec/libsapsecu)

rdisp/wp_no_dia = 10

rdisp/wp_no_btc = 3

exe/icmbnd = $(DIR_CT_RUN)/icmbnd

rdisp/j2ee_start_control = 1

rdisp/j2ee_start = 1

rdisp/j2ee_libpath = $(DIR_EXECUTABLE)

exe/j2ee = $(DIR_EXECUTABLE)/jcontrol$(FT_EXE)

rdisp/j2ee_timeout = 600

rdisp/frfc_fallback = on

icm/HTTP/j2ee_0 = PREFIX=/,HOST=localhost,CONN=0-500,PORT=5$$00

icm/server_port_0 = PROT=HTTP,PORT=80$$,TIMEOUT=240,PROCTIMEOUT=600

#-----------------------------------------------------------------------

# SAP Message Server parameters are set in the DEFAULT.PFL

#-----------------------------------------------------------------------

ms/server_port_0 = PROT=HTTP,PORT=81$$

rdisp/wp_no_enq = 1

rdisp/wp_no_vb = 1

rdisp/wp_no_vb2 = 1

rdisp/wp_no_spo = 1

icm/server_port_1 = PROT=SMTP,PORT= 25000

rsdb/obj/buffersize = 50000

abap/shared_objects_size_MB = 100

ipc/shm_psize_10 = 136000000

ipc/shm_psize_40 = 112000000

SAPJVM_VERSION = 4.1.026

Profile parameter for DVEBMGS02

SAPSYSTEMNAME = SMQ

# Modify instance number during downtime

#SAPSYSTEM = 00

SAPSYSTEM = 02

# Modify instance number during downtime

#INSTANCE_NAME = DVEBMGS00

INSTANCE_NAME = DVEBMGS02

DIR_CT_RUN = $(DIR_EXE_ROOT)/run

DIR_EXECUTABLE = $(DIR_INSTANCE)/exe

#DIR_SAPJVM = $(DIR_EXECUTABLE)$(DIR_SEP)sapjvm_4

DIR_SAPJVM = /sapmnt/SMQ/exe/jvm/linuxx86_64/sapjvm_4.1.026

DIR_CT_SAPJVM = /sapmnt/SMQ/exe/jvm/linuxx86_64/sapjvm_4.1.026

jstartup/vm/home = /sapmnt/SMQ/exe/jvm/linuxx86_64/sapjvm_4.1.026

FN_JSTART = jcontrol$(FT_EXE)

jstartup/trimming_properties = off

jstartup/protocol = on

jstartup/max_caches = 500

jstartup/release = 700

jstartup/instance_properties = $(jstartup/j2ee_properties):$(jstartup/sdm_properties)

j2ee/dbdriver = $(DIR_EXECUTABLE)/db2jcc.jar:$(DIR_EXECUTABLE)/db2jcc_license_cu.jar

exe/saposcol = $(DIR_CT_RUN)/saposcol

ssf/name = SAPSECULIB

sec/libsapsecu = $(DIR_EXECUTABLE)$(DIR_SEP)$(FT_DLL_PREFIX)sapsecu$(FT_DLL)

ssf/ssfapi_lib = $(sec/libsapsecu)

# *** TEMPORARY 702 CHANGE ***

#rdisp/wp_no_dia = 10

# *** TEMP 702 CHANGE ***

#rdisp/wp_no_dia = 2

rdisp/wp_no_dia = 6

rdisp/wp_no_btc = 3

exe/icmbnd = $(DIR_CT_RUN)/icmbnd

rdisp/j2ee_start_control = 1

# *** TEMPORARY 702 CHANGE ***

#rdisp/j2ee_start = 1

rdisp/j2ee_start = 1

rdisp/j2ee_libpath = $(DIR_EXECUTABLE)

exe/j2ee = $(DIR_EXECUTABLE)/jcontrol$(FT_EXE)

rdisp/j2ee_timeout = 600

rdisp/frfc_fallback = on

#icm/HTTP/j2ee_0 = PREFIX=/,HOST=localhost,CONN=0-500,PORT=5$$00

#icm/HTTP/j2ee_0 = PREFIX=/,HOST=localhost,CONN=0-500,PORT=5$$00

#icm/HTTP/j2ee_0 = PREFIX=/,HOST=localhost,CONN=0-500,PORT=5$$00

#icm/HTTP/j2ee_0 = PREFIX=/,HOST=localhost,CONN=0-500,PORT=5$$00

icm/HTTP/j2ee_0 = PREFIX=/,HOST=localhost,CONN=0-500,PORT=5$$00

#icm/server_port_0 = PROT=HTTP,PORT=80$$,TIMEOUT=240,PROCTIMEOUT=600

#icm/server_port_0 = PROT=HTTP,PORT=80$$,TIMEOUT=240,PROCTIMEOUT=600

#icm/server_port_0 = PROT=HTTP,PORT=80$$,TIMEOUT=240,PROCTIMEOUT=600

# *** TEMP 702 CHANGE ***

#icm/server_port_0 = PROT=HTTP,PORT=80$$,TIMEOUT=240,PROCTIMEOUT=600

#-----------------------------------------------------------------------

# SAP Message Server parameters are set in the DEFAULT.PFL

#-----------------------------------------------------------------------

#ms/server_port_0 = PROT=HTTP,PORT=81$$

#ms/server_port_0 = PROT=HTTP,PORT=81$$

#ms/server_port_0 = PROT=HTTP,PORT=81$$

#ms/server_port_0 = PROT=HTTP,PORT=81$$

ms/server_port_0 = PROT=HTTP,PORT=81$$

# Entries for configuring a stand-alone enqueue. Integrated enqueue is no longer supported for kernel 802 and higher.

#rdisp/wp_no_enq = 1

# *** TEMPORARY 702 CHANGE ***

#rdisp/wp_no_vb = 1

rdisp/wp_no_vb = 2

rdisp/wp_no_vb2 = 1

# *** TEMPORARY 702 CHANGE ***

#rdisp/wp_no_spo = 1

rdisp/wp_no_spo = 0

icm/server_port_1 = PROT=SMTP,PORT= 25000

rsdb/obj/buffersize = 50000

abap/shared_objects_size_MB = 100

# *** TEMPORARY 702 CHANGE ***

#ipc/shm_psize_10 = 136000000

ipc/shm_psize_10 = 200000000

ipc/shm_psize_40 = 112000000

# Modify instance number during downtime

rdisp_sna_gw_service = sapgw02

# Entries for support of High-Availibitity release 702

#rdisp/enqname = smq_SMQ_02

# *** TEMPORARY 702 CHANGE ***

# *** TEMP 702 CHANGE ***

#rdisp/btctime = 60

rdisp/btctime = 5

rdisp/btcname = smq_SMQ_02

rdisp/max_wprun_time = 0

rsdb/pmandt = 000

login/system_client = 000

rdisp/bufrefmode = sendoff,exeauto

rdisp/TRACE = 1

transport/during_upgrade = ON

DIR_TRANS = /usr/sap/SMQ/SUM/abap

DIR_PUT = /usr/sap/SMQ/SUM/abap

rdisp/system_needs_spool = false

rspo/spool_id/use_tskh = 0

rec/client = OFF

abap/buffersize = 400000

rdisp/autoabaptime = 0

rdisp/start_icman = false

vmcj/enable = off

# Entries for configuring a stand-alone enqueue. Integrated enqueue is no longer supported for kernel 802 and higher.

enque/serverhost = smq

enque/serverinst = 02

enque/encni/port = 50219

enque/process_location = REMOTESA

# *** TEMP 702 CHANGE ***

rdisp/wp_no_enq = 1

rsdb/rep/fast_touch = off

rsdb/staton = 0

auth/object_disabling_active = N

rdisp/accept_remote_trace_level = 0

rdisp/auto_vb_stop = 0

jstartup/signal_handling = 0

SAPJVM_VERSION = 4.1.026

Accepted Solutions (1)

Accepted Solutions (1)

JPReyes
Active Contributor

Did you upgrade your SAPJVM manually?... was 4.1.016 your previous version?...

Regards, Juan

0 Kudos

During the initial installation of Solution Manager 7.1 and when we are choosing the SAPJVM, i chose the SAPJVM 4.1.026 which i had downloaded earlier. This issue is occuring when I updating from SPS04 to SPS07. Its basically a new installation and an immediate update after that.

Former Member
0 Kudos

Hi,

    To make is simple, try to create a soft link  for /usr/sap/SMQ/SYS/exe/jvm/linuxx86_64/sapjvm_4.1.016 which points to  /sapmnt/SMQ/exe/jvm/linuxx86_64/sapjvm_4.1.026

And try again.

Thanks and Regards,

Vimal

0 Kudos

Thanks

It worked. Plus also had to create a link for the sapjvmmanifest file

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi

Have you checked your OS Environment Variables as it's going to read them for installations/patching.

Regards,

Graham