Patching cluster from 11.2.0.1 to 11.2.0.3

I'm a long time Oracle DBA but have only recently started with RAC and have never done any patching or upgrades in a RAC environment.
My environment consists of a 2 node RAC cluster, and 2 physical standbys at separate remote locations.
The database, GI, ASM, and clusterware are all at version 11.2.0.1.
I want to upgrade all components to the latest patchset which is 11.2.0.3. Eventually I also want to apply the latest PSU.
Can I do this without down time? It is a mission critical database where downtime could conceivably endanger lives. If it can't be done with zero downtime, then downtime must be kept to an absolute minimum (minutes, not hours).
I suspect the clusterware needs to be patched first and I do not know whether I can do it on one node at a time.
Running the cluster on 1 node at a time is an option.
I welcome your suggestions.

Pl see if this slide deck can help - http://apex.oracle.com/pls/apex/f?p=202202:2:::::P2_SUCHWORT:bestpractice
Examples of near zero-downtime and rolling upgrade are in this deck - http://apex.oracle.com/pls/apex/f?p=202202:2:::::P2_SUCHWORT:migrate112
See slides beginning at 243 and 290
HTH
Srini

Similar Messages

Non priviledged commands fail after patch cluster install

For several years, to allow users to access system functions for higher clock resolutions in their
applications, we have made the following mods to two files (per Sun recommendations):
In the /etc/system file, add lines:
* 10 ms clock resolution*
set higher_tick = 1*
In /etc/user_attr, add:
dssuser::::type=normal;defaultpriv=proc_clock_highres,file_link_any,proc_info,proc_session,proc_fork,proc_exec
Everything was fine until I installed the latest patch cluster (from 2-14-2011) on our Netra 210. No issues installing the cluster. Upon reboot, the dssuser cannot do some simple things, like use ftp or ping. Messages like this:
ping: unknown host
ftp: socket: Permission denied.
The root user has no problems using any of these commands. As soon as I comment out the dssuser line from the /etc/user_attr file, everything works as expected. But we need the highres clock settings for our applications. I am unfamiliar with the workings and intent of the entries in user_attr so any help would be most appreciated.
Mark

The problem is that after patch implementation, the special privileges for any user defined in the /etc/user_attr file were modified to append the string "!net_privaddr" specifically denying use of common commands ping and ftp for example. The output of ppriv:
$ ppriv $$
14870: -sh
flags = <none>
E: basic,proc_clock_highres,!net_privaddr
I: basic,proc_clock_highres,!net_privaddr
P: basic,proc_clock_highres,!net_privaddr
L: all
I had to add the keyword net_privaddr in the user_attr file like:
dssuser::::type=normal;defaultpriv=proc_clock_highres,file_link_any,proc_info,proc_session,proc_fork,proc_exec,net_privaddr
to get past this problem. A bug or what?

Patch cluster pass code - NEW from Sun just to inconvenience you

Wow. A few of the admins here, myself included, had to throw the latest patch cluster onto a few of our servers. Sun is now requiring a pass code as an argument! And they've hidden the pass code in the README with the excuse that it's to get you to read it.
Anyway, this "pass code" is "s10cluster". So, you have to run "./installcluster --s10cluster" to get the thing to install. {grumble} A pass code to install a cluster. Ridiculous.{grumble}
That said, some of the other changes they've made to the install script are very welcome.

Sorry for spamming i just realized what do i make wrong after
3 hours of programig.
..({id'} has a missing @ mark :)

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

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@f,400000/esp@f,800000/sd@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@f,400000/esp@f,800000/sd@0,0
Boot device: /iommu/sbus/espdma@f,400000/esp@f,800000/sd@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.

Need patchset/patch cluster for solaris 10 5/09 update 7 to update8

Please let me know where i can download the patch cluster or patchset to upgrade solaris 10 5/09 from update 7 to update8
Solaris 10 5/09 s10s_u7wos_08 SPARC to Solaris 10 5/09 s10s_u8wos_08 SPARC
Its a 64 bit SPARC
Thanks in advance.
With Regards
Suresh Rao Jc
Edited by: user13549783 on 14-Apr-2012 05:55

Moderator Advice:
Welcome to the OTN forums.
This is your very first post to the forums, so before you go any further, a piece of advice:
When you give your post a title of "Hi All" it does not tell anyone anything about what your inquiry might be.
The topic title that you place onto each one of your posts is just as important as what you place into your post. It tells everyone whether they need to spend any time with it. It tells everyone whether you are worth spending time with, whether you will be able to understand what they type in a reply, how technical they can be in a response.
These are technical forums. They are not chat rooms for casual feel-good gatherings. They are not `blogs`. The site is also NOT a way to make contact to Oracle's technical support staff. The OTN community is from the entire globe and is from end-users that happen to have an interest in the topics you read here.
Spend some time reading the forum FAQ,
https://wikis.oracle.com/display/Forums/Forums+FAQ
which is linked at the top corner of every page.
Also, spend some time with the forums Terms Of Use
http://www.oracle.com/us/legal/terms/index.html
which is linked at the bottom of every page.
In particular, spend some time reviewing section #6 in that T.O.U.
When you make your posts more informative and easier to read then responses will be more helpful.
... now go back and edit your post. Change the title to something that better describes your actual question.

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.

9_Recommended patch cluster breaks ssh

Hi all,
I recently installed the latest 9_Recommended patch cluster and it has rendered ssh inoperable. I get the following error when I try to start ssh:
ld.so.1: sshd: fatal: libgss.so.1: open failed: No such file or directory
In doing some research, it seems that there is now a dependency on the SUNWgss packages. I either need to find a place where I can get this package from or remove the patch that has broken ssh.
Any ideas?

I have a case open as well. Here is the current response:
RFE for patch 113273-11
Take a look at this
But he did not give any approved workaround so I pinged him again and
await feedback.
For the "unable to initialize mechanism library
[usr/lib/gss/gl/mech_krb5.so]" (see bug 6392328)
The following workarounds were provided by PTS
and one of my customers confimred that workaound suggestion
number 1 worked for him
1) Turn off GSS-API support in ssh_config(4) and
sshd_config(4)
Add to /etc/ssh/ssh_config and /etc/ssh/sshd_config:
GSSAPIAuthentication=no
GSSAPIKeyExchange=no
2) Configure /etc/krb5/krb5.conf (even if Kerberos V is not in use) so
it contains no syntax errors.
attached krb5.conf was given to me by my backline support for you to
use.
All patches for SSH Solaris9
Solaris 9 Patches:
>>>
113273-10 SunOS 5.9: /usr/lib/ssh/sshd Patch
114356-06 SunOS 5.9: /usr/bin/ssh Patch
Solaris 9 Backport Patches:
Those patches are:
112908-24
117177-02
114356-07
113273-11
Based on previous patch dependencies you will want to confirm that
these previously released patches are also installed:
112908-01
112921-07
112922-02
112923-03
112924-01

10_Recommended patches: run from local filesystem

The install_cluster script for the latest Solaris 10 Recommended patch cluster checks to see if it's being run from a local filesystem.
If not, it bails out: Excerpt below:
df -l . > /dev/null 2>&1
if [ $? != 0 ]; then
echo "install_cluster must be run from a local filesystem.\n"
return 1
fi
Anyone know why?

Bumping this subject up.
Can someone please explain the reason for this check? Its only purpose seems to be to annoy system administrators.

Stub out Error Cluster from Error Code.vi?

When I profile my application, I find that the biggest consumer of CPU time is the Error Cluster from Error Code.vi, called from a number of locked NI libraries. How can I stub out this .vi, replacing it with basically a pass-through? I tried creating a project specific .vi with the same name, and when I open my project all the project and vi.lib .vis used link to it, but they all come up broken and have to be re-linked, which I can't do in the locked .vis (I matched the ins and outs and connector pattern). I can't edit the Error Cluster...vi directly, getting a message about the .vi being used by another application even with a clean start of LV and going directly to that .vi in the library (and I would prefer to not mess with the vi.lib version anyway). Any suggestions? Thanks. LV 2011.
Matt

If you have the LLB manager open it reserves your VI in a different appliation instance, therefore it is locked and no editing. Simply close the LLB manager and you can whack away at that VI.
I doubt that the shared clone setting plays much of a role here, there are some deeper issues. A rather amusing VI in a few ways:
In order to show the VI Title instead of the Name you Open a VI reference which is going to stick you into the root loop. 10 reentrent clones simply means 10 copies waiting in line for the root loop. A non-reentrent version would simply have 10 copies waiting to run. Minus the root loop issue, reentrency is the way to go, and on a desktop machine shared clones is typically quite effective.
It can't be a slow VI, look Trim Whitespace was inlined manually to avoid a performance hit! In a loop maybe, but really, shaving off the overhead of a single subVI? That's optimization.
But wait, all of that and much, much more is given right back by the use of Delete From Array to remove the first element of the Array. Bad on so many levels. Delete From Array is a data copy machine, and now you are doing one needlessly. Array subset is your friend here, tells the compiler you are only reading, nothing to get excited about. Pull it outside the case structure, you are ditching the first element twice in the two branches.
Concatenating strings in a loop, also a recipe for fun. Often there are ways to leverage Array to Spreadsheet string for better performance, or build a string array and then concatenate at the end. Probably not a big deal here, how big are call chains really, but if you are inlining subVIs by hand then you should really be frying the bigger fish.
I find myself in your shoes fairly often. Some clunker in vi.lib causes a bug or sluggish performance. You either ditch the NI code and roll your own, or make it work on your machine but not others, or chalk it up to the cost of doing business. I have tried on numerous occasions to suggest that all patches to vi.lib be made readily and freely available to all previous versions of LV that are compatible. Let's say this VI got tweaked so it was a bit more performant for you, at least enough to be viable. Then you could happily use the patched version in LV11, and if you went to a different machine you would simply make sure vi.lib was up-to-date. These types of patches could roll out incrementally as needed, less need to cross your fingers that you won the CAR lottery with each new version of LV. (I guess most lottery winners don't shell out $$$ to collect their "winnings" though).
After all that what would I do here? I would wrap that sucker inside a disable structure (provide minimal functionality, like pass through caller name, code and error instead). Then I would check the performance again. Now you have a data point as to whether or not it is worth it to proceed.

Latest Patch cluster (Feb 11, 2010) unable to run in Single user mode.

Hi ,
This is my first post in this forum.
Hope you people will help to resolve the issue.
My issue - I have downloaded the latest patch cluster (Feb 11, 20100) and tried to install it from single user mode.
Nothing happened. I have waited for more than 30 mins, still no progres.
Then I killed the process, and tried to run it in Multi user mode (To verify any issue with extraction or file) -- Its working(and killed the process) !!!
Anyone facing this strange issue ?
Appreciate your help to complete the patching.
Thanks.
sas.

Hi,
If you're encountering issues with a patch cluster bundle your best bet is to contact [email protected] From the description it sounds like there may be a filesystem not mounted in SUM that the cluster is trying to patch.

Latest Patch Cluster

Hi,
Can some help me, how to find and download the latest patch cluster package for sparc machine.
Thanks
Karthik

Moderator Action:
Not a hardware question. It is an OS question.
Your post has been moved from the hardware forum you had put it into
to a Solaris forum.
(we guessed Solaris 10 -- you didn't botrher to mention what you are using.)
Suggestion:
Since patches and patch clusters are only available to those with service contract login credentials to Oracle Support, you might try to log into MOS and search over there.

Obtaining obsoleted Sun Alert patch Cluster

I need to build a Solaris 10 Sparc update 3 with Sun Alert Patch Cluster July 16 2007.
I cannot use a more recent Solaris instal version, nor can I use a more recent Sun Alert Patch Cluster version.
I cannot locate this specific Sun Alert Patch Cluster version for download from Sunsolve.
Can anyone advise if it is possible to obtain this Sun Alert Patch Cluster?

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

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.

Patching cluster from 11.2.0.1 to 11.2.0.3

Similar Messages

Maybe you are looking for