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

Similar Messages

  • ABAP and Kernel Patches for Upgrade and Conversion in 4.6C

    Hi,
    We are in a process of upgrade and unicode conversion for the source release 4.6C (Kernel  46D_EXT Patch 2225).
    "Combined Upgrade&Unicode Conversion Guide"  for "SAP Basis 4.6C u2192 SAP NetWeaver 7.0 application Server ABAP Unicode Including Enhancement Package 1 Support Package 01 - 06" , In Software Requirements step,  it says
    "3. Import 4.6D Kernel patch 2326 from SAP Service Marketplace according to SAP Note 19466"
    We wanted to know whether "IT IS ABSOLUTELY NECCESSARY TO GO FOR THE KERNEL PATCH 2326".  We dont have "EBCIDIC code pages" in our MDMP system.
    We need to know  becauase we are also doing OS migration from AIX to Sun and this step will add to our production downtime.
    Please advice what are the other causes we should go for the kernel 2326.
    Regards

    Hello Mr. Nils Buerckel,
    Thanks for the reply.
    We wanted to be very sure whether we should used Kernel 46D Kernel patch 2326 (As it is specifically mentioned in the SAP CU&UC guide and in SAP Note 867193, It is mentioned that  "This patch contains enhancements that are required to execute the "INDX Analysis" scan)
    OR
    Can we go for the latest kernel patch avaialable at market place? And Will the latest kernel patch also contains the "enhancements that are required to execute the "INDX Analysis" ?
    Please reply
    Thanks

  • 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 <i>SUPPORT PACKAGE --> Load FROM FORNT END</i>. then upload the car files and <i>Display/Define Queue</i>. then <i>Import Queue</i>. after queue is imported, <i>Confirm</i>
    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

  • MSCS and Kernel patches: Can someone please refresh my memory?

    Greetings,
    We run 4.7 Ent on a 2-node MSCS Cluster (SQL).
    I need to do a kernel upgrade, but I have forgotten the precise distribution of kernel files outside of the "run" directory for the cluster.
    I understand they are:
    Main Kernel Files
    shared_drive \usr\sap\<SID>\SYS\exe\run
    MSCS Files (on each node)
    local_drive \Windows\SapCluster\
    local_drive \Windows\System32\
    However, could someone please remind me which files go into
    "SapCluster" and "System32", or if you know the location, point me to an SAP document that details the kernel patch process in an MSCS Cluster (rather than a general MSCS config document which is of no use in this situatio).
    Thanks if anyone is able to help.
    Tim
    Edited by: Tim McKenzie on May 28, 2008 4:52 PM

    Hi Tim,
    We have a productive SAP R/3 4.7 (Windows 2003 IA64 Oracle 9.2) on a 2 nodes MSCS cluster.
    In C:\windows\SapCluster
    We have the following files :
    backint.exe
    brarchive.exe
    brbackup.exe
    brconnect.exe
    brgui
    brrecover.exe
    brrestore.exe
    brspace.exe
    brtools.exe
    cpio.exe
    cpqccms.dll
    dd.exe
    dev_rout
    mkszip.exe
    mt.exe
    niping.exe
    pstat.exe
    rfcoscol.exe
    routtab.txt
    sapevents.dll
    sapgw
    sapntchk.exe
    sapntwaitforhalt.exe
    saposcol.exe
    saprouter.exe
    sapsrvkill.exe
    sapstart.exe
    sapstartsrv.exe
    sapstartsrv.exe.new
    sapxpg.exe
    uncompress.exe
    So basically the SAP cluster dlls and the brtools.
    We have also  C:\windows\SapCluster\brgui with the brgui files
    and C:\windows\SapCluster\sapgw with the standalone gateway executables
    In C:\windows\system32 we have these SAP files :
    sapmmc.dll
    sapmmcada.dll
    sapmmcinf.dll
    sapmmcms.dll
    saprc.dll
    saprcex.dll
    sapstart.log
    sapstartsrv.exe
    To update the kernel, we do it one node after the other one switching the SAP resources between the 2 nodes .
    We of course keep the same patch level in the different directories.
    Hope this helps.
    Olivier
    Hope this helps.

  • 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

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

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

  • 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

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

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

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

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

Maybe you are looking for