Upgrade from R/3 4.7 ext 2.00 to ECC6 EHP7 on AIX 6.1 DB2 9.7.10

[Former Member]

Dear Experts,

O/s Version: AIX 6.1

DB version: DB2 9.7FP10

We are in process of upgrade from SAP R/3 4.7 ext 2 to ECC6 EHP7.  I have used maintenance optimizer to calculate media for the upgrade, Mopz calculated the target release as ECC6 EHP7 SP stack 07 with Kernel 7.42. Mopz did not add upgrade export media & Kernel DVD's to the download basket. As SUM tool was asking for Kernel DVD during Extraction phase, I have downloaded NW 7.42 Kernel DVD (Label: 51049350) & Upgrade export DVD's (Label 51048902_9, 51048902_10, 51048902_11, 51048902_12, 51048902_13 & 51048902_14) from SMP, uploaded to the server & gave the path of the DVD's. It went ahead but stuck up with below error in Extraction phase.

Error message is clearly stating that current DB version is not supported for Kernel 7.42. But I can not upgrade my DB to 10.5 as R/3 4.7 does not support DB2 10.5 version (there is no entry found in PAM).

I just wanted to understand

1) Why the stack.xml file (MOPZ) did not calculate the Kernel DVD & Upgrade export DVDs?(It has only calculated *.SAR files related to software components)

2) Why MOPZ has chosen incompatible Kernel (7.42 in my case) for the target release ?

The only option left is to recalculate the stack file by choosing the target kernel as 7.41 & download the media again. As my s-user ID license got expired I am not able to recalculate the stack.xml file again (SAP-OSS RFC is not working).

As a work around I have downloaded the 7.41 Kernel DVD (Label: 51049209) from SMP & gave 7.41 kernel path instead of 7.42 Kernel. SUM tool has detected the DVD, but it was not moving ahead.

I tried by changing the entries of kernel from 7.42 to 7.41, still SUM is redirecting in the same page.

Is there any way to move ahead with out regenerating the stack file (like by modifying the entries in the stack file) ?

BR,

Vinay

[Reagan · Accepted solution]

EHP7 is based on NetWeaver 7.4. The kernel 7.42 is select based on the target release and SP level. Check this SAP note 1969546 - Release Roadmap Kernel 740

In addition to the above there is also a requirement to have a higher version of DB to upgrade the systems to NetWeaver 7.8 SP08 and above.

1951491 - Minimal DB system platform requirements for SAP NetWeaver 7.4 SP08

RB

[Former Member · Accepted solution]

Hi Reagan,

Thanks for reply.

I have regenerated the stack file by choosing target Kernel as 7.41 UC (SPS04) & downloaded the media as per stack file & restarted the SUM tool.

I got stuck up at extraction phase, it's not moving ahead after giving Kernel, upgrade export DVD's path. It's redirecting in the same page after clicking on continue button.

[Former Member · Accepted solution]

It seems SUM is looking for upgrade master DVD, I am downloading below DVD & will check if it works.

51033520_15

ERP 6.0 SR3 UC-Upgrade Master AIX 64bit

ri3pa043:os2adm 11> pwd

/usr/sap/OS2/SUM/SUM/sdt/log

ri3pa043:os2adm 12> more MIDService.log

[Former Member · Accepted solution]

it did not work, still redirecting in the same page.

[former_member185954 · Accepted solution]

Hello Vinay,

Its probably a bug, please raise it to OSS.

Regards,

Siddhesh

[Reagan · Accepted solution]

Follow the SAP note 1300960 - Problems with MID-based DVDs during upgrade

[Former Member · Accepted solution]

Thanks Siddhesh.  I am in process of raising OSS message, need to get the approval from management.

BR,

Vinay

[Former Member · Accepted solution]

Hi Reagan,

I have already checked the note 1300960 - Problems with MID-based DVDs during upgrade(seems you have posted the same in another thread), but it did not help. I am going to raise OSS message.

BR,

Vinay

[Former Member]

Hi Siddhesh,

I have checked PAM, found below entry. There no entry found for 7.42 UC kernel & DB2 9.7.

BR,

Vinay

[former_member185954]

Okay, sorry I can't think of any reasons, hope you have raised OSS message for this ?

Regards,

Siddhesh

[former_member185954]

Hello Vinay,

I wouldn't try and modify the stack.xml manually.

Maybe its a bug, have you checked PAM before initiating these activities ?

Regards,

Siddhesh