Recommended patch cluster release

Hello,
How often is the Recommended Patch cluster released?
A Couple of years ago, i was told at a Sun event during a session, that changes has been made en the way patch cluster was created, and that the patch clusters was created 4 times a year, to make it more streamlike, instead of creating patchclusters once in a while, when enough patches has been created. I need to know if it still works the way, that patch cluster are created 4 times a year, it is to be used with patch procedures and recommendations.
Best regards
Yngve Berthelsen

Recommended patch sets are and to the best of my knowledge have always been regenerated twice a month.
I think your thinking of maintenance releases. When they generate a new CD image which can be used to do an upgrade install.
They try to generate those every 6 months, but the schedule often slips.
The two most recent were sol10 11/06 and sol10 8/07.

Similar Messages

  • How to backout a Recommended Patch cluster deployment in Solstice disksuite

    Hello Admin's,
    I am planning to use the following Plan of action for deploying the latest Solaris 8 Recommended Patch cluster on the production server's i support.My
    concern is if the patching activity fails or the application and Oracle databases dont come up after deploying the patch cluster.How do i revert back to system to its original state using the submirror's which i have detached prior to patching the system :
    1) Will shutdown the applications and the databases on the server:
    2) Will capture the output of the following commands :
    df -k
    ifconfig -a
    contents of the files /etc/passwd /etc/shadow /etc/vfstab /etc/system
    metastat -p
    netstat -rn
    prtvtoc /dev/rdsk/c1t0d0s0
    prtvtoc /dev/rdsk/c1t1d0s0
    3) We bring the system to the ok prompt
    4) We will try to boot the system from both the disk's which are part of the d10 metadevice for root filesystem
    =======================================================================================
    user1@myserver>pwd ; df -k / ; ls -lt | egrep '(c1t0d0s0|c1t1d0s0)' ; prtconf -vp | grep bootpath ; metastat d10
    /dev/dsk
    Filesystem kbytes used avail capacity Mounted on
    /dev/md/dsk/d10 8258597 3435895 4740117 43% /
    lrwxrwxrwx 1 root root 43 Jul 28 2003 c1t0d0s0 -> ../../devices/pci@1c,600000/scsi@2/sd@0,0:a
    lrwxrwxrwx 1 root root 43 Jul 28 2003 c1t1d0s0 -> ../../devices/pci@1c,600000/scsi@2/sd@1,0:a
    bootpath: '/pci@1c,600000/scsi@2/disk@0,0:a'
    d10: Mirror
    Submirror 0: d11
    State: Okay
    Submirror 1: d12
    State: Okay
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 16779312 blocks
    d11: Submirror of d10
    State: Okay
    Size: 16779312 blocks
    Stripe 0:
    Device Start Block Dbase State Hot Spare
    c1t0d0s0 0 No Okay
    d12: Submirror of d10
    State: Okay
    Size: 16779312 blocks
    Stripe 0:
    Device Start Block Dbase State Hot Spare
    c1t1d0s0 0 No Okay
    user1@myserver>
    ===================================================================================
    ok nvalias backup_root <disk path>
    Redefine the boot-device variable to reference both the primary and secondary submirrors, in the order in which you want to access them. For example:
    ok printenv boot-device
    boot-device= disk net
    ok setenv boot-device disk backup_root net
    boot-device= disk backup_root net
    In the event of primary root disk failure, the system automatically boots from the secondary submirror. To test the secondary submirror, boot the system manually, as follows:
    ok boot backup_root
    user1@myserver>metadb -i
    flags first blk block count
    a m p luo 16 1034 /dev/dsk/c1t0d0s7
    a p luo 1050 1034 /dev/dsk/c1t0d0s7
    a p luo 2084 1034 /dev/dsk/c1t0d0s7
    a p luo 16 1034 /dev/dsk/c1t1d0s7
    a p luo 1050 1034 /dev/dsk/c1t1d0s7
    a p luo 2084 1034 /dev/dsk/c1t1d0s7
    o - replica active prior to last mddb configuration change
    u - replica is up to date
    l - locator for this replica was read successfully
    c - replica's location was in /etc/lvm/mddb.cf
    p - replica's location was patched in kernel
    m - replica is master, this is replica selected as input
    W - replica has device write errors
    a - replica is active, commits are occurring to this replica
    M - replica had problem with master blocks
    D - replica had problem with data blocks
    F - replica had format problems
    S - replica is too small to hold current data base
    R - replica had device read errors
    user1@myserver>df -k
    Filesystem kbytes used avail capacity Mounted on
    /dev/md/dsk/d10 8258597 3435896 4740116 43% /
    /dev/md/dsk/d40 2053605 929873 1062124 47% /usr
    /proc 0 0 0 0% /proc
    fd 0 0 0 0% /dev/fd
    mnttab 0 0 0 0% /etc/mnttab
    /dev/md/dsk/d30 2053605 937231 1054766 48% /var
    swap 2606008 24 2605984 1% /var/run
    swap 6102504 3496520 2605984 58% /tmp
    /dev/md/dsk/d60 13318206 8936244 4248780 68% /u01
    /dev/md/dsk/d50 5161437 2916925 2192898 58% /opt
    user1@myserver>metastat d40
    d40: Mirror
    Submirror 0: d41
    State: Okay
    Submirror 1: d42
    State: Okay
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 4194828 blocks
    d41: Submirror of d40
    State: Okay
    Size: 4194828 blocks
    Stripe 0:
    Device Start Block Dbase State Hot Spare
    c1t0d0s4 0 No Okay
    d42: Submirror of d40
    State: Okay
    Size: 4194828 blocks
    Stripe 0:
    Device Start Block Dbase State Hot Spare
    c1t1d0s4 0 No Okay
    user1@myserver>metastat d30
    d30: Mirror
    Submirror 0: d31
    State: Okay
    Submirror 1: d32
    State: Okay
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 4194828 blocks
    d31: Submirror of d30
    State: Okay
    Size: 4194828 blocks
    Stripe 0:
    Device Start Block Dbase State Hot Spare
    c1t0d0s3 0 No Okay
    d32: Submirror of d30
    State: Okay
    Size: 4194828 blocks
    Stripe 0:
    Device Start Block Dbase State Hot Spare
    c1t1d0s3 0 No Okay
    user1@myserver>metastat d50
    d50: Mirror
    Submirror 0: d51
    State: Okay
    Submirror 1: d52
    State: Okay
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 10487070 blocks
    d51: Submirror of d50
    State: Okay
    Size: 10487070 blocks
    Stripe 0:
    Device Start Block Dbase State Hot Spare
    c1t0d0s5 0 No Okay
    d52: Submirror of d50
    State: Okay
    Size: 10487070 blocks
    Stripe 0:
    Device Start Block Dbase State Hot Spare
    c1t1d0s5 0 No Okay
    user1@myserver>metastat -p
    d10 -m d11 d12 1
    d11 1 1 c1t0d0s0
    d12 1 1 c1t1d0s0
    d20 -m d21 d22 1
    d21 1 1 c1t0d0s1
    d22 1 1 c1t1d0s1
    d30 -m d31 d32 1
    d31 1 1 c1t0d0s3
    d32 1 1 c1t1d0s3
    d40 -m d41 d42 1
    d41 1 1 c1t0d0s4
    d42 1 1 c1t1d0s4
    d50 -m d51 d52 1
    d51 1 1 c1t0d0s5
    d52 1 1 c1t1d0s5
    d60 -m d61 d62 1
    d61 1 1 c1t0d0s6
    d62 1 1 c1t1d0s6
    user1@myserver>pkginfo -l SUNWmdg
    PKGINST: SUNWmdg
    NAME: Solstice DiskSuite Tool
    CATEGORY: system
    ARCH: sparc
    VERSION: 4.2.1,REV=1999.11.04.18.29
    BASEDIR: /
    VENDOR: Sun Microsystems, Inc.
    DESC: Solstice DiskSuite Tool
    PSTAMP: 11/04/99-18:32:06
    INSTDATE: Apr 16 2004 11:10
    VSTOCK: 258-6252-11
    HOTLINE: Please contact your local service provider
    STATUS: completely installed
    FILES: 150 installed pathnames
    6 shared pathnames
    19 directories
    1 executables
    7327 blocks used (approx)
    user1@myserver>
    =======================================================================================
    5) After successfully testing the above we will bring the system to the single user mode
    # reboot -- -s
    6) Detach the following sub-mirrors :
    # metadetach -f d10 d12
    #metadetach -f d30 d32
    #metadetach -f d40 d42
    #metadetach -f d50 d52
    # metastat =====> (to check if the submirror�s are successfully detached)
    7) Applying patch on the server
    After patch installation is complete will be rebooting the server to single user mode
    # reboot -- -s
    confirming if patch installation was successful (uname �a) .
    8) Will be booting the server to the multiuser mode (init 3) and confirming with the database and the application teams if the
    Applications/databases are working fine .Once confirmed successful will be reattaching the d12 submirror.
    # metattach d12 d10
    # metattach d30 d32
    #metattach d40 d42
    # metattach d50 d52
    # metastat d10 =====> (to check the submirror is successfully reattached)
    user1@myserver>uname -a ; cat /etc/release ; date
    SunOS myserver 5.8 Generic_117350-04 sun4u sparc SUNW,Sun-Fire-V210
    Solaris 8 HW 12/02 s28s_hw1wos_06a SPARC
    Copyright 2002 Sun Microsystems, Inc. All Rights Reserved.
    Assembled 12 December 2002
    Mon Apr 14 17:10:09 BST 2008
    -----------------------------------------------------------------------------------------------------------------------------

    Recommended patch sets are and to the best of my knowledge have always been regenerated twice a month.
    I think your thinking of maintenance releases. When they generate a new CD image which can be used to do an upgrade install.
    They try to generate those every 6 months, but the schedule often slips.
    The two most recent were sol10 11/06 and sol10 8/07.

  • Solaris 10 SPARC Recommended Patch Cluster for  2008 quarter 3 version

    Dear All,
    Could any one please guide me, where I can download "Solaris 10 SPARC Recommended Patch Cluster" for 2008 quarter 3 version.
    I have checked in sunsolve.sun.com, I'm able to find only the latest release.
    please guide me.
    Thanks and regards,
    veera

    Ok,
    Here's a cute little formula to try using your systems parameters to gain some "head's-up" on an expected or estimated time to complete the patch run.
    You will need a few things to prepare.
    Number of "real" CPU's (not hyperthreads)
    Speed of each CPU as a whole number i.e 2.87Ghz = 2,867
    the total number of patches from the cluster i.e. Sept 15th = 381 (Solaris 10)
    Network factor if using NFS = 2.5
    local cluster file factor = 1.5
    Patch cluster on CDROM factor = 3.25
    Now, combine all of those elements in this equation:
    { ( #1 * #2 ) / #3 * factor(#4 or #5 or #6) }
    This will yield a number in minutes of patch run time. Then all you will need to add is the standard boot up time to get the total of all patching and reboot.
    Of course you could write a script to extract all of this information and feed it to "bc -l" to get a quick figure.
    Example, on one of my Solaris 10 boxes with the information filled in to the equation:
    #> echo "((4*2660)/381)*1.5"|bc -l
    #> 41.88976377952755905511
    It actually took 44.2 minutes to complete the patching of this box plus another 12 minutes to reboot. But all in all a pretty fair estimate I think.

  • MB.ACT light OFF --- after Solaris 9 recommended patch cluster applied

    After applying the recommended patch cluster to several SunFire V210s/V240s the "system ready" or "activity" light on the front panel no longer illuminates. The systems come up fine and are fully functional, just no light.
    While this has absolutely no impact on usability it is a bit disconcerting for the folks in the server room when glancing at the rack and not seeing the typical green light.
    I first noticed the problem in mid 2007 and have tried patch clusters as recent as last month, but the light remains out.
    One interesting discovery is that if I reset (hard) the ALOM module the light comes back on. However, if the system is subsequently rebooted for any reason the light does not come back on...
    If anyone can shed some light on the issue I would greatly appreciate it!
    -Sap

    continued.
    I removed patch 138217-01 (svccfg & svcprop patch) and re-applied it.
    Then, after booting into S-mode, I tried to continue with the broken patch 139555-08 (kernel).
    It ends with
    ! root@jumpstart:/var/spool/patch # patchadd 139555-08
    Validating patches...
    Loading patches installed on the system...
    Done!
    Loading patches requested to install.
    Preparing checklist for non-global zone check...
    Checking non-global zones...
    This patch passes the non-global zone check.
    139555-08
    Summary for zones:
    Zone oem
    Rejected patches:
    None.
    Patches that passed the dependency check:
    139555-08
    Patching global zone
    Adding patches...
    Checking installed patches...
    Executing prepatch script...
    Installing patch packages...
    Pkgadd failed. See /var/tmp/139555-08.log.21103 for details
    Patchadd is terminating.
    ! root@jumpstart:/var/spool/patch #the logfile shows
    ! root@jumpstart:/var/spool/patch # vi /var/tmp/139555-08.log.21103
    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.
    pkgadd: ERROR: couldn't lock in /var/run/.patchSafeMode/root/var/sadm/install (s
    erver running?): Resource temporarily unavailable
    Installation of <SUNWarc> failed (internal error).
    No changes were made to the system.Help!
    -- Nick

  • Solaris reboot loop after recommended patch cluster

    Hi,
    I have a problem with my solaris 10 x86 install on my intel notebook. after installing the latest recommended patch cluster and the necessary reboot my latop stays in a loop.
    one of the last lines I was able to see:
    panic&#91;cpu0&#93;/thread=fec1d660: boot_mapin():No pp for pfnum=20fff
    fec33b4c genunix:main+1b ()
    skipping system dump - ....
    rebooting...
    any ideas ?
    cu+thx

    This horrible patch caught me out too. I found this and it fixed my problem.
    http://weblog.erenkrantz.com/weblog/software/solaris
    <snip>
    &#91;...at the Solaris boot prompt; enable kmdb, debugging, and single-user
    so that you can remove the patch and reboot...&#93;
    boot -kds
    &#91;...wait for it to boot...&#93;
    physmax:w
    :c
    &#91;...you'll see 'stop on write of'...&#93;
    physmax/X
    &#91;...you'll see something like the following line:
    physmax: bff7f
    this is a hex number; add one; so if you see bff7f,
    your next line will need to be bff80...&#93;
    physxmax/W bff80
    :c
    &#91;...system will boot and go into single user mode...
    now, go toss those patches...&#93;
    patchrm 118844-19 120662-03 118345-12 118376-04 \
    118565-03 118886-01 119076-10 118813-01 \
    118881-02 120082-07 119851-02
    shutdown -i6 -y -g0 "sun should test their patches"
    </snip>

  • Problem: installing Recommend Patch Cluster: patch 140900-10 fails

    I don't know if this is correct location for this thread (admin/moderator move as required).
    We have a number of Solaris x86 hosts (ie 4) and I'm trying to get the patched and up to date.
    I obtained the latest Recommended Patch Cluster (dated 28Sep2010).
    I installed it on host A yesterday, 2 hours 9 mins, no problems.
    I tried to install it on host B today, and that was just a critical failure.
    Host B failed to install 140900-01, because the non global zones rejected the patch because dependancy 138218-01 wasn't installed in the non global zones.
    Looking closer, it appears that 138218-01 is for global zone installation only; so it makes sense that the non global zones rejected it.
    However, both hosts were in single user mode when installing the cluster and both hosts have non global zones.
    140900-01 installed on host A with log:
    | 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 <SUNWcsu> was successful.
    140900-1 failed on host B with this log:
    | Validating patches...
    |
    | Loading patches installed on the system...
    |
    | Done!
    |
    | Loading patches requested to install.
    |
    | Done!
    |
    | Checking patches that you specified for installation.
    |
    | Done!
    |
    |
    | Approved patches will be installed in this order:
    |
    | 140900-01
    |
    |
    | Preparing checklist for non-global zone check...
    |
    | Checking non-global zones...
    |
    | Checking non-global zones...
    |
    | Restoring state for non-global zone X...
    | Restoring state for non-global zone Y...
    | Restoring state for non-global zone Z...
    |
    | This patch passes the non-global zone check.
    |
    | None.
    |
    |
    | Summary for zones:
    |
    | Zone X
    |
    | Rejected patches:
    | 140900-01
    | Patches that passed the dependency check:
    | None.
    |
    |
    | Zone Y
    |
    | Rejected patches:
    | 140900-01
    | Patches that passed the dependency check:
    | None.
    |
    |
    | Zone Z
    |
    | Rejected patches:
    | 140900-01
    | Patches that passed the dependency check:
    | None.
    |
    | Fatal failure occurred - impossible to install any patches.
    | X: For patch 140900-01, required patch 138218-01 does not exist.
    | Y: For patch 140900-01, required patch 138218-01 does not exist.
    | Z: For patch 140900-01, required patch 138218-01 does not exist.
    | Fatal failure occurred - impossible to install any patches.
    | ----
    | patchadd exit code : 1
    | application of 140900-01 failed : unhandled subprocess exit status '1' (exit 1 b
    | ranch)
    | finish time : 2010.10.02 09:47:18
    | FINISHED : application of 140900-01
    It looks as if the patch strategy is completely different for the two hosts; both are solaris x86 (A is a V40z; B is a V20z).
    Trying to use "-G" with patchadd crabs the patch is for global zones only and stops (ie it's almost as if it thinks installation is being attempted in a non global zone).
    Without "-G" same behavior as patch cluster install attempt (no surprise there).
    I have inherited this machines; I am told each of these machines were upgraded to Solaris 10u6 in June 2009.
    Other than the 4-5 months it took oracle to get our update entitlement to us, we've had no problems.
    I'm at a loss here, I don't see anyone else having this type of issue.
    Can someone point the way...?
    What am I missing...?

    Well, I guess what you see isn't what you get.
    Guess I'm used to the fact USENET just left things formatted the way they were :-O

  • Problem install Recommended Patch cluster

    Trying to install the Recommended patch cluster on Ultra 45s, on each one, the 40th patch, 120272-28, fails, and I don't understand why. Here's the snippet from the log:
    STARTING : application of 120272-28
    start time : 2010.11.30 08:41:42
    # /usr/sbin/patchadd 120272-28
    Validating patches...
    Loading patches installed on the system...
    Done!
    Loading patches requested to install.
    Done!
    The following requested patches have packages not installed on the system
    Package SUNWsmaS from directory SUNWsmaS in patch 120272-28 is not installed on the system. Changes for package SUNWsmaS will not be applied to the system.
    Checking patches that you specified for installation.
    Done!
    The following requested patches will not be installed because
    they are incompatible with patches already installed or with
    other patches that you have specified for installation. In order to install these
    requested patches you should resolve this incompatibility
    by removing incompatible patches from requested-to-install set
    or from the system.
    0 Patch 120272-28 is declared as incompatible by IDR138540-01, which has already been installed on the system.
    No patches to install.
    patchadd exit code : 3
    application of 120272-28 failed : unhandled subprocess exit status '3' (exit n branch)
    finish time : 2010.11.30 08:41:42
    FINISHED : application of 120272-28
    I don't understand why it fails, rather than just being "skipped", as several other patches are. I assume the failure isn't coming from the fact that it's been declared incompatible, but rather the "unhandled subprocess exit status". How do I determine what that is?
    Or, better yet, how do I tell the installcluster script to just not do that one?
    Thanks!

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

  • Management console problem after installing recommended patch cluster

    Hello everyone.
    I just got a new SUN 440 server, it didn't come with the solaris os installed and so I installed solaris 9 12/03 to it. The installation went fine and I could start the management console with no problems at all. Then I went to sunsolve.sun.com to download the latest recommended patch clusters for solaris 9 (this was yesterday Sept.-06-2006), I downloaded the file, checked it with md5sum, unzipped it, went to single user mode and ran the install_patch script. After the patch cluster finished installing I rebooted the server for the patches to take effect, I logged in, tried to run console management 2.1 and it starts OK but I cannot use any services it offers because it says (in the console events):
    "Server Not Running: no solaris management console server was available on the specified server. Please ensure there is a Solaris Management Console server available on the specified host and that it is running"
    When I click on "See Exception" I get (for a particular service that is... in this case com.sun.admin.fsmgr.client.VFsMgr - for managing file systems):
    java.rmi.RemoteException: Server RMI is null:
    at sun.com.management.viperimpl.client.ViperClient.lookupServer(ViperClient.java:376)and so on...
    I already checked that the service is running on port 898 and it seems that there is no other app. using that same port. I also restarted the service using /etc/init.d.init stop/status/start but I get the same results.
    I don't know solaris very much and don't know what else to do, please help.
    Thanks in advance.

    Well, I guess what you see isn't what you get.
    Guess I'm used to the fact USENET just left things formatted the way they were :-O

  • SPARC10 not booting after 2.5.1 Recommended Patch Cluster Install

    Hi everyone,
    Just finished installing the "latest" patch cluster on my ancient SPARC10, and now it doesn't boot. Here's what I see:
    ok boot /iommu/sbus/espdma&#64;f,400000/esp&#64;f,800000/sd&#64;0,0
    screen not found.
    Can't open input device.
    Keyboard not present. Using tty for input and output.
    SPARCstation 10 (1 X 390Z55), No Keyboard
    ROM Rev. 2.25, 112 MB memory installed, Serial #6332710.
    Ethernet address 8:0:20:12:7f:99, Host ID: 7260a126.
    Rebooting with command: /iommu/sbus/espdma&#64;f,400000/esp&#64;f,800000/sd&#64;0,0
    Boot device: /iommu/sbus/espdma&#64;f,400000/esp&#64;f,800000/sd&#64;0,0 File and args:
    not found: abort_enable
    not found: abort_enable
    not found: tod_validate
    not found: tod_fault_reset
    krtld: error during initial load/link phase
    Memory Address not Aligned
    Type help for more information
    ok
    At first I thought I had a RAM problem. I've swapped RAM, but that didn't make it boot. I then thought I had a system board problem. I've swapped that as well, and still no dice. I wish I'd have kept the list of patches that successfully installed like my gut told me to, but I didn't. Searching Google and the Sun websites didn't turn up any fixes to the problem, so I'm hoping I can find help here.
    Did the patches clobber something the machine needs to boot? I believe the OS disks are mirrored, and I've tried booting off each submirror, but the result is the same.
    If I can avoid booting off of CD-ROM, that would be ideal since I don't have an external CD-ROM available to boot from.
    Thanks for any help!

    Ouch !
    Haven't seen that one in years !
    It's your choice of that ancient Operating Environment, combined with a cpu faster than 419MHz.
    I hope you still have the extra OECD disk that was packed with that system when it was first shipped from Sun.
    Otherwise you may just be out of luck with using Solaris 2.5.1
    Here's a link at a non-Sun 3rd party web site to SRDB document *20576*
    http://www.sunshack.org/data/sh/2.1/infoserver.central/data/syshbk/collections/intsrdb/20576.html
    Perhaps MAAL and haroldb can contribute their thoughts on this.

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

  • Where are older Recommended Patch Clusters located?

    My project is spec'd to use the June 2009 Recommended Patch Cluster release, but I can't find the previous patch cluster releases. Is there anywhere on the Sun site that I can find the older patch clusters?

    I ended up calling out Sun support, and after about a week he got back with us and said that although usually such a patch is available on a DVD he recieves every month, the June 2009 DVD was pulled due to "quality issues". Thank you both for your support.

  • Solaris 8 x86 patch cluster installation

    hi. i recently installed solaris 8 x86 on my intel p4 machine. i got through the installation fine but i am now running into problems with installing the 8x86 recommended patch cluster.
    whenever i run the install_cluster script, it says every patch failed to install due to return code 1. i even tried manually installing the patches manually via patchadd...but i end up getting a message saying the patch directory is not valid.
    i basically downloaded the 8x86 recommended patch cluster zip file on a windows 2k machine. i unzip the file and then burn the patches onto a cd. i then copy the patches from the cd onto my solaris machine and try to install the patches that way. so far...this doesn't work..and i dont know what im doing wrong.
    does anyone know how to fix this problem? thx.

    hi again. i just fixed my problem. apparently when i unzipped the file and then burned it onto cd...the data got corrupted. i fixed it by copying the zip file onto cd and then extracting the patches onto the solaris machine.

  • Installing new patch cluster after os is hardened with Jass 4.2

    hi, i have a Solaris 10 system that's hardened with Jass 4.2. what is the correct way/best practice to apply the latest recommended patch cluster?
    will applying the latest recommended patch cluster 'un harden' the system?
    thanks.

    Well, I guess what you see isn't what you get.
    Guess I'm used to the fact USENET just left things formatted the way they were :-O

  • How can install the latest SUN patch cluster on individual zones?

    I have a global zone running Solaris 10 (11/06). I have a number of whole root zones running. I only want to apply the latest Sun Recommended patch cluster to a few of the individual local zones. Can this be done? How do I run install_cluster at the global and have it apply to only some of the local zones?
    thanks in advance,
    Brock

    bgammel wrote:
    I have a global zone running Solaris 10 (11/06). I have a number of whole root zones running. I only want to apply the latest Sun Recommended patch cluster to a few of the individual local zones. Can this be done? How do I run install_cluster at the global and have it apply to only some of the local zones?It really makes no sense to talk about a patch cluster this way. For some individual patches in the cluster, it may be possible for others not.
    If a patch applies to the kernel, it makes no sense to apply to some zones and not others (or not the global zone). Otherwise you'd have files out of sync with the running kernel.
    For other patches that are purely application-specific, it could be just fine. Something that patches 'sed' for instance should apply cleanly to a whole-root zone.
    You'll need to read the notes for the individual patches.
    Darren

  • Patch cluster backout

    How to remove patch cluster without going through patchrm command on each patch individually?
    The latest cluster that we installed is not testing well. One application is generating the Segmentation Fault Error due to an updated version of the X Windows Library . See more info on this bug:
    http://forums.vni.com/showthread.php?p=1599#post1599
    I only see two options, either implement a fix for this bug (if it is available out there some where) or remove the entire patch bundle. If I know which patch is the culprit patch then I may be able to uninstall that patch it self instead of removing the entire bundle.
    Need Help. Thanks!
    MK

    If you are talking about the Recommended Patch Cluster for SunOS 10 :
    http://sunsolve.sun.com/private-cgi/show.pl?target=patches/patch-access
    I have downloaded the cluster to my home directory, and reviewed the cluster for a possible Uninstall script, which in this case doesnt exist.
    I did read the README file located in the cluster that states the following :
    SAVE AND BACKOUT OPTIONS:
    By default, the cluster installation procedure uses the patchadd
    command save feature to save the base objects being patched. Prior to
    installing the patches the cluster installation script will first
    determine if enough system disk space is available in /var/sadm/patch
    to save the base objects and will terminate if not. Patches can only
    be individually backed out with the original object restored if the
    save option was used when installing this cluster. Please later refer
    to the patchrm command manual page for instructions and more
    information. It is possible to override the save feature by using the
    [-nosave] option when executing the cluster installation script. Using
    the nosave option, however, means that you will not be able to backout
    individual patches if the need arises.

Maybe you are looking for

  • Is there an hp wireless printer that uses 21 & 22 ink?

    I have an old hp printer and want to purchase a wireless. I have ink for the old printer can I use on a new hp wireless printer?

  • How can I tell iTunes to NOT convert certain files from wma format?

    I just got an iPod classic, and downloaded iTunes and it automatically started adding all my music. I have almost 5000 songs that are in wma format, and it started converting them all. Then after it got almost 2000 songs finished, it just stopped. Fo

  • Screen flickers continuously.

    Hi i have recently got HP pavilion G6 and everything was going smooth for like 4 months, but just today ive got the screen flickering problem. the screen doesnt flicker allways, just in some aplications like task manager o some games. it is really an

  • How to know a list of columns for people search

    Hi Guys, I am using .Net code that calls search.asmx.  I am calling the following query and it is working. <QueryPacket xmlns='urn:Microsoft.Search.Query'><Query><Context><QueryText language="en-US" type="MSSQLFT">SELECT Title, JobTitle, FirstName, L

  • Zero bleed at inside page on even and odd master pages

    Hello guys!  Going directly to my question would be how to apply bleed option specifically on inside pages when working with individual master pages for master and facing pages on the main document. The thing is when I've set no bleed on inside on my