Path to download Kernel patch

Hi,
Please tell me the path to download kernel releae 700 patch number 0133
Also tell me the process of applying the patch

Hi Balaji,
The version of the kernal you have to download is 'SAPEXEDB_133-20001361.SAR'
It was released on 23.10.2007.
We are also on the same configuration as you are,
but is this a urgent or mandatory thing that you want to update the kernal.Before doing this take a back up of sys/exe folder back up and then proceed.
Just uncar the sar file in any temp directory other then sys/exe,
you will get a exe file.
first stop your sap system,then just copy paste the exe file you have got in the sys/exe/uc/ntadmin directory,
make sure you have backed up the exe directory then start your sap system.
Reward points if helpfull.
Regards,
Vamshi

Similar Messages

Path to download kernel path 95

Please let me know the path to download kernel path 95

Dear Balaji,
given the patch level, I assume that you are talking about an 7.00 kernel. This should be available for download from http://service.sap.com/patches, Select 'Entry by Application Group' on the left hand side, then Select
SAP NetWeaver
    SAP NETWEAVER
       SAP NETWEAVER 2004S
           Entry by Component
              Application Server ABAP
and from there the correct version (32-BIT or 64-BIT) and the correct platform.
The file that you are looking for is in the database independant branch and called dw_95*.SAR
Best Regards,
Tim
Message was edited by:
        Tim Buchholz

Kernel Patch 108528-26 bad?

On machine: SunOS boedev 5.8 Generic_108528-14 sun4u sparc SUNW,UltraAX-MP
As part of the J2SE recommended patches, I attempted install of the downloaded 108528-26 kernel patch and received:
<snip>
Installation of <SUNWcar> was successful.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
pkgadd: ERROR: source path </export/home/src/J2SE_Solaris_8_Recommended/108528-2
6/SUNWcarx.u/reloc/platform/SUNW,Sun-Blade-100/kernel/misc/sparcv9/platmod> is c
orrupt
file cksum <38281> expected <38278> actual
pkgadd: ERROR: source path </export/home/src/J2SE_Solaris_8_Recommended/108528-2
6/SUNWcarx.u/reloc/platform/SUNW,Sun-Blade-1000/kernel/misc/sparcv9/platmod> is
corrupt
file size <4832> expected <4830> actual
file cksum <34048> expected <33987> actual
Installation of <SUNWcarx> partially failed.
------------------------------>
Then, without rebooting, I downloaded the separate patch 108528-26 and attempted to load with patchadd...basically the same result:
Installation of <SUNWcar> was successful.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
WARNING: /kernel/sys/sparcv9/rpcmod <no longer a regular file>
pkgadd: ERROR: source path </export/home/src/patches/108528-26/SUNWcarx.u/reloc/
platform/SUNW,Sun-Blade-100/kernel/misc/sparcv9/platmod> is corrupt
file cksum <38281> expected <38278> actual
pkgadd: ERROR: source path </export/home/src/patches/108528-26/SUNWcarx.u/reloc/
platform/SUNW,Sun-Blade-1000/kernel/misc/sparcv9/platmod> is corrupt
file size <4832> expected <4830> actual
file cksum <34048> expected <33987> actual
Installation of <SUNWcarx> partially failed.
I think this patch is "bad" as it has been released... but I have as yet seen no acknowledgement of that. Anyone else tried this patch?!
The machine reboots and runs, but in what state is it left with the new patches running on the old kernel?
I have posted this to other related groups. Thanks. jj.

JJ,
I downloaded and tried to install this patch this weekend. I am having the same problems. Anyone know where I can get patch 108528-21? I need this for a piece of software I am installing.
Thanks,
Sherryl

Please help me in Downloading KERNEL

HI,
can anybody help me in downloading the KERNEL for NETWEAVER 2004S SR1.
Please provide me the link to download.
CHEERS
BALU
(09986829664)

Hi Balu,
Did you follow the complete path to your kernel? There are many times when navigating where it says no information available yet there is still a link.
For example, for a 7.0 (2004s) 64-bit AIX/Oracle kernel I went to http://service.sap.com/swdc -> Download -> Entry by Application Group -> Support Packages and Patches -> Additional Components" -> SAP Kernel -> SAP KERNEL 64-BIT -> SAP KERNEL 7.00 64-BIT -> AIX 64-bit -> ORACLE. The "No additional information available" is just an info page and means there is nothing yet to download...more information is needed.
Best Regards,
Matt

J2EE Recommended Patch Cluster fails with Kernel patch 108528-26

As part of the J2EE recommended cluster, I attempted installing patch 108528-26 to my Solaris 8 box (all of which was downloaded from sun.com):
SunOS boedev 5.8 Generic_108528-14 sun4u sparc SUNW,UltraAX-MP
It failed and rolled back as part of the cluster with the following error log:
Package not patched:
PKG=FJSVhea
Original package not installed.
Package not patched:
PKG=FJSVmdb
Original package not installed.
Package not patched:
PKG=FJSVmdbx
Original package not installed.
Package not patched:
PKG=FJSVvplr.us
Original package not installed.
Package not patched:
PKG=FJSVvplu.us
Original package not installed.
Package not patched:
PKG=SUNWcar.d
Original package not installed.
Package not patched:
PKG=SUNWcar.m
Original package not installed.
Package not patched:
PKG=SUNWcar.us
Original package not installed.
Package not patched:
PKG=SUNWcarx.us
Original package not installed.
Package not patched:
PKG=SUNWcpc.us
Original package not installed.
Package not patched:
PKG=SUNWcpcx.us
Original package not installed.
Package not patched:
PKG=SUNWcpr.m
Original package not installed.
Package not patched:
PKG=SUNWcpr.us
Original package not installed.
Package not patched:
PKG=SUNWcprx.us
Original package not installed.
Package not patched:
PKG=SUNWdrr.u
Original package not installed.
Package not patched:
PKG=SUNWdrr.us
Original package not installed.
Package not patched:
PKG=SUNWdrrx.u
Original package not installed.
Package not patched:
PKG=SUNWdrrx.us
Original package not installed.
Package not patched:
PKG=SUNWefcx.u
Original package not installed.
Package not patched:
PKG=SUNWidn.u
Original package not installed.
Package not patched:
PKG=SUNWidnx.u
Original package not installed.
Package not patched:
PKG=SUNWkvm.us
Original package not installed.
Package not patched:
PKG=SUNWkvmx.us
Original package not installed.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Installation of <SUNWarc> was successful.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Installation of <SUNWarcx> was successful.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Installation of <SUNWcar> was successful.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
pkgadd: ERROR: source path </export/home/src/patches/108528-26/SUNWcarx.u/reloc/platform/SUNW,Sun-Blade-100/kernel/misc/sparcv9/platmod> is corrupt
file cksum <38281> expected <38278> actual
pkgadd: ERROR: source path </export/home/src/patches/108528-26/SUNWcarx.u/reloc/platform/SUNW,Sun-Blade-1000/kernel/misc/sparcv9/platmod> is corrupt
file size <4832> expected <4830> actual
file cksum <34048> expected <33987> actual
Installation of <SUNWcarx> partially failed.
Without rebooting, I then downloaded the patch from sunsolve as a separate patch and attempted to load it with patchadd, to no avail but with additional errors (WARNING:) along with the original ones:
Package not patched:
PKG=FJSVhea
Original package not installed.
Package not patched:
PKG=FJSVmdb
Original package not installed.
Package not patched:
PKG=FJSVmdbx
Original package not installed.
Package not patched:
PKG=FJSVvplr.us
Original package not installed.
Package not patched:
PKG=FJSVvplu.us
Original package not installed.
Package not patched:
PKG=SUNWcar.d
Original package not installed.
Package not patched:
PKG=SUNWcar.m
Original package not installed.
Package not patched:
PKG=SUNWcar.us
Original package not installed.
Package not patched:
PKG=SUNWcarx.us
Original package not installed.
Package not patched:
PKG=SUNWcpc.us
Original package not installed.
Package not patched:
PKG=SUNWcpcx.us
Original package not installed.
Package not patched:
PKG=SUNWcpr.m
Original package not installed.
Package not patched:
PKG=SUNWcpr.us
Original package not installed.
Package not patched:
PKG=SUNWcprx.us
Original package not installed.
Package not patched:
PKG=SUNWdrr.u
Original package not installed.
Package not patched:
PKG=SUNWdrr.us
Original package not installed.
Package not patched:
PKG=SUNWdrrx.u
Original package not installed.
Package not patched:
PKG=SUNWdrrx.us
Original package not installed.
Package not patched:
PKG=SUNWefcx.u
Original package not installed.
Package not patched:
PKG=SUNWidn.u
Original package not installed.
Package not patched:
PKG=SUNWidnx.u
Original package not installed.
Package not patched:
PKG=SUNWkvm.us
Original package not installed.
Package not patched:
PKG=SUNWkvmx.us
Original package not installed.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
WARNING: /kernel/sys/sparcv9/rpcmod <no longer a regular file>
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Installation of <SUNWarc> was successful.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Installation of <SUNWarcx> was successful.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Installation of <SUNWcar> was successful.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
WARNING: /kernel/sys/sparcv9/rpcmod <no longer a regular file>
pkgadd: ERROR: source path </export/home/src/patches/108528-26/SUNWcarx.u/reloc/platform/SUNW,Sun-Blade-100/kernel/misc/sparcv9/platmod> is corrupt
file cksum <38281> expected <38278> actual
pkgadd: ERROR: source path </export/home/src/patches/108528-26/SUNWcarx.u/reloc/platform/SUNW,Sun-Blade-1000/kernel/misc/sparcv9/platmod> is corrupt
file size <4832> expected <4830> actual
file cksum <34048> expected <33987> actual
Installation of <SUNWcarx> partially failed.
Now I have a box with many J2EE patches but without the proper kernel!!! Halp! jj.

did you try and removed the IDR? I.e: patchrm IDR138540-01 ?
.7/M.

Pchdtv hd-3000 kernel patches

I just purchased an HD-3000 HDTV card from http://www.pchdtv.com. Their instructions are for Fedora Core 2. Since I can't stand Fedora, and I have Arch installed, I was wondering if anyone knew how to install the kernel driver for this card in Arch. On their downloads page, there are kernel patches, but I've never installed a kernel patch before. The patches appear to be for kernel 2.6.3 and 2.6.6. I know that my kernel is 2.6.9. Would I have to go back some kernels in order to use the patch? How does one go about using a kernel patch?
Thanks for any assistance on this topic.

http://www.thegeorges.us/mythtv/
there's a patch on there.

Solaris 10 kernel Patch 127127-11

we need to apply solaris 10 kernel Patch 127127-11 in our prod server as a prerequisite for oracle10g patch set 10.2.0.4 installation
but i found a Doc 242366 (May Cause a system Panic from ip_wput_ioctl()).It is mentioned in doc that Binary relief is available through normal
support channels.Is that Binary complete fix of this problem?If yes, then i need that binary please give me the link where i can download the binary,
If not, then what is the solution of this problem.?
Thanks

These kinds of binary hotfixes/IDR's are only available through sun support to contract customers.
If your concerned, I suggest you raise a support case.
That being said, 127127-11 is kinda old. So I would be surprised if the bug hadnt been fixed by now.
Its been replaced by either 137111 or 137137.
Ive upgraded at least a dozen systems past that level and never seen a problem.
So it can't be too common..

Solaris 10 kernel patch upgrade

Hi all,
i am in a process of upgrading the kernel patch of a solaris 10 x64 machine, the present kernel patch is "5.10 Generic_144489-06 i86pc i386 i86pc" the updated kernel patch that i am going to upgrade to is patch "144501-19".
could you please let me know if there is any special handling to undergo the upgrade or it is only sufficient to follow the 144501-19 README file?
i know that i should put the system on the single user mode level and i have to have a valid OS backup before doing the patchadd, but if i am missing anything else please let me know
thanks

Hello,
if you are having system filesystems (/ /usr /var ...) on software RAID1 devices, best practise is to split mirrors and have most recent actual copy of the system (or create current ZFS snapshot if using ZFS on root),patch it in single user mode or use Live Upgrade functionality and create alternate boot environment and patch the ABE on running system (you can find various info in Oracle Docs or get inspired by various blogs:http://nilesh-joshi.blogspot.com/2011/10/oracle-solaris-patching-using-live.html). I always patch kernel and other system components using PCA patching utility - have a look on project homepage http://www.par.univie.ac.at/solaris/pca/ it's really advanced and helpful tool. It can save you lot of time when solving dependecies and also downloading the patches.
Good luck

Steps for Kernel Patch Updation on Solaris 10 X4100 with 2disks mirrored

Hi all,
I have Solaris 10 10/06 (118855-19) installed on one of the X4100 server. This is the time for me to update the latest kernel patch (118855-36). We have two disks mirrored. My questions are,
1) Do i need to detach any of the disk from the mirror before doing any patching.
2) Is it possible to install the patches without detaching any disks from the mirror. (i.e. installeing patch on mirrored root filesystem)
3) how to boot from the second disk in case the patch installation creates problem while booting up.
Any suggestions or steps which you have already implemented for the above scenario.

This isn't really a question for this forum, you may be better to look at some of the sys-admin forums for a complete answer.
You should not need to break the mirror in order to apply the kernel patch, however doing so would allow for quicker recovery of the system should something go wrong during patching.
I would strongly advise that you read the special install instructions for the kernel patch prior to installing it.
http://sunsolve.sun.com/search/document.do?assetkey=1-21-118855-36-1
You may also wish to use a patch cluster rather than smpatch/updatemanager, these can be downloaded from SunSolve:
http://sunsolve.sun.com/private-cgi/show.pl?target=patchpage

Kernel Patching with zones

I have a T2000 installed with the Solaris 10 1/06 release with several zones created on it. 4 zones are "sparse" root, and one (zone-5) is a "whole root" zone.
In order to apply and certify (internally) the latest sendmail patch, Solaris 10 needs a later kernel patch than I had installed (this is a subject for another discussion...). So I downloaded the latest patch cluster (4/6 Recommended cluster) to apply it.
I shut down the non-global zones, and took the machine to single user mode, and installed the cluster. It seemed to go in fine, except for the following error:
Zone zone-5
Rejected patches:
122856-01
Patches that passed the dependency check:
None.
Fatal failure occurred - impossible to install any patches.
zone-5: For patch 122856-01, required patch 118822-30 does not exist.
Fatal failure occurred - impossible to install any patches.Now, 118822-30 is a kernel patch series that is prerequisite for the latest kernel patch (118833-03). Zone-5 is my only whole-root zone. I then looked at the patch cluster log, and discovered that a handful of patches (including 118822-30) had also failed:
titan15n> grep failed /var/sadm/install_data/Solaris_10_Recommended_Patch_Cluster_log
Pkgadd failed. See /var/tmp/119254-19.log.6615 for details
Pkgadd failed. See /var/tmp/118712-09.log.9307 for details
Pkgadd failed. See /var/tmp/119578-18.log.15160 for details
Pkgadd failed. See /var/tmp/121308-03.log.18339 for details
Pkgadd failed. See /var/tmp/119689-07.log.22068 for details
Pkgadd failed. See /var/tmp/118822-30.log.9404 for details
Pkgadd failed. See /var/tmp/119059-11.log.29911 for details
Pkgadd failed. See /var/tmp/119596-03.log.4724 for details
Pkgadd failed. See /var/tmp/119985-02.log.8349 for details
Pkgadd failed. See /var/tmp/122032-02.log.13334 for details
Pkgadd failed. See /var/tmp/118918-14.log.27743 for detailsLooking at any of these logs (in the non-global zone-5's /var/tmp directory shows failures like the following snippet:
pkgadd: ERROR: unable to create unique temporary file </usr/platform/sun4us/include/sys/cheetahregs.h6HaG8w>: (30) Read-only file sy
stem
pkgadd: ERROR: unable to create unique temporary file </usr/platform/sun4us/include/sys/clock.h7HaG8w>: (30) Read-only file system
pkgadd: ERROR: unable to create unique temporary file </usr/platform/sun4us/include/sys/dvma.h8HaG8w>: (30) Read-only file systemQuestion(s):
Why would there be read-only file systems where tmp files are getting written? Possibly a timing issue?
Is there a "best practice" on applying patch clusters, and specifically, the kernel patch? Did I make a mistake in taking the zones down first? It seems like the zones were being booted up as the patches were getting applied, but I may be misinterpreting the output.
Even though the patches failed to apply to zone-5, the uname -a output in the zone show the latest kernel patch, but does NOT show 118822-30 (118822-25 is what showrev -p in the non-global zone-5 shows -- which is the level I was at before attempting to patch).
Any solutions?
Thanks.

The kernel config and patch are irrelevant - I have tried to compile the stock arch kernel just to make sure that it WASN'T the patch - I simple copied the folder from ABS, did makepkg and installed - no lucky. The problem seems to be that all of the kernels I compile end up with the folder in /lib/modules having -dirty on the end of them. How do I stop this '-dirty'?
I notice in the build I get this message -
==> Building the kernel
fatal: cannot describe '604d205b49b9a478cbda542c65bacb9e1fa4c840'
CHK include/linux/version.h

SP 's and Kernel patches

Hi all,
I have a few questions and want clear my basics.
Is Kernel upgrade the same as applying a kernel patch? For any SAP system release, there's
just one kernel version right? We just keep applying new patch versions to update it. Is this
correct? Please throw some light.
secondly, in SPAM, what is the difference between new and imported packages? When trying
to apply latest support packages, what steps should you follow? And what are support package
stacks? I know they are a collection od packages but how to find out which one I will need
depending on the current package status of my system?
Thanks in advance
Cyrus

hi Cyrus,
> secondly, in SPAM, what is the difference between new
> and imported packages? When trying
> to apply latest support packages, what steps should
> you follow?
SPAM - Support Package Manager is used to put ABAP patches in your system. Imported packages mean the packages that are already imported in your system. say your WAS is on SP9 - this means you will find SP1..SP9 in imported packages. this will be useful if you are patching it up in stages. you will find which are already imported and hence put the rest. Sometimes higher patches needs to have some prerequisites. you may find if these prerequisites are satisfied.
New packages are already loaded but yet to be imported. You will find the traffic light - Yellow. for imported packs you will find it green.
if you want to apply latest support packs, first load them into your ABAP system after downloading them from service market place. you may do it using the SUPPORT PACKAGE --> Load FROM FORNT END. then upload the car files and Display/Define Queue. then Import Queue. after queue is imported, Confirm
Presto! you have finished upgrading.
>And what are support package
> stacks? I know they are a collection od packages but
> how to find out which one I will need
> depending on the current package status of my
> system?
first Find which stack your system is running. this is source stack. then find give the target (say SP14) in service market place. this will give all necessary stacks from your source to target. download them.
hope i managed to throw some light!
Regards
ak
Message was edited by: Arun Kumar Ravi

Problem of SIGPOLL(SI_NOINFO) in latest Solaris9 kernel patch

Hi,
We are facing a rather strange problem with the latest kernel patch on Solaris 9. (Generic_112233-08). We had not faced this problem with any of the other kernel patches of Solaris 9.
Our application has a main thread and a single child thread (pthread). The main thread schedules aio_writes() on the raw disk interface and lets the child thread block on sigwaitinfo() to listen to the signal completion notification. This is communicated to it via the SI_ASYNCIO code of SIGPOLL. The child thread then informs the main thread by writing to a bi-directional pipe. Since the main thread has registered for read interest on the bi-directional pipe (via /dev/poll) it is informed of the completion of the aio_write() without having to block itself. Under normal circumstances, the child thread receives SIGPOLL with SI_ASYNCIO code.
This application has been running fine on all the previous builds of Solaris (Generic, Generic_112233-04, Generic_112233-06) on sparc platform expect with the latest kernel patch. The child thread now keeps receiving SIGPOLL with SI_NOINFO code. There has been no change in our application and we are perplexed to the reason of this behaviour. Since it is SI_NOINFO there is not much debugging information we can get.
We have been able to replicate this behaviour using a small stand-alone program. We are attaching it at the end of the email. We tried this program on a couple of different Sparc systems and were able to reproduce this behaviour on one of them but not on the other.
Has anybody faced problems with regard to SIGPOLL in the latest kernel patch of Solaris 9 for sparc systems ?
Thanks
Regards
Raj Pagaku
proxy-24:~ >uname -a
SunOS proxy-24 5.9 Generic_112233-08 sun4u sparc SUNW,Ultra-5_10
proxy-24:~ >gcc -v
Reading specs from /usr/local/lib/gcc-lib/sparc-sun-solaris2.9/3.2/specs
Configured with: ../configure with-as=/usr/ccs/bin/as with-ld=/usr/ccs/bin/ld --disable-nls
Thread model: posix
gcc version 3.2
Compiled this program using the following command : gcc -g kernel_bug.c -lrt -lpthread
#include <stdio.h>
#include <aio.h>
#include <errno.h>
#include <fcntl.h>
#include <pthread.h>
#include <signal.h>
#include <stdlib.h>
#include <string.h>
#include <unistd.h>
#include <sys/resource.h>
#include <sys/stat.h>
#include <sys/types.h>
#define min(x,y) (((x)<=(y))?(x):(y))
#define DISPLAY_COUNT 10000
typedef struct DiskInfoCallOut {
void (*func_ptr)(void *);
void *data_ptr;
} DiskInfoCallOut;
typedef struct DiskInfo {
struct aiocb di_aiocb;
DiskInfoCallOut di_callout;
off_t di_currOffset;
int di_scheduled;
} DiskInfo;
typedef struct Disk {
int fd;
char *buffer;
int bufferLen;
} Disk;
static sigset_t aioSignalSet;
int aioSigFD[2];
int glob_scheduled = 1;
int glob_respond = 1;
Disk disk;
static void LaunchDiskOperation(DiskInfo *di);
char BUFDATA[4096] = {'a'};
char rawDeviceName[256] = "/dev/rdsk/";
static void
InitializeDisk()
int fd;
if ((fd = open(rawDeviceName, O_RDWR, 0)) == -1) {
fprintf(stderr, "Unable to open raw device \n");
exit(-1);
disk.fd = fd;
disk.buffer = BUFDATA;
disk.bufferLen = sizeof(BUFDATA);
static void
AIOSignalHandler(int sigNum, siginfo_t* si, void* context)
fprintf(stderr, "WARN: got signal %d in AIOSignalHandler!\n", sigNum);
/* Function implementing the slave thread */
static void*
AIOSignalThread(void *arg)
struct sigaction sa;
siginfo_t info;
sigset_t ss;
int sig_num;
int retVal;
/* Initialize the signal set*/
sigemptyset(&ss);
sigaddset(&ss, SIGPOLL);
if ((retVal = pthread_sigmask(SIG_SETMASK, &ss, NULL))) {
fprintf(stderr, "pthread_sigmask failed in AIOSignalThread \n");
exit(-1);
sa.sa_handler = NULL;
sa.sa_sigaction = AIOSignalHandler;
sa.sa_mask = aioSignalSet;
sa.sa_flags = SA_SIGINFO;
if (sigaction(SIGPOLL, &sa, NULL)) {
fprintf(stderr, "sigaction in AIOSignalThread \n");
exit(-1);
/* Wait infinitely for the signals and respond to the main thread */
while (1) {
sig_num = sigwaitinfo(&aioSignalSet, &info);
if (sig_num != SIGPOLL) {
fprintf(stderr, "caught unexpected signal %d in AIOSignalThread \n",
sig_num);
exit(-1);
if (info.si_code != SI_ASYNCIO){
fprintf(stderr, "ERROR: siginfo_t had si_code != SI_ASYNCIO, si_code = %d \n", info.si_code);
continue;
/* Write the stored pointer value in the pipe so that the main thread can process it */
if (write(aioSigFD[1], &(info.si_value.sival_ptr), sizeof(info.si_value.sival_ptr)) !=
sizeof(info.si_value.sival_ptr)) {
perror("Couldn't write the whole pointer");
exit(-1);
return (NULL);
static void
Init()
pthread_attr_t aioAttr;
pthread_t aioThread;
int retVal = 0;
/* Create a bidirectional pipe */
if (pipe(aioSigFD)) {
perror("pipe failed");
exit(-1);
/* Initialize to prevent other threads from being interrupted by
SIGPOLL */
sigemptyset(&aioSignalSet);
sigaddset(&aioSignalSet, SIGPOLL);
if ((retVal = pthread_sigmask(SIG_BLOCK, &aioSignalSet, NULL))) {
fprintf(stderr, "pthread_sigmask failed in Init\n");
exit(-1);
InitializeDisk();
if ((retVal = pthread_attr_init(&aioAttr)))
fprintf(stderr, "pthread_attr_init failed \n");
if ((retVal = pthread_attr_setdetachstate(&aioAttr, PTHREAD_CREATE_DETACHED)))
fprintf(stderr, "pthread_attr_setdetachstate failed \n");
if ((retVal = pthread_attr_setscope(&aioAttr, PTHREAD_SCOPE_SYSTEM)))
fprintf(stderr, "pthread_attr_setscope failed in \n");
if ((retVal = pthread_attr_setstacksize(&aioAttr, 2*1024*1024)))
fprintf(stderr, "pthread_attr_setstacksize failed \n");
if ((retVal = pthread_create(&aioThread, &aioAttr,
AIOSignalThread, NULL)))
fprintf(stderr, "pthread_create failed \n");
static void
UpdateDiskWriteInformation(DiskInfo *di)
di->di_currOffset += disk.bufferLen;
di->di_scheduled = 0;
static void
DiskOpCompleted(void *ptr)
DiskInfo di = (DiskInfo )ptr;
if (aio_error(&di->di_aiocb))
perror("aio_error");
if (aio_return(&di->di_aiocb) < 0)
perror("aio_return ");
UpdateDiskWriteInformation(di);
glob_respond++;
static void
LaunchDiskOperation(DiskInfo *di)
int res;
di->di_callout.func_ptr = DiskOpCompleted;
di->di_callout.data_ptr = di;
memset(&di->di_aiocb, 0, sizeof(di->di_aiocb));
di->di_aiocb.aio_fildes = disk.fd;
di->di_aiocb.aio_buf = disk.buffer;
di->di_aiocb.aio_nbytes = disk.bufferLen;
di->di_aiocb.aio_offset = di->di_currOffset;
di->di_scheduled = 1;
di->di_aiocb.aio_sigevent.sigev_notify = SIGEV_SIGNAL;
di->di_aiocb.aio_sigevent.sigev_signo = SIGPOLL;
di->di_aiocb.aio_sigevent.sigev_value.sival_ptr = &di->di_callout;
res = aio_write(&di->di_aiocb);
if (res == -1) {
perror("aio op error");
static void
HandleSignalResponses()
int fd;
#define DISKINFO_CALLOUT_MAX 64
DiskInfoCallOut* callout[DISKINFO_CALLOUT_MAX];
struct stat pipeStat;
int numCompleted;
int bytesToRead;
int sz;
int i;
fd = aioSigFD[0];
while (1) {
/* Find whether there is any data in the pipe */
if(-1 == fstat(fd, &pipeStat)) {
perror("fstat");
exit(-1);
if (pipeStat.st_size < sizeof(DiskInfoCallOut *))
break;
numCompleted = min((pipeStat.st_size/sizeof(DiskInfoCallOut *)),DISKINFO_CALLOUT_MAX);
bytesToRead = numCompleted * sizeof(DiskInfoCallOut *);
if ((sz = read(fd, callout, bytesToRead)) != bytesToRead) {
perror("Error reading from pipe");
exit(-1);
for (i = 0; i < numCompleted; i++)
(*callout[i]->func_ptr)(callout[i]->data_ptr);
int main(int argc, char *argv[])
DiskInfo *di;
FILE *logPtr1 = NULL;
FILE *logPtr2 = NULL;
FILE *logPtr3 = NULL;
struct rusage ru;
struct timeval t1, t2;
long timeTaken = 0;
int writeCount = 0;
int i;
char logFileName1[1024];
char logFileName2[1024];
char logFileName3[1024];
if (argc < 2) {
fprintf(stderr, "Usage : %s <partition_name> \n", argv[0]);
exit(-1);
strcat(rawDeviceName, argv[1]);
writeCount = 1;
printf("Partition selected = %s \n", rawDeviceName);
di = calloc(writeCount, sizeof(DiskInfo));
sprintf(logFileName1, "%s.log1", argv[0]);
if ((logPtr1 = fopen(logFileName1, "w+")) == NULL) {
fprintf(stderr, "Unable to create file test_pgm \n");
exit(-1);
sprintf(logFileName2, "%s.log2", argv[0]);
if ((logPtr2 = fopen(logFileName2, "w+")) == NULL) {
fprintf(stderr, "Unable to create file test_pgm \n");
exit(-1);
sprintf(logFileName3, "%s.log3", argv[0]);
if ((logPtr3 = fopen(logFileName3, "w+")) == NULL) {
fprintf(stderr, "Unable to create file test_pgm \n");
exit(-1);
Init();
for (i = 0; i < writeCount; i++) {
di.di_currOffset = (1 << 18) * (i + 1);
di[i].di_scheduled = 0;
gettimeofday(&t1, NULL);
while (1) {
int curScheduled = 0;
/* Schedule the disk operations */
for (i = 0; i < writeCount; i++) {
if (di[i].di_scheduled == 0) {
LaunchDiskOperation(&di[i]);
glob_scheduled++;
curScheduled++;
/* Handle the responses */
HandleSignalResponses();
if ((curScheduled) && (glob_respond % DISPLAY_COUNT == 0)) {
gettimeofday(&t2, NULL);
timeTaken = ((t2.tv_sec * 1000000 + t2.tv_usec) -
(t1.tv_sec * 1000000 + t1.tv_usec))/1000;
printf("Scheduled = %d, Responded = %d, Time Taken = %ld ms \n",
glob_scheduled, glob_respond, timeTaken);
fprintf(logPtr1, "Scheduled = %d, Responded = %d, Time Taken = %ld ms \n",
glob_scheduled, glob_respond, timeTaken);
fprintf(stderr,"wrote to logPtr1 ..\n");
fprintf(logPtr2, "Scheduled = %d, Responded = %d, Time Taken = %ld ms \n",
glob_scheduled, glob_respond, timeTaken);
fprintf(stderr,"wrote to logPtr2 ..\n");
fprintf(logPtr3, "Scheduled = %d, Responded = %d, Time Taken = %ld ms \n",
glob_scheduled, glob_respond, timeTaken);
fprintf(stderr,"wrote to logPtr3 ..\n");
t1 = t2;

Hi @cooldog ,
I hit this same LVM2 snapshot kernel oops on several Oracle Linux 6.5 servers running UEK R3 kernel version 3.8.13-16.3.1. I have Linux Premier Support so I opened a Service Request. Oracle Support got back to me with the following notes.
Hello Matt,
Bug 17487738 : EXT4: STRESS TESTING WITH SUSPEND/RESUME FS ACCESS CAUSES FS ERRORS This bug is fixed in kernel version: 3.8.13-18. This kernel will be available quite soon for download.
You may upgrade the kernel once its available. ~Siju
Update
Dear Matt, Latest available UEK3 kernel version 'kernel-uek-3.8.13-26.el6uek.x86_64' incorporates the required bugfix. [root@server1 tmp]# rpm -q --changelog -p kernel-uek-3.8.13-26.el6uek.x86_64.rpm | grep -i 17487738
warning: kernel-uek-3.8.13-26.el6uek.x86_64.rpm: Header V3 RSA/SHA256 signature: NOKEY, key ID ec551f03
- fs: protect write with sb_start/end_write in generic_file_write_iter (Guangyu Sun) [Orabug: 17487738] <<<<<<======================================== You can download the UEK3 kernel from ULN or from public-yum repo.
http://public-yum.oracle.com/repo/OracleLinux/OL6/UEKR3/latest/x86_64/getPackage/kernel-uek-firmware-3.8.13-26.el6uek.noarch.rpm
http://public-yum.oracle.com/repo/OracleLinux/OL6/UEKR3/latest/x86_64/getPackage/kernel-uek-3.8.13-26.el6uek.x86_64.rpm Hope this helps! ~Siju
Subscribe to the Oracle Linux el-errata mailing list .
The latest kernel-uek-3.8.13-26.el6uek.x86_64 version fixed the problem.
- Matt

Kernel Patch Install Procedure.

Dear All,
we are getting the error for "STORAGE_PARAMETERS_WRONG_SET"
while executing the program.
But SAP give the solution for this issuse(Latest Kernel Patch Install)
I have dowlnload the below kernel patch level in service market place.
SAPEXE_175-20000182.SAR Kernel Part I (for Basis 640/620/610) Q2/2008
SAPEXEDB_175-20000185.SAR Kernel Part II (for Basis 640/620/610) Q2/200
And the I have install (Over write)the our IDES above download the kernel patch level but not chnage the kernel patch value(System status check). But working well.
Any other procedure your advise Kindly help me.
Thank you.
Best Regards,
M.Thiru

Dear All,
we are getting the error for "STORAGE_PARAMETERS_WRONG_SET"
while executing the program.
But SAP give the solution for this issuse(Latest Kernel Patch Install)
I have dowlnload the below kernel patch level in service market place.
SAPEXE_175-20000182.SAR Kernel Part I (for Basis 640/620/610) Q2/2008
SAPEXEDB_175-20000185.SAR Kernel Part II (for Basis 640/620/610) Q2/200
And the I have install (Over write)the our IDES above download the kernel patch level but not chnage the kernel patch value(System status check). But working well.
Any other procedure your advise Kindly help me.
Thank you.
Best Regards,
M.Thiru

Sequence of Applying Kernel Patches

Hi All,
We have ECC 5.0 (Central Instance) OS:HP UNIX and four Dialog Instances on Windows Platform.
For Applying the latest kernel patches what should be the sequence, first dialog instances or Central Instance?
For this landscape is it required that while applying kernel patch Database should be in shutdown mode?
Regards,
Prashant.

Dear,
>First we have to apply Support pack in the Dialog instance
Its not first dialog instance.
Please follow below steps.
1. shutdown all dialog instances.
2. take backup of current kernel directory
3. stop central instance
4. switch the kernel files from new kernel
5. start the central instance.If its successfully up with new patch level then
6. One by one start the dialog instance.
Note: If the dialog instances sharing the path of Central instance Kernel directory then no need to do anything on dialog instances. Sapcpe program will copy new kernel to dialog instance local kernel directory automatically while restarting the dialog instances.
If dialog instances not sharing the path of CI then repeat the same procedure as of CI for DI's.
Edited by: Imran Mulani on Sep 11, 2008 9:29 AM

Solaris 9 kernel patch

Hello everyone,
I'm new to Solaris, so excuse me if my questions seems stupid.
I have e solaris 9 SunOS sirius 5.9 Generic_118558-11 sun4u sparc SUNW,Sun-Fire-V890and I want to increase the kernel patch level to the last one.
Could you give me some hints where I can find and download the latest patch and the steps to install it.
Thanks for your time.

[http://sunsolve.sun.com/search/document.do?assetkey=1-21-122300-31-1]
Instructions are in the readme file for the patch.

Path to download Kernel patch

Similar Messages

Maybe you are looking for