The Full Monty – Part 6 – SPAM & Kernel Update
Previous blog The Full Monty – Part 5 – HTTPS & Sapcrypto
As I intend on importing some transports and performing some upgrades, SAP always recommends the Support Package Manager – SPAM, to be the latest.
Before I underwent any tasks, I browsed SDN for some useful information and found the following. Although they are a little dated, the principles still apply and are a great help. They talk about the downloads, unpackings, backup up, etc. In my case, I just went ahead and did it. Thomas Jung even has a Video. Check it out.
So, I download the latest SPAM version from the SAP Market Place. Note, your SAP User ID needs to have the correct access privilages.
Support Packages and Patches – Entry by Application Group->Additional Components->SAP SPAM/SAINT UPDATE->SPAM/SAINT UPDATE 701->Support Packages
In my case, it came in the form of a compressed file, KD70139.SAR (SPAM/SAINT Update – Version 701/0039 )
Logged on to the NSP as user DDIC, client 000, transaction SPAM, and the following message appears.
Next, got to the main screen
You can see from the title, that this is version 7.01/33. So I’ll be taking it up 6 revisions to 39.
Navigated to Support package->Load Packages->From Frontend
Located my SPAM update file – KD70139.SAR from the windows dialog box, and “Open”
Continued to “Decompress” the files
Upon successful decompression, the following message appeared
Now, I could perform the update, by going to Support Packages->Import SPAM/SAINT Update
“Tick” to continue, and the update commenced. The Status turned red, as it performed it’s various actions
About 20 mins in, I got a Runtime Error
I simply re-started SPAM, and the update, Support Packages->Import SPAM/SAINT Update, a prompt to continue the update occured, and after accepting the prompt, two seconds later, I was asked to re-start SPAM and check the version.
Here you have it
Upgrading the kernel is not as scarey as it sounds. In fact, it is one of the easiest tasks. I dare say, a few basis people will have something else to add.
You can tell what kernel version you are running by going from the main screen to System->Status->(Shift F5)
Download your kernel files, both SAPEXE and the SAPEXEDB versions. At the time of this writing, trying to download the SAPEXE, via the download manager, was causing a “cannot read file” error, displaying at the status bar of the download manager. I would sit there for ever, having a “partially downloaded” status. I managed to get the file through a colleague of my, so I can continue the blog.
As I mentioned at the beginning of the blog, there are two other blogs that do a great job in explaining the upgrade process. So, the following information I present, require reading with the blogs above.
Having said that, in short…
Download the latest Kernel versions from the SAP Market Place. Note, your SAP User ID will need to have the proper privilages access the files, also note, there may be slight differences with the exact file names due to versioning.
Go here, Support Packages and Patches – Entry by Application Group->SAP NetWeaver->SAP NETWEAVER->SAP EHP1 FOR SAP NETWEAVER 7.0->Entry by Component->Business Intelligence, then get both the database dependent, and database independent files from here,
SAP KERNEL 7.01 32-BIT->Windows Server on IA32 32bit->#Database independent->SAPEXE_69-10006350.SAR, Kernel Part I (for Basis 7.01)
SAP KERNEL 7.01 32-BIT->Windows Server on IA32 32bit->MaxDB->SAPEXE_69-10006346.SAR, Kernel Part II (for Basis 7.01).
I did the extraction into their own temporary directorys “sapexe” and “sapexedb”, and stopped the Windows Services as per the blog.
Instead of backing up the whole “c:usr” directory i simply renamed “C:usrsapNSPDVEBMGS00exe” to “C:usrsapNSPDVEBMGS00exe old”, and recreated a new “exe” so i ended up with a new “C:usrsapNSPDVEBMGS00exe”. I then copied the new unpacked kernel files over into the new “C:usrsapNSPDVEBMGS00exe”. First the files from the temporary “sapexe” directory, and then the files from the temporary “sapexedb” directory. There were four identical files which prompted me for replacement during the “sapexedb” copy.
I told the copy command to “skip” them.
Next, which was not obvious to me, but in between the reading, I found the files also needed to be copied to the NSP unicode kernel directory – “C:usrsapNSPSYSexeucNTI386”. So in a similar fashion to the “exe” directory, I renamed it to “NTI386 old” and recreated a new “NTI386. Then copied all my new files in “”C:usrsapNSPDVEBMGS00exe” to “C:usrsapNSPSYSexeucNTI386”.
I started the Windows Services I stopped, and started the NSP in the MMC.
After logging in, to my plesant surprise, I found the immediate runtime error, I was getting, had disappeared, and I was presented with the NSP’s splash screen.
I navigated to check the Kernel version
There we have it, at version 69!
Continue to my next blog…