SystemInformation doesn't display the current SP level after upgrading NW07

[Former Member]

Hi

I have updated a fresh installation of Nw2004s SR1 with Support pack SP07 to SP12. While upgrading I followed the guide “SAP NetWeaver 2004s Support Package Stack Guide — SPS12”

I used JSPM to apply all the support packages and it was successfully done.

Then to upgrade the kernel, I did the following steps

1. I extracted the SAPEXE_102-20000972.SAR ,SAPEXEDB_102-20000974.SAR , IGSEXE_8-10003070.SAR to a temp directory .

2. Then shut down the j2ee server (all instances and all services) completely

3. Then kept a backup of DIR_CT_RUN.

4. Copy the newly extracted components at temp directory to DIR_CT_RUN

5. Restarted all services and j2ee engine. It started the server successfully

The upgrade is visible in SDM and JSPM, but

When I used to see the System Information(http://host:port/sap/monitoring/SystemInfo), it is still showing me the old SP details. That is

sap.com/SAP-JEECOR 7.00 SP7

sap.com/SAP-JEE 7.00 SP7

So was the version of all components are the showing the old version

While trying to open Visual Admin, I am getting the following warning message

“Warning: J2EE Engine Kernel Version is older than the version of Visual Administrator”

J2EE Engine Kernel Version:SP7

Visual Administrator Version:SP12

Can any body tell me why this is happening and how to fix this issue?

Thanks

Arati

[Former Member]

Resolved by self

Possible Reason

Component versions are updated in the SDM GUI but

not in the JSPM GUI. SDM does not update the versions of

the deployed components in the database but onlyin the SDM repository.

Solution

To synchronize the database and the SDM repository:

1.Go to the /usr/sap/<SID>/<Central instance name>/

SDM/program directory.

2.Run the StopServerscript file.

3.In the command line, execute the following commands:

sdm jstartup #mode=standalone#

sdm systemcomponentstate #mode=activate#

sdm jstartup #mode=integrated#

4. Run the StartServer script file.

5. Restart JSPM

For more details,kindly refer to following SAP Documentation.

http://help.sap.com/saphelp_nw2004s/helpdata/en/

56/86e342599e5a04e10000000a155106/frameset.htm

[JPReyes]

Hi Arati,

Seems like the j2ee kernel was not updated... is the version displaying correctly on JSPM???

regards

Juan

[Former Member]

Hi Juan,

The upgrade versions are correctly shown in SDM and JSPM. That is in SDM it shows the version as SP12.

Below are the JSPM logs for those two packages specifically

-

---

#1.5 #C0000A081CD5000000000881010E3293000436C6EE390F40#1186127934984#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.deployment.deploy.DeploymentManager.updateItemResults(DeploymentManager.java:1667)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.deployment.deploy.DeploymentManager.updateItemResults(DeploymentManager.java:1667)#Java###Deployment message for component : #2#SAP-JEE#Archive

vmeiPE5
sapmnt
trans
EPS
in
SAPJEE12_0-10003469.SCA has been deployed.. <b>Software component SAP-JEE deployment messages:</b>. # #1.5 #C0000A081CD5000000000882010E3293000436C6EE390F40#1186127934984#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.deployment.deploy.DeploymentManager.updateItemResults(DeploymentManager.java:1667)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.deployment.deploy.DeploymentManager.updateItemResults(DeploymentManager.java:1667)#Java###Deployment message for component : #2#SAP-JEECOR#Archive

vmeiPE5
sapmnt
trans
EPS
in
SAPJEECOR12_0-10003466.SCA has been deployed.. <b>Software component SAP-JEECOR deployment messages:</b>. #

-

---

Is there any other way to upgrade kernel (NW07 J2EE Engine),other than the steps specified by me. If so please let me know

Regards

Arati

[Former Member]

Dear Arati ,

Please Check the SAP Note : 758298 ; How to move /update the Visual Administrator.

Regards,

Santosh Karadkar

[Former Member]

Hi Santosh ,

Thanks for reply,but the issue i am facing is different

My Visual Administrator is showing me correct version.I don't have to update that.

The problem is the J2EE kernel, not reflecting the current version after upgrade

Regards

Arati