cancel
Showing results for 
Search instead for 
Did you mean: 

Kernel upgrade not reflected in disp+work and in system status

ashit_mehra1
Explorer
0 Kudos

I have upgraded the kernel to 401 patch from 300.It is a 64 bit system.But the patch showing in the system status and disp+work is still 300.I did the same thing for other systems and I was successful.

What can be the issue?Pls help..

Accepted Solutions (0)

Answers (11)

Answers (11)

ashish_mishra2
Contributor
0 Kudos

You might like to have a look at below URLs:

http://scn.sap.com/thread/1913201

https://scn.sap.com/thread/863800

ashish_mishra2
Contributor
0 Kudos

Hi Ashit,

I checked 15+ cases and in all cases 90% issue was due to corrupted SAR file and 10% different release of SAPCAR executable.

No other reason of this problem.

Check and compare the *.SAR file size from other servers where in you were able to extract successfully.

Cheers !!!

Ashish

Reagan
Advisor
Advisor
0 Kudos

Hello

The way you are extracting the .SAR files are wrong.

You need to first rename the SAPCAR file present at the kernel location.

mv SAPCAR LSAPCAR

LSAPCAR -xvf SAPEXE.SAR

LSAPCAR -xvf SAPEXEDB.SAR

The reason is that there is also an SAPCAR in the .SAR file and if there is one present in that location the extraction will fail when it is extracting SAPCAR from the archive.

Regards

RB

Reagan
Advisor
Advisor
0 Kudos

Why don't you extract the .SAR files into a temporary location first and then copy them to the kernel location ?

Regards

RB

ashit_mehra1
Explorer
0 Kudos

Hi Reagan,

I copied the files manually also...but still when I hit disp+work it is not showing the upgraded patch.

Also the kernel at /sapmnt/GAQ/exe is the kernel that I want and I have already rebooted the system.But it is still not reflecting.

AtulKumarJain
Active Contributor
0 Kudos

Hi Ashit,

Can you please check your env setting . this may be due to env pointing to old kernel location .Please check and correct it. after changing the env you need to restart the sap .

BR

Atul

Former Member
0 Kudos

Hi,

Or Just try to do a find command and see where all you can find Disp+Work.

Try to copy the dips+work from another os.

Why dont you use disp+work -v command in all the above directory and see which one is wrong..

Thanks

Rishi Abrol

ashit_mehra1
Explorer
0 Kudos

Can u pls guide me as to how to check the env setting?

ashish_mishra2
Contributor
0 Kudos

Hi Ashit,

This happens at times when your all kernel locations are not up to date. which means disp+work is being picked from location where in still old files exists.

To find this, use command  'which disp+work'

this will give u complete path from where this executable is being picked and then update that location too with your updated kernel files.

Hope this resolves your problem.

Cheers !!!

Ashish

AtulKumarJain
Active Contributor
0 Kudos

Hi Ashit,

Please check env using command env once you logon to os level with sidadm user (in linux ,unix os ) if it is window then you can check from 

http://www.computerhope.com/issues/ch000549.htm

you can check current env using report  RSBDCOS0 ,it can be runfrom se38.

BR

Atul

ashit_mehra1
Explorer
0 Kudos

Hi atul,

u were right.The patch on the path in env is 300.But when i tried to UNCAR it it showed the error:

SAPCAR: error in GetEntryData(); unknown block type (error 100). No such file or directory.

ashit_mehra1
Explorer
0 Kudos

Hi Ashish,

I think the error which I mentioned to atul is the main cause.

I tried 'which disp+work command' nd have already updated that path earlier.

AtulKumarJain
Active Contributor
0 Kudos

Hi Ashit,

Good to here , you have found the root cause of the issue , if your issue resolved please mark this thread as answered.

Thanks for your understanding.

BR

Atul

ashit_mehra1
Explorer
0 Kudos

Hi atul,

Can you give a solution to the error?

AtulKumarJain
Active Contributor
0 Kudos

Hi Ashit,

Could you please provide which comand you are running.

please attach screen shot of the issue ,but it seems the above issue due to corrupt s/w either sapcar or .sar file .

Please download again and try it.

BR

Atul

ashish_mishra2
Contributor
0 Kudos

Hi Ashit,

This error means that the SAR file you are trying to uncar using SAPCAR is corrupted.

Please, be sure that you did transfer (ftp) to the server in binary mode.

Such error also happens when the .SAR archives are corrupt.

Cheers !!!

Ashish

ashit_mehra1
Explorer
0 Kudos

I used the same .SAR files for updating 6 other systems.So I dont think that is the issue.

Also I transfered it in binary mode only.

ashit_mehra1
Explorer
0 Kudos

I am using command: SAPCAR -xvf SAPEXEDB_402-20005274.SAR.

I am attaching the screenshot of the issue:

Reagan
Advisor
Advisor
0 Kudos

Hello

The way you are extracting the .SAR files are wrong.

You need to first rename the SAPCAR file present at the kernel location.

mv SAPCAR LSAPCAR

LSAPCAR -xvf SAPEXE.SAR

LSAPCAR -xvf SAPEXEDB.SAR

The reason is that there is also an SAPCAR in the .SAR file and if there is one present in that location the extraction will fail when it is extracting SAPCAR from the archive.

Regards

RB

ashit_mehra1
Explorer
0 Kudos

It is still showing the same error

Reagan
Advisor
Advisor
0 Kudos

Download the latest SAPCAR from the market place and use that.

You may extract the kernel to a temporary place before moving it to the /sapmnt/SID/exe location.

Regards

RB

Former Member
0 Kudos

Hello Ashit,

FTP the SAR files again and try.  Hope it works fine or else atleaset  it will remove the probability of the files being corrupt.  🙂

Mudasir

AtulKumarJain
Active Contributor
0 Kudos

Hi Ashit,

Can you change the owner of .SAR file  to sideadm and try it again.

BR

Atul

Former Member
0 Kudos

Hi,

Why cant you just copy the kernel from some other system which is on the same release that is working fine.

Thanks

Rishi Abrol

AtulKumarJain
Active Contributor
0 Kudos

Hi Ashit,

You can uncar the above SAR file at another dir or on different server and after that copy uncared kernel to present kernel location and adjust the kernel exe owner and group.

BR

Atul

ashit_mehra1
Explorer
0 Kudos

Thank you all for your replies.

I checked on both the paths and also the path on rsparam in SE38.All have the new patch files but still the patch number is not reflecting.

I have attached the beginning og the sapcpe.log file.Pls check.

Reagan
Advisor
Advisor
0 Kudos

Hello

This screen shot is not sufficient.

First check whether the kernel you have at /sapmnt/GAQ/exe is the one you want.

su - gaqadm

cdexe

./disp+work -V | head -50

If yes then :

Stop the SAP system and copy the kernel manually.

cp -rhp /usr/sap/GAQ/SYS/exe/run/* /usr/sap/GAQ/DVEBMGS00/exe

Start the SAP system

Regards

RB

Former Member
0 Kudos

Hi,

Did you run disp+work -v in both the directory with SIDADM.

Check that all the permission is fine.

As you told that you did it for other system then it rule out the fact of kernel or support pack issue as you can see in other system.

Thanks

RishiA brol

Former Member
0 Kudos

sapmanifest.mf in exe directory contains the actual kernel patch level. Kernel patch level and disp+work (or other executables') patch level can be different.

Below is an example of sapmanifest.mf where kernel patch level is 402 and disp+work patch level is 401.

If your sapmanifest.mf has kernel patch level as 401 and disp+work patch level as 300 then there is no issue. Otherwise you will have to check what went wrong in kernel upgrade.

sapmanifest.mf:

---------------------------------------------------------------------------------------------------

Manifest-Version: 1.0

keyname: SAP_KERNEL

keyvendor: sap.com

keylocation: SAP AG

kernel release: 720

kernel patch number: 402

kernel os: linuxx86_64

compilation mode: UNICODE

compiled for: 64 BIT

make variant: 720_REL

downward-compatible to: 700 710 701 702 703 711 720 730 731 732

patch number ILE: 324

patch number LDAP Connector: 400

patch number R3check: 210

patch number R3ldctl: 324

patch number R3load: 324

patch number R3szchk: 324

patch number R3ta: 324

patch number R3trans: 324

patch number RSecSSFx: 213

patch number SAPCAR: 315

patch number SAPSLDREG: 210

patch number SAPinst: 0

patch number SAProuter: 314

patch number ccmagent: 324

patch number cleanipc: 212

patch number cpictlib: 0

patch number db2jcllib: 70

patch number db2radm: 324

patch number dbsl: 327

patch number disp+work: 401

patch number enqueue: 318

patch number gateway: 327

patch number icman: 324

patch number jcmon: 108

patch number jcontrol: 108

patch number jlaunch: 108

patch number jsmon: 43

patch number jstart: 63

patch number lgtst: 0

patch number librfc: 320

patch number mdx: 220

patch number msgserver: 413

patch number relinfo: 401

patch number rslgcoll: 117

patch number rslgsend: 2

patch number sapacosprep: 322

patch number sapcpe: 316

patch number sapevt: 322

patch number sapftp: 315

patch number saphttp: 324

patch number sapiconv: 210

patch number saplicense: 312

patch number saplikey: 312

patch number sapmc: 5

patch number sappfpar: 109

patch number sapstart: 323

patch number sapxpg: 215

patch number showipc: 212

patch number snmplib: 320

patch number sybctrl: 327

patch number tp: 324

patch number vscan_rfc: 64

---------------------------------------------------------------------------------------------------

Regards,

Amol Thorat

ashit_mehra1
Explorer
0 Kudos

I checked the sapmanifest.mf file.The patch level of disp+work there also is 401.

As mentioned earlier I have applied the same patch to other systems also but this issue did not come there.

Former Member
0 Kudos

You can try restart the application server again and check. Clean all sidadm processes and memory using sapcontrol, cleanipc and ipcrm.

Regards,

Amol Thorat

former_member183107
Contributor
0 Kudos

Check as instructed by RB and Prabhakar.

if the replication still fails, see DVEBMGS00\work\sapcpe.log for details.

Regards,

Himanshu

AtulKumarJain
Active Contributor
0 Kudos

Hi Ashit,

Please check the disp+work at below mention location

/usr/sap/SID/*/exe

/sapmnt/SID/exe.

then you will come to know what is the issue , please check sapcpe log in work dir .

Best Regards,

Atul

Former Member
0 Kudos

Hi,

- start your SAP system

- logon to it

- run transactoin SE38 and report rsparam

- check the value of DIR_CT_RUN (the source directory of the replictaion process)

  this is the directory where you have to unpack the patches to

- check the value of DIR_EXECUTABLE (the destination directory of the sapcpe replication and the instance executable directory)

- if the replication still fails, see DVEBMGS00\work\sapcpe.log for details.

BR,

Prabhakar

Reagan
Advisor
Advisor
0 Kudos

You need to put the new kernel at DIR_CT_RUN location and then make sure that the sapcpe program replicates to the DIR_EXECUTABLE location.

DIR_CT_RUN = /sapmnt/SID/exe

DIR_EXECUTABLE = /usr/sap/SID/DVEBMGS00/exe

Regards

RB

Former Member
0 Kudos

Hi,

Try to check the version in the below two directory.

/usr/sap/SID/*/exe

/sapmnt/SID/exe.

Thanks

RishI Abrol