SUM needs a disp+work that does not exist

[benoit-schmid]

Hello,

I am updating an ECC 6.04->6.07.

SUM complains with the following error.

---

ERROR: The executable disp+work in /usr/sap/EH7/SUM/abap/exe is too old.
It needs at least release 740
Download the new tools according to SAP Note 19466 and put the archives into the download directory.

---

We are using 7.20EXT on Solaris Sparc.

The latest dispatcher patch level is the following.

---

dw_518-20006767.sar

disp+work package

518

Info

208006

14.11.2013

---

As 518 is lower than 740, what am I supposed to do?

Does SAP wants me to update the kernel from 7.20EXT to 7.40?

Regards,

[Former Member · Accepted solution]

Hi,

Generate the stack xml again and start, Check whether you are able to find 740 kernel or not.

http://service.sap.com/mopz

If found start with new Kernel or try downloading kernel 740 and uncar in the /usr/sap/EH7/SUM/abap/newexe

This will work...

BR,

Prabhakar

[benoit-schmid · Accepted solution]

Hello,

Is my ECC 6.04 supposed to work with Kernel 7.40?

Do we agree that the answer is no?

If the previous answer is no do we agree that it is a very bad idea to uncar 740 Kernel

in my exe directory?

Regards,

[Former Member · Accepted solution]

Is my ECC 6.04 supposed to work with Kernel 7.40?

No it not supported...

So please create a new xml file...

Thanks

Rishi Abrol

[Reagan · Accepted solution]

Is my ECC 6.04 supposed to work with Kernel 7.40?

No. Kernel 7.40 will not work with systems with BASIS level below 740

Do we agree that the answer is no?

Yes I agree.

If the previous answer is no do we agree that it is a very bad idea to uncar 740 Kernel in my exe directory?

The exe directory which is used for the upgrade is /usr/sap/EH7/SUM/abap/exe.

The main system is not using this kernel location and you should not put the 7.40 kernel in the kernel location used by the main or primary system which is DIR_CT_RUN (/sapmnt/SID/exe) and DIR_EXECUTABLE (/usr/sap/SID/DVEBMGS00/exe).

All system switch upgrades are done using a shadow system.

The shadow system is created with the target level kernel and the upgrade is done there.

As you are upgrading the system to EHP7 then the kernel for the shadow system should be 7.40

Regards

RB

[JPReyes · Accepted solution]

You do not need to create a new xml file, simple download, uncar and upload the new 740 kernel in the SUM exe directory. That should be sufficient.

Regards, Juan

[Former Member · Accepted solution]

Hi

I agree with as I've just done this (yesterday in fact).  The 740 is the kernel you are going to  not the one you have currently. The 740 kernel in the update kit it too old and has some known bugs.

Regards,

Grhaam

[benoit-schmid · Accepted solution]

Hello,

I have recreated the xml.

The mopz did not proposed a 7.40 kernel.

Is it as expected?

Why do I have to manually copy the 740 Kernel in SUM exe directory?

Regards,

[Reagan · Accepted solution]

Benoit,

Did you get the option "Select OS/DB-Dependent Files" when you were creating the stack file using the Solution Manager Maintenance Optimizer Tx  ?

Regards

RB

[benoit-schmid · Accepted solution]

Hello,

Reagan Benjamin wrote:
Benoit,
Did you get the option "Select OS/DB-Dependent Files" when you were creating the stack file using the Solution Manager Maintenance Optimizer Tx  ?

Yes, but I could not select 7.40.

Only 7.20 and 7.21 were available.

Regards,

[benoit-schmid · Accepted solution]

Hello,

Juan Reyes wrote:
You do not need to create a new xml file, simple download, uncar and upload the new 740 kernel in the SUM exe directory. That should be sufficient.
Regards, Juan

Why is this not performed by the SUM?

Could you tell me again the directory where I should uncar?

Regards,

[former_member189797 · Accepted solution]

SUM did not have any 740 kernel files reference so it did not did it.

Correct directory will be...  ../SUM/abap/exe/

Regards,

Gaurav

[Reagan · Accepted solution]

Yes, but I could not select 7.40.
Only 7.20 and 7.21 were available.

Then the problem with MOPZ should be fixed.

I would raise an OSS message to SAP and get this fixed before continuing with the upgrade.

Regards

RB

[Reagan]

I believe you are updating the system to EHP7.

In what phase are you on ?

Bear in mind that if the basis release is lower than 7.40 the you should use kernel version 7.20 or 7.21

It appears to me that the kernel chosen for the EHP7 update is not 740 release

Regards

RB

[benoit-schmid]

Hello,

I have not found any 740 kernel reference in the stack file.

During the Mopz, I did not select any kernel because I had update

my system with the latest 7.20EXT Kernel.

The only ref to 740, I have in my stack file is for the gateway:

<name>SAP_GWFND</name><version>740</version>
<caption>SAP_GWFND 740: SP 0001</caption>

What am I supposed to do to continue my EHP 7 update?

Regards,

[Reagan]

You may recreate the stack file with 740 kernel and start the upgrade again.

Else the upgrade tool will use the old kernel and for EHP7 it is not compatible.

Regards

RB

[Former Member]

hi,

Please recreate the stack as to upgrade to EHP7 you will get 740 release and you have to fo to 740 kernel else you cant go to EHP7.

Thanks

Rishi Abrol

[benoit-schmid]

Helo Benjamin,

Reagan Benjamin wrote:
I believe you are updating the system to EHP7.
In what phase are you on ?

Yes this is for EHP7 as said in my first post.

I am in phase PREP_INIT/DBCHK_INI.

I will regenerate the stack an try back?

Regards,

[Reagan]

Schmid,

I will regenerate the stack an try back?

That is the correct path.

Also make sure that the source system is running on a compatible OS and DB for the EHP7 upgrade.

From EHP6 onwards there is a need to have a higher version of OS and DB.

Please check PAM for OS and DB compatibility for EHP7

Regards

RB

[former_member189797]

Hi Benoît,

Please check the PAM (Product Availability Matrix). Here you can see that supported kernel version for EHP7 is Version 740.

Please download the latest 740 kernel (both database dependent & Independent part) and update the kernel in the ..SUM/abap/exe/ directory.

This will solve the issue.

[benoit-schmid]

Hello,

Gaurav Kumar Pandey wrote:
Please download the latest 740 kernel (both database dependent & Independent part) and update the kernel in the ..SUM/abap/exe/ directory.

In which SUM phase should I uncar 740 Kernel?

Regards,

[ashish_vikas]

Hi,

there is a another way..

you can rename your .SAR files of release 740 to same as of .SAR files of release 720 as mentioned in stack XML.

After this, just place this in download directory and SUN will take care of extraction automatically.

best regards

ashish

[Former Member]

Hi,

Please generate the xml file using the solution manager . Dont manually change the files as it can cause other issues.

SO check the system settings if you thin it doesn't helps try to go to sap and get the fix.

Thanks

Rishi Abrol

[benoit-schmid]

Hello,

ashish vikas wrote:
you can rename your .SAR files of release 740 to same as of .SAR files of release 720 as mentioned in stack XML. 

I have performed almost like that.

I have edited the stack file to use the latest kernel 740 patch level.

Regards,

[benoit-schmid]

Hello,

Rishi Abrol wrote:
Please generate the xml file using the solution manager . Dont manually change the files as it can cause other issues.

As there is no way to tell the crappy Mopz that I want to use the latest patch level of 740

Kernel, I had to change the xml.

Regards,

[benoit-schmid]

Hello,

I now have a new problem that has nothing to do with the original post.

In the DBCONNCHK.LOG there is the following error.

---

4 ETW000  [    dbsloci.,00000]  *** ERROR => Connect via SAPUSER not supported for kernel >= 740.         47  0.031317
4 ETW000  [     dev trc,00000]     Only Secure Connect method possible.                                   39  0.031356

---

Hum, hum I am not at the end oh the EHP, as I have to use SSFS 😞

Regards,

[Former Member]

Hi,

Can only say that if some thing goes wrong during the upgrade then sap will not support you and have only one line "Please restore from backup and then restart the activity ".

Thanks

Rishi Abrol

[Reagan]

For SSFS check this SAP note

1622837  - Secure connection of AS ABAP to Oracle via SSFS

Regards

RB

[ashish_vikas]

it is asking for updated disp+work of Kernel release 740 not 7.20EXT.

You need to download and place this in /usr/sap/EH7/SUM/abap/exe.

best regards

ashish

[Former Member]

One more thing to add

For these SPs, the stack will contain an older version of the kernel than is already available in the system (SUM/abap/exenew).

For upgrade scenarios, it is in any case a requirement that you include the OS-specific kernel in the stack to ensure that the right stack.xml will be created.

For all higher SP stack levels, the SAP kernel that comes with the installation media will be too old to be used for the upgrade/update procedure. SUM/abap/exe will thus contain an outdated kernel. You have to manually update the kernel in SUM/abap/exe in module "Extraction" of the upgrade/update process, but only after phase "SCANDIR_EXTRACT".

SO it makes sure that you dint select the kernel 740 in the generation of the stack file and that is the reason it is looking for 720 kernel in the /exe directory rathere than /newexe

Thanks

Rishi Abrol

[Former Member]

Hi,

It is not talking about the kernel patch level . It want kernel 740 version not 740 patch.

Did you select the kernel related file while generating the stack files.

Try to download kernel 740 and uncar in the /usr/sap/EH7/SUM/abap/newexe.

Dont forget to take backup of this directory.

Thanks

Rishi abrol