Skip to end of metadata
Go to start of metadata

Keywords

  • READ_PROFILES

Problem

During PREPARE unit of Java Upgrade(SAPJup), a 640 J2EE Engine may
be wrongly detected as 7.0. The reason for this is the existence of
JSPM directory and its contents under /usr/sap/<SID>/<Central
instance>/j2ee.

Symptoms

JSPM tool should not be available under the file system of 640 J2EE
Engines. It may happen at custemer systems when a system restore after a
previous upgrade was performed incorrectly. Since SAPJup uses JSPM
itself to detect the engine release, existence of JSPM will lead to
wrongly detected source system as 700.

You experience the following error?

Locate your latest <java upgrade dir>\log\READ_PROFILES_RBP_xx.LOG and look for the following error lines:

#/System/Server/Upgrade/Phases/PREPARE/INIT/READ_PROFILES##com.sap.sdt.j6
630.sysinfo.InfoController.determineProperties(InfoController.java:569)##
#####Thread[main,5,main]##0#0#Error#1#com.sap.sdt.j630.sysinfo.InfoContr
oller.determineProperties(InfoController.java:569)#Java###Error while
reading properties from
\usr\sap\J2E\SYS\profile\<SID>SCSxx<hostname>. Variables
[/J2EE/StandardSystem/ServiceInstance/MessagePort] not found. A possible
reason can be that the start release is lower than 6.40 SPS09.##

Solution

Apply

SAPNote: 1112766

Related SAP Notes

SAPNote: 1112766


  • No labels