Skip to Content

Apologies for the detour, as I could not upload any more images.

Continuing from …

Upgrading SAP Kernel from Release 700 to SAP Kernel 720_REL / 720_EXT Part I of II

Deploy the IGSHELPER.SAR to the relevant local directory /usr/sap/<SID>/<INSTANCE> on every instance as shown below:

1.JPG

Now switch to user root and run shell script saproot.sh from the kernel directory

1.JPG

Delete all the local executable’s on the individual instances. To do this switch to local relevant executable directory /usr/sap/<SID>/<INSTANCE>/exe/ and execute rm -rf *


1.JPG

1.JPG

Since the executables from the local executable directory can be executed for the start before SAPCPE runs, start an initial copy of the executables.

For all application server instances (PAS, CI, AAS, DI, CI) & For Java Only Systems, perform the below:

If your system is running with the SAPJVM:

sapcpe pf=/usr/sap/<SID>/SYS/profile/<instance profile> source:<sapjvm directory> list:<sapjvm directory>/sapjvm_<version>.lst

Checking if the SAP system is using SAP JVM or 3rd Party JDK?

1.JPG

Execute SAPCPE now to sync the kernel directory:

1.JPG

Follow-up Activities

This step only applies to release 7.00 and 7.01 Dual-stack and Java only systems.

In all (Dxx, DVEBMGSxx, Jxx, JCxx etc) instance profiles, you must set the following parameter:

FN_JSTART= jcontrol$(FT_EXE)

1.JPG

You can start your SAP System now with the new SAP Kernel 720 (Check R3trans -x, Oracle DB & Listener should be up and running)

1.JPG

1.JPG

Well, WHAT DID JUST HAPPENED 😯 ?

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

I just switched to Local Instance Kernel directories and observed that all the executables were not replicated from the Global Kernel directory.

SAPCPE only replicated the JVM and other executables.

So, I manually copy all the executables from the Global Kernel Directory to all the Local Instance Specific Executable directories, and started the SAP system.

1.JPG

Voila. the SAP system started up like a champ πŸ™‚

1.JPG

And the SAP Kernel has been successfully upgraded to SAP KERNEL 720_REL Patch Level 401.

Best Regards,

Akshay.

To report this post you need to login first.

17 Comments

You must be Logged on to comment or reply to a post.

  1. Former Member

    Hello,

    Your blog is real good and i gained a lot of knowledge in kernel upgrade with your blog post and your explanation here is simple and sweet in kernel upgrade procedure…. πŸ™‚

    and i am having few doubts..?

    1. I have downloaded all the required components for kernel upgrade from the SMP,  now how i can copy these files into sap server(HP-UNIX) which is located in other country.

    2. How to create a soft link to sapmnt/sid/exe from usr/sap/sid/dvebmgs/exe.

    Thanks in advance. πŸ™‚

    (0) 
    1. Akshay Gupta Post author

      Hi Maruthi,

      Thanks for the kind words. Much appreciated!

      1) To copy the files to server located on outer network zone, you will have to figure out some bridge to reach there. My guess would be some local team (where your server is located) will be able to access the server locally and that’s your link. As this is HP-UX server I cant say much about using open network using Internet which is much possible between two windows machine anywhere on the planet just connected to Internet. Teamviewer and Ammy Admin take care of that in Windows, for Unix please check.

      2) Are you sure you would like to create this link by yourself? Usually once SAP System is installed the local executables (usr/sap/sid/dvebmgs/exe) are locally stored (In case of Distributed System). Anyways, here you go=>

      ln -s /sapmnt/sid/exe/ /usr/sap/sid/dvebmgs/exe

      -Akshay

      (0) 

Leave a Reply