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

Similar Messages

Install Kernel Patch and Support Package

Hi Gurus.
How can I update the kernel patch and support package in solution manager?
What patchs i have to download In the service.sap.com ?
best Regards
luis

Hi Luis,
Yopu must already have checked this info at Inst Guides..
else...The Post installation steps in the installation guide contain the procedure for application of latest support packs procedure.
https://websmp204.sap-ag.de/instguides
The following SAP notes can also be referred : 212876
Information of how to download a kernel can be obtained from 19466.
Details of Patches and their release schedules can be obtained as always at
https://websmp104.sap-ag.de/ocs-schedules
Hopefully it Helps in your quest.
Br,
Sri

Solaris 10 X86 kernel patch 118844-30 ... probably bad

I installed the patch on some Dells. Seemed to run fine.
Actually, I installed 121127-01, 113000-07, and 118344-06
first since they were required by 118844-30.
Some problems have now turned up.
1. When you power cycle one of the patched machines they
refuse to boot with
Warning - The following files in / differ from the boot archive:
/boot/solaris/bootenv.rc
to continue booting .. #svc clear system/boot-archive
and then demand the root password.
2. Randomly, when you do a reboot, a patched machine will claim
that the hardware has changed and demand that you run
kdmconfig. Simply going in and out of kdmconfig, without
changes, does the job. Weird.
3. I went to patch the next machine and after the patch
install and reboot, it was a total brick, with the error
File not executable
Panic : No entry point in kernel/unix
Press any key to reboot
And, naturally, this patch cannot be backed out. For yucks
I tried the equivalent patches on a sparc. No problems. So
I think Sun effed up the GRUB stuff in the kernel patch

Ok ... I noticed that deep down in the README for the patch
they say to do a "reboot -r". Cute. We'll try that.
That seemed to go ok, but when I tried a power cycle, it
wouldn't boot, claiming
SMF database integrity check of /etc/svc/repository.db
failed making me run
/lib/svc/bin/restore_repository
which turned out to be a struggle.
My advice - stay FAR AWAY from this patch. At minumum,
it makes the power up boot process VERY delicate. Wait
for the -32 rev, which I predict will not be long in coming.
Thank you sun.

Static library not accessed properly after Solaris Kernel patch update !

Hi,
We are facing a sever issue in our application after our customer updated the Solaris 10 kernel patch u9 to u10.
We have two static libraries libdlib.a and libDLIB.a, with exactly same code base, but these two libraries are scattered across the code base and linked by many shared objects in our application.
However, one of the shared objects that links to "libdlib.a" library tries to access a function from "libDLIB.a". This behavior is causing a crash at a later point, since that shared object is supposed to access the function from "libdlib.a". Moreover, we found this is happening through the use of dbx.
I'm unable to understand why this problem surfaced after kernel patch update, though still the shared object works fine on Solaris 10 u9 patch.
Flow is something like this :
1. syslogrecorder.so gets loaded by one of the processes.
2. syslogrecorder.so is linked to "libdlib.a" at compile time, so it uses "libdlib.a" function DLIB_LoadLibrary and gets a handle to all the function pointers of the loaded library ( The purpose of DLIB_LoadLibrary is to load a shared library dynamically using dlopen )
3. syslogrecorder.so tries to do a "dlsym" and to do that it needs access to the library handle which we got in previous call DLIB_LoadLibrary. So syslogrecorder.so calls another function from DLIB_ProcAddress, which actually gives back the access to the loaded shared library.
Here is a catch in step 3, it is supposed to call DLIB_ProcAddress from the libdlib.a but as we observed from dbx output it does so by calling DLIB_ProcAddress from libDLIB.a and hence fails to give back the access to loaded shared library, causing crash at a later point in code.
Can someone put some light here that why this could happen ??
Thanks
Kuldeep

To clarify: You did not modify or rebuild any of your binaries, but after installing a kernel patch, the application stopped working. Most likely, something about your application depended on a accidental behavior of the runtime loader. That accidental behavior changed due to the patch, and your application failed.
For example, if there is a circular dependency among shared libraries, the loader will break the cycle at an arbitrary point to establish an initialization order. By accident, that order might work, in the sense of not causing a problem. A change to the loader could cause the cycle to be broken at a different point, and the resulting initialization order could cause a now-uninitialized object to be accessed. I'm not saying this is what is wrong, but this is an example of a dependency on accidental loader behavior.
Finding your actual problem will require tracing the sequence of operations leading up to the failure. You are more likely to find help in a Solaris linker forum. AFAIK, there are currently no Oracle forums for Solaris, and the old OpenSolaris forums have been converted to mailing lists. You can try the "tools-linking" list found on this page:
http://mail.opensolaris.org/mailman/listinfo
I also suggest you review the paper on best practices for using shared libraries written by Darryl Gove and myself:
http://www.oracle.com/technetwork/articles/servers-storage-admin/linkinglibraries-396782.html
If you have a service contract with Oracle, you can use your support channel to get more help.
Edited by: Steve_Clamage on May 18, 2012 3:21 PM

Can I take my OS on kernel patch backwards?

Hi All,
I know that this is a weird question.
Can I take my OS one (or two) kernel patch backwards?
Lets say from "Generic_120011-14" to "Generic_118833-36". ? is it possiblle?
All this mass is beacuse of a testing team at my work.
Thanks!!!!

It depends on how you got to 120011-14.
If your initial install was 118833-36 or earlier and you patched up to 120011-14, then in theory you can back out the patches.
But the initial install was higher than 118833-36. Or you live upgraded past it then you can't go back.
Even if you patched past it, it would be a difficult excercise because there are a lot of related patches that rely on the higher kernel. So you would need to backout any patches that rely on it first.

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

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.

Kernel patch 127128-11 renders my x86 system unbootable - what to do?

Just installed some patches with smpatch as usual, kernel patch 127128-11 among them. I then dropped to single user mode to finish the installation, rebooted and... nothing. I get the SunOS copyright notice, and then nothing but a flashing cursor... I waited for half an hour, but nothing happened, no disk activity, keyboard not responding, nothing.
I had to reset the stupid machine...
This happened on old(ish) HP Vectra SFF.
What I can do now? What are my options? (And please DON'T say: "reinstall everything"!!!)
I have used Linux for 7-8 years, but Solaris is pretty new for me, this installation is some 2 months old (Sun Solaris 10 - 8/07 - x86)

I remember I ever tried a tool that you need to run in order to put your computer on the list.
Well it suddenly crashed and I didn't try it again.The certification tool: http://www.sun.com/bigadmin/hcl/hcts/
At Sun they know very well which systems I'm running Solaris on.
This data is sent when you register to apply for updates.They don't use your registration info to list a system as certified to run Solaris10. See link above.
I have to admit I never added any patches by going into single user mode.I install in single user per instructions in patch README. I have rarely had issues installing patches this way.
Reading back this thread I see that this patch was part of the Solaris 10 5/08 version
and since I recently upgraded to this version and everything is working fine,
I don't think there is an issue. Neither do I think that there is an issue with 127128-11 patch, which is why I mentioned that OPs machine was not on HCL. It's an issue with OPs hardware, not the new kernel. So, what is that 'fix' disabling so that Solaris will run on unsupported hardware?
I haven't tried OpenSolaris yet. What do you think of it so far?

Last kernel patch for Solaris 10 x86 screwed up my kernel

Hi,
The last kernel patch for Solaris 10 x86 (sorry I can�t remember the patch id, but the revision is 30), available from Sun Update Manager screwed up my system.
The system is still booting but in maintenance mode: smf can't start because of repository corrupted. Given instructions to restore the repository does not work because / filesystem is mounted read-only...
As I am not a solaris expert, I will reinstall it from CD. I hope I won't loose the filesystem.
I was used to blindly trust Sun solaris patches, that was a mistake.
Laurent.

i dont know why but still i do get default log in into the single mode
after startup
Requesting maintenance mode
(See /lib/svc/share/README for aditional information. )
Root password for system maintenance (control-d to bypass):i did removed the patch installed before so now
SunOS jorgito 5.10 Generic_118844-26 i86pc i386 i86pcand finaly i do have milestone like this
bash-3.00$ svcprop restarter | grep mile
options/milestone astring svc:/milestone/multi-user:default
dont know what to do else, also tried to synchronize boot-archive from solaris failsafe ...

Kernel patch updation for solaris 10 x86

I have Solaris 10 06/06 installed on x86 machine which is using svm and clustered with another node. The kernel revision is 118855-19 from the uname -a output. I am looking for the kernel patch updation and I heard 118855-36 is the latest one. Shall I go ahead with this patch and what r the dependency patches for this.
If anyone done this please guide me..

Patch 118855-36 is the latest kernel patch for Solaris 10 on x86 and its dependencies are:
113000-01 117435-02 118344-14 119043-09 119255-14 121264-01 122035-01 123840-01 (or greater)
Whether you should go ahead and install the patch is up to you, if possible try it out on a test box first. For better advice on this matter, I would suggest posting in the Solaris 10 forum as this forum is for the Sun Update Connection, Patch Manager & PatchPro toolsets.

Kernel patch update for solaris 10 x86

I have Solaris 10 06/06 installed on x86 machine which is using svm and clustered with another node. The kernel revision is 118855-19 from the uname -a output. I am looking for the kernel patch updation and I heard 118855-36 is the latest one. Shall I go ahead with this patch and what r the dependency patches for this.
If anyone done this please suggest and guide me..

For Solaris 10 x86 the latest offered with smpatch is 125101-07 and yes it may be recommended to patch. Then again you said clustered with sun cluster? You may want to check the documentation and if your machines aren't facing the internet you may wait for 7/07 to hit the street and do an upgrade.

How to do Kernel Patching in Solaris 10?

How to do Kernel Patching in Solaris 10?

Hi,
In single user
# init s
# patchadd <kernel_patch>
or the best is to install the last Solaris update patch bundle
See http://sunsolve.sun.com/show.do?target=patches/patch-access
Marco.

Solaris 10 U4 and kernel patches

When I install a fresh U4 machine, I then (as I always do) apply the recommended patch cluster. U4 has kernel patched to 120011-14. In the patch cluster, there are kernel patches 118833-36 and also 120011-14. When I run the patch cluster, it installs 118833-36! Isn't this older than the kernel on there? Shouldn't both 118833-36 and 120011-14 BOTH not install as the kernel is already at level 120011-14. The cluster gets to 118833-36 installs that and then of course every patch after that one fails as the machine is waiting for a reboot.

KJP 137138-09 should be ok with cpquary3 driver 1.9.1. KJP 137138 introduced new feature which does not allow misaligned pointer mutexes to work and panics the system. with revision 07 SUN introduced a new environment variable as a for applications which cannot be ported easily "6729759 need to accommodate non-8-byte-aligned mutexes".
This is documented in alert 244606 "The resolution for OpenSolaris releases sets _THREAD_LOCKS_MISALIGNED to 0. This is to ensure that any faulty applications fail and are identified. To allow such applications to continue to work on OpenSolaris releases based upon snv_96 or later, the environment variable _THREAD_LOCKS_MISALIGNED must be set to 1." For this to work you need to have revision 09 of this KJP applied.
Can you post the stack trace so i can have a look at it. I guess you have another application which uses unaligned mutexes.
A pkginfo of the cpquary3 package would also be useful.
-Marco

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

Kernel Patch Install Procedure.

Similar Messages

Maybe you are looking for