on 11-20-2013 7:26 AM
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..
You might like to have a look at below URLs:
http://scn.sap.com/thread/1913201
https://scn.sap.com/thread/863800
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Why don't you extract the .SAR files into a temporary location first and then copy them to the kernel location ?
Regards
RB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
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
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
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
Check as instructed by RB and Prabhakar.
if the replication still fails, see DVEBMGS00\work\sapcpe.log for details.
Regards,
Himanshu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Try to check the version in the below two directory.
/usr/sap/SID/*/exe
/sapmnt/SID/exe.
Thanks
RishI Abrol
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
81 | |
25 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.