cancel
Showing results for 
Search instead for 
Did you mean: 

Kernel Change

Private_Member_19084
Active Contributor
0 Kudos

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

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

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

Private_Member_19084
Active Contributor
0 Kudos

First thx for help.

But now I am confused lol

the /usr/sap/<sid>/SYS/exe/uc exists but it is a link to /sapmnt/<sid>/exe/uc.

And when I go to /sapmnt/<sid>/exe/ there don't exists an directory called "uc".

Any ideas?

JPReyes
Active Contributor
0 Kudos

Your kernel should be in /sapmnt/<sid>/exe as this is an HPUX box. Vishal example is for a Windows box.

Regards, Juan

Private_Member_19084
Active Contributor
0 Kudos

thx Juan,

and which directory is it in /sapmnt/<sid>/exe/ ?

Do I only have to:

1. stop new sap system

2. copy /sapmnt/<sid>/exe/<unknown dir> to /sapmnt/<new sid>/exe/...

3. start new sap system

and the kernel is changed?

Thx

former_member189725
Active Contributor
0 Kudos

Yes you will have to do the steps you mentioned .

Make sure after the copy , you have the right permission of the executables.

Regards

Ratnajit

Private_Member_19084
Active Contributor
0 Kudos

ok,

but which directory in /sapmnt/<sid>/exe/ do I have to copy?

The whole /exe/?

Thx

JPReyes
Active Contributor
0 Kudos

Replacing the kernel is basic stuff. follow SAP Note 19466, simply you wont have to decompress the kernel only move it, make sure you don't replace your old kernel just in case you need it later, also pay attention to the file permissions.

Regards, Juan

Private_Member_19084
Active Contributor
0 Kudos

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

JPReyes
Active Contributor
0 Kudos

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

Private_Member_19084
Active Contributor
0 Kudos

ok, this I already understood.

But which files in /exe/ do I have to copy?

I doubt that I have to copy the whole /sapmnt/<sid prod>/exe to /sapmnt/<sid new>/exe or?

Sorry for the stupid question, but I could not find the answer in 19466.

Thx

JPReyes
Active Contributor
0 Kudos

the contents of exe is the kernel.

Regards, Juan

Former Member
0 Kudos

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

Private_Member_19084
Active Contributor
0 Kudos

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

Former Member
0 Kudos

Hi,

You don't need to care about permissions, as long as you extract/copy the files as <sid>adm.

Although, sometimes I have had to "chown" the oracle dba tools (br*) files before extraction.

BR,

Samuli

Former Member
0 Kudos

The standard procedure is to run the script saproot.sh ( You can find that in /sapmnt/<SID>/exe Dir)

as a root user. This will change the permissions of br* files ans SAPOSCOL.

Proceed as follows:-

stopsap

su - root

cd
/sapmnt/<SID>/exe

./saproot.sh
<SID>

exit

startsap

Cheers,

Vishal

Answers (1)

Answers (1)

Private_Member_19084
Active Contributor
0 Kudos

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!

JPReyes
Active Contributor
0 Kudos

Step 4 was not necesary because SAPCPE would have copied the new kernel to all required locations. But your procedure certainly would have given the desired results.

Regards, Juan