Solved: Kernel upgrade failing

Former Member · ‎01-14-2013

Hello

I'm going through the process of upgrading the Kernel. We are running 720_REL, 64 bit, Unicode on Solaris 10 – current patch level 201. Our system is ERP6 EHP5.

The stack I've downloaded includes Kernel patch level 400. I've tried installing this (and also patch level 300) but get the same problem with both of these. When I revert to 201 the system still works OK.

I have successfully upgraded the Host Agent using the one included in the stack.

I now have 3 directories under /sapmnt/<SID>:

exe (patch level 201)
exe_300
exe_400

When I close the system & rename the directories (exe --> exe_201 & exe_400 --> exe) I restart the host agent (to force a restart of saposcol), then restart SAP.

The database opens OK & the application appears to begin correctly. When I try to connect to the application using SAPGui the dw.sap<SID>_DVEBMGS00 processes die.

I then get this error from SAPGui:

application server shutdown

Component DPTM Return Code -17

Release 720

Version 10

Return Code -17

counter 1

I have double checked permissions in the 3 subdirectories & all permissions are the same (the newer kernels have a few extra files).

I have found some references to similar problems as this using Google but people seem to be indicating that I'm getting a network error. Our network must be OK because the 201 version kernel works fine.

Can anyone advise why this might be failing?

Thanks, Chris

Reagan · ‎01-15-2013

Good Day

Please check the developer traces (dev_w0) and also provide the output for this command.

sapcontrol -nr 00 -function GetVersionInfo

Note : Replace 00 with the right system number

Cheers

RB

Former Member · ‎01-15-2013

As sugegsted by Reagan I manually copied the kernel to the local directory. I used find . -print | cpio -pumdB

So all files from the kernel are now in the local directory (/usr/sap/HRD/DVEBMGS00/exe) and it now works!

I can open & close the system OK, I can login (previously all the dw processes died when I tried this) & if I run sapcontrol -nr 00 -function GetVersionInfo the files it reports are patch level 400 not 201.

Many thanks but I assume I still have a more fundamental problem such that sapcpe isn't working correctly.

I need to fix this hopefully before I start putting the new kernel & associated patches onto our QA and Prod systems.

If anyone can offer any suggestions I'd be very grateful?

Chris

Former Member · ‎01-15-2013

Thank you for all the replies. I think I can see why it's failing but I haven't figured out how to fix it yet.

I ran

sapcontrol -nr 00 -function GetVersionInfo

as recommended by Reagan. What I see is that after installing the 400 patch the local directory is still running 201:

> /usr/sap/HRD/SYS/exe/run/sapcontrol -nr 00 -function GetVersionInfo

15.01.2013 11:46:15
GetVersionInfo
OK
Filename, VersionInfo, Time
/usr/sap/HRD/DVEBMGS00/exe/sapstartsrv, 720, patch 201, changelist 1315677, optu (Mar 20 2012, 03:09:56), sun_64, 2012 03 20 4:32:46
/usr/sap/HRD/DVEBMGS00/exe/disp+work, 720, patch 201, changelist 1315677, optu (Mar 19 2012, 20:13:48), sun_64, 2012 03 21 08 28:15
/usr/sap/HRD/DVEBMGS00/exe/gwrd, 720, patch 201, changelist 1315677, optu (Mar 19 2012, 20:13:48), sun_64, 2012 03 20 03:28:1 /usr/sap/HRD/DVEBMGS00/exe/msg_server, 720, patch 201, changelist 1315677, optu (Mar 20 2012, 03:09:56), sun_64, 2012 03 20 0 :22:46
/usr/sap/HRD/DVEBMGS00/exe/dboraslib.so, 720, patch 201, changelist 1315677, optu (Mar 19 2012, 20:13:48), sun_64, 2012 03 19 19:37:19
/usr/sap/HRD/DVEBMGS00/exe/enserver, 720, patch 201, changelist 1315677, optu (Mar 20 2012, 03:09:56), sun_64, 2012 03 20 04: 6:13
/usr/sap/HRD/DVEBMGS00/exe/icman, 720, patch 201, changelist 1315677, optu (Mar 20 2012, 03:09:56), sun_64, 2012 03 20 04:17: 6
/usr/sap/HRD/DVEBMGS00/exe/sapwebdisp, 720, patch 201, changelist 1315677, optu (Mar 20 2012, 03:09:56), sun_64, 2012 03 20 0 :18:39
/usr/sap/HRD/DVEBMGS00/exe/jcontrol, 720, patch 201, changelist 1315677, optu (Mar 20 2012, 03:09:56), sun_64, 2012 03 20 04: 3:55
/usr/sap/HRD/DVEBMGS00/exe/jlaunch, 720, patch 201, changelist 1315677, optu (Mar 20 2012, 03:09:56), sun_64, 2012 03 20 04:4 :03
/usr/sap/HRD/DVEBMGS00/exe/jstart, 720, patch 201, changelist 1315677, optu (Mar 20 2012, 03:09:56), sun_64, 2012 03 20 04:42 21
>

I assume sapcpe should fix this? I tried running sapcpe on the command line

sapcpe pf=/usr/sap/HRD/SYS/profile/HRD_DVEBMGS00_devsap

but discovered that we had no files defined in /usr/sap/HRD/SYS/exe/uc/sun_64.

I copied the file sapcpeft from the new kernel to this directory but it's now looking for all files listed here in /usr/sap/HRD/SYS/exe/uc/sun_64 which is empty apart form the file I've just copied.

Do I need to somehow tell the program to look in the central direcotry for source files? Where is this defined (not in the Instance profile file from what I can see).

Maybe we missed a step when we upgraded from 4.7 to ERP6 last year?

Thanks, Chris

Ranjith418 · ‎01-15-2013

Hello Vimal,

The kernel is basically stored in central directory of executable's (read one file system) which is mounted on other servers if the application servers are present on different hosts.

On Unix systems the /sapmnt/SID/exe (DIR_CT_RUN) is that location.

When you start an SAP system the sapcpe program copies the kernel from the /sapmnt/SID/exe (DIR_CT_RUN)

location to the (DIR_EXECUTABLE) /usr/sap/SID/DVEBMGS00/exe directories.

Are you trying to use 720 ext kernel? check the permissions of all the files inside exe and ensure oracle and brtool files are under respective owners and groups.

Thanks,

Ranjith

Former Member · ‎01-15-2013

Hi,

You MUST overwrite the exe folder not creating a new folder. Reason is there are many files which will not be available in the new Uncared Kernel. Perform the following steps.

1. Stop the SAP system & DB and check whether any SAP processes is running . If yes, please kill or end the processes

2. Take a backup of the exe which is working.

3. Uncar the latest Kernel and copy the contents to exe folder.

4.Run saproot.sh <SID> to set the br tools version.

5. Start the SAP system.

6. Check if SAP is running fine, if not, attach the dev_w0 and dev_disp files for further analysis.

Thanks and Regards,

VImal

Former Member · ‎01-14-2013

Hi

Dont use mv command on exe folder,for example my current patch is 102 i want upgrade to 300 if i move my current exe to exe_old(102) and created a new exe folder copied 300 patch in that created folder.in this secenario SAP will not up.

Because if u mv exe(102 patch) to exe_old,all soft link exist on this exe will not be available for your new exe folder created for 300 patch.

Thnaks.

Mahipal

Former Member · ‎01-14-2013

Hello Chris

Please follow SAP note https://service.sap.com/sap/support/notes/1636252

It has step by step instructions on kernel upgrade.

If you think you are following the exact steps then please try this out.

Once your kernel is upgrade and before starting the system go to profile directory

execute sappfpar check pf=<path to your instance profile > , make sure there are no errors.

A new kernel can also require you to increase shared pools.

If this does not fix it , then attach some logs for us to look at.

Regards

Amit Padmawar

divyanshu_srivastava3 · ‎01-14-2013

Hi Chris,

Please match the contents of other exe location..... This could also happen if due sync missing...... use sapcpe to sync..........

former_member185239 · ‎01-14-2013

Hi Chris,

Instaed of replacing the whole folder , /sapmnt/SID/exe with 300 or 400 , just replace the content of

/sapmnt/SID/exe with the kernal 300 or 400.

Also paste the logs for dev_disp and dev_ms , dev_w

With Regards

Ashutosh Chaturvedi

Kernel upgrade failing

Accepted Solutions (1)

Accepted Solutions (1)

Answers (8)

Answers (8)

Re: HTTP Receiver adapter with Dynamic value in UR...

How to create a rolling forecast in SAC? I have an...

In SAP Hana Cloud, do packages exist as database o...

Re: Mass Update a Zfield in Std Table with Split &...

Re: Change BW Query Initial Variable Input at runt...