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.

Similar Messages

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

Solaris kernel patch levels

I have engineers asking for a particular kernel patch level to be installed on machines.
Is there anywhere that lists the kernel patch level on releases and hardware updates for Solaris 8-10?
Thanks,
Duane

Please start with Sunsolve (http://sunsolve.sun.com) and Sun documentation (http://docs.sun.com) web sites.

Applied Kernel Patch to Solaris 10 on v40z, no longer auto boots

I recently updated the patches on a v40z machine including a kernel patch. After rebooting, the machine would no longer automatically boot to Solaris. Instead it would just wait for user input at the Grub bootloader screen. Anyone experienced this or have a solution?
I believe the patch in question is 118855-19
# bootadm list-menu
The location for the active GRUB menu is: /boot/grub/menu.lst
default 0
timeout 10
0 Solaris 10 6/06 s10x_u2wos_09a X86
1 Solaris failsafe

SOLVED:
Disabled ECC in the bios (though Windows and Gentoo Linux show now trouble whatsoever with my ECC memory, solaris doesn't like it)

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 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

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

Core dump on Solaris 8 Patch-15

I have compiled my code on Solaris 8 machine with the Kernal Custer Paths 12 and is working properly on the same machine. IF I move to a similar Solaris 8 machine with Patch 15 it core dumps. Do I have to recompile on Patch 15 environment? Or is it some other problem. The core happens when the executable is using C libraries (libc.so.1)

The program probably dumped core with seg fault? The
libc might well have changed with a kernel patch. I
would recommend that you recompile. If the failure
persists, I would post your question on the Solaris
forum as the lib with "little c" is maintained in the
OS and not in the Compiler Collection.

Solaris 8 patches added to Solaris 9 patch cluster and vice versa

Has anyone noticed this? On the Solaris 8 and 9 patch cluster readmes, it shows sol 9 patches have been added to the sol 8 cluster and sol 8 patches have been added to the sol 9 cluster. what's the deal? I haven't found any information about whether or not this is a mistake.

Desiree,
Solaris 9's kernel patch 112233-12 was the last revision for that particular patch number. The individual zipfile became so large that it was subsequently supplanted by 117191-xx and that has also been supplanted when its zipfile became very large, by 118558-xx.
Consequently you will never see any newer version than 112233-12 on that particular patch.
What does <b>uname -a</b> show you for that system?
Solaris 8 SPARC was similarly effected, for 108528, 117000 and 117350 kernel patches.
If you have login privileges to Sunsolve, find <font color="teal">Infodoc 76028</font>.

Solaris 10 - patch for new DST 2007 changes

I am trying to track down the one patch I need for the new standard for daylight savings time date changes that took effect in 2007. Each time I get one patch and read the readme file, it tells me I need another patch for the U.S. Energy Policy Act for 2005. I am just about to install Solaris 10 patch 119689-07. I don't need any other patch updates, just the bare minimum new DST patch. Thanks for your help.

119689-07 is obsoleted by 118836. http://sunsolve.sun.com/search/document.do?assetkey=1-21-119689-07-1
118836-36 is latest rev of this patch -- the kernel patch, whic has latest timezone data for the OS
You'll need to make sure java has latest tz data, too:
http://java.sun.com/javase/timezones/
As far as I know, these are the bare minimums for a system to function properly re: latest DST schedule

Solaris 9 kernel patch

Similar Messages

Maybe you are looking for