on 05-22-2012 7:37 AM
Hi experts,
we have a new system.
This system actually has the kernel:
kernel release: 720
compilation: HP-UX B.11.23 U ia64 May 6 2010 20:44:45 (but sytem is a 11.31)
patch level 46
As we would like to use this system as a sandbox system, we would like to use the same kernel version as in the productive system.
This is the current version:
kernel release: 720
compilation: HP-UX B.11.31 U ia64 Nov 28 2011 21:15:07
patch level 114
So I would like to update the Kernel of the new system to the version of the productive sytem.
I already found the note 19466.
But I can't find the kernel pl on service marketplace.
Can someone please help me?
Would be great
thx in advance
Kernel patch level 144 seems to not available on the marketplace right now.
In this case you can raise an OSS message, they can provide you the path to download the same.
Or
There is work around, copy the directory \usr\sap\<SID>\SYS\exe\uc\NTAMD64 from your production system to the same path in sandbox system.
Regards,
Vishal
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hmmm
yes problem is (see above) that the PL which I need is not available on service marketplace.
I already read the note 19466.
Therein is written, that I have to back up the kernel directory /usr/sap/<SAPSID>/sys/exe/run.
So is the "run" directory the directory, which I have to copy from productive sytem to our new system?
Thx for help
Let me explain something to you... in a UNIX based system the directory where your decompress your kernel is /sapmnt/<sid>/exe why?.... when you start your system SAPCPE copies the kernel into usr/sap/<sid>/sys/exe/run and also serve as a base for distribution of the kernel to dialog instances.
So you should copy your kernel from /sapmnt/<sid>/exe
Regards, Juan
Hi Chris,
I would advise against REPLACING any files.
My common strategy of kernel update:
1) Find out where your kernel and executables are
cd <profile dir>
sappfpar pf=<instance profile>
DIR_CT_RUN <--- gives you the origin directory of kernel
DIR_EXECUTABLE <--- gives you the actual directory where your SAP instance is started
2) backup old kernel e.g. using SAPCAR:
cd <DIR_CT_RUN>
sapcar -cvf /tmp/SAPKERNELOLD.SAR *
3) stop your SAP system and startup service
stopsap r3
stopsap startupsrv
4) copy SAPCAR executable to other directory
cd <DIR_CT_RUN>
cp SAPCAR /tmp/
5) extract your SAR archives in this order
cd <DIR_CT_RUN>
/tmp/SAPCAR -xvf <path>/SAPEXE_XXX_YYYY.SAR
/tmp/SAPCAR -xvf <path>/SAPEXEDB_XXX_YYYY.SAR
/tmp/SAPCAR -xvf <path>/dw_xxx_yyyy-SAR
6) run sapcpe to replicate
cd <profile dir>
sapcpe pf=<instance profile>
7) check output of sapcpe to see if everything is OK
😎 Start your SAP instance
startsap r3
9) check trace and log files
BR,
Samuli
Before I anger on you, one last question lol.
If I do this way (copy exe from sapmnt) I don't have to check the permission of the files or?
Because at the startup the kernel files are copied automatically from /sapmnt/... to /usr/sap/... and so I guess this copy-process sets the correct permissions.
Or do I have to check the permissions on /sapmnt/<new sid>/exe?
And a great thank you again for help
Thx to all for fast help, I solved the problem now.
I guess, that you don't like my way, but it works (till now lol).
So I also post, what I've done.
1. I stopped sap
2. I checked the directory /sapmnt/<new sid>/exe/uc/hpia64 that it is empty
3. I copied the directory /sapmnt/<prod sid>/exe/ to /sapmnt/<new sid>/
4. I copied the directoy /usr/sap/<prod sid>/DVEBMGS(nr)/exe/ to /usr/sap/<new sid>/DVEBMGS(nr)/exe/
5. I started sap
Now I have exactly the same kernel as in the prod system.
Note. Don't forget to make a backup from the two dirs, which gets overwritten!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.