Recommended Patch 118918-24 fails

Hi
I have installed the latest Solaris 10 update 5.
And I have downloaded the Recommended Patches . But, while I try to install I get failure message:
Following patches failed to apply :
118918-24
Aborting due to failure while applying patch 118918-24.
The log file shows :
Application of this patch should have succeeded - this failure is unexpected.
Please assess cause of failure and verify system integrity before proceeding.
# /usr/sbin/patchadd 118918-24
Validating patches...
Loading patches installed on the system...
Done!
Loading patches requested to install.
Version of package SUNWcakr from directory SUNWcakr.u in patch 118918-24 differs
from the package installed on the system.
Version of package SUNWcar from directory SUNWcar.u in patch 118918-24 differs f
rom the package installed on the system.
Version of package SUNWcakr from directory SUNWcakr.us in patch 118918-24 differ
s from the package installed on the system.
Version of package SUNWcar from directory SUNWcar.us in patch 118918-24 differs
from the package installed on the system.
Done!
The following requested patches have packages not installed on the system
Package SUNWhea from directory SUNWhea in patch 118918-24 is not installed on th
e system. Changes for package SUNWhea will not be applied to the system.
No patches to check dependency.
patchadd exit code : 1
application of 118918-24 failed
FINISHED : application of 118918-24
Could somebody help please??

Please state what option did you choose while installing Solaris 10 update 5? Did you install the "entire distribution" or "OEM"
SUNWhea points to SunOS C/C++ header files for general development of software. Make sure you have Solaris 10 and not Solaris 9 headers installed.
-GGR

Similar Messages

Recommended patch 125541-02 fails to install

Patch 125541-02 fails to install. When it is running patchadd perhaps, it complains that the dependency package SUNWthunderbird is not present. I am not inclined to search and add support for it unless it is necessary. I tried it five different hosts running Solaris 10. The results are the same.

I had exactly the same results on a Sun Blade running Sol 10 11/06. The patch will not install using update manager, or with smpatch add -i, or from the manually downloaded patch using patchadd.
The following requested patches have packages not installed on the system
Package SUNWthunderbird from directory SUNWthunderbird in patch 125541-02 is not installed on the system. Changes for package SUNWthunderbird will not be applied to the system.

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

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.

Patch 120185-09 failed to install (SO update 5)

hi,
on a SunOS 5.9 Generic_117171-09 sun4u sparc SUNW,Sun-Fire-15000
i have this error:
Checking installed patches...
Verifying sufficient filesystem capacity (dry run method)...
Patch 120185-09 failed to install due to a failure produced by pkgadd.
See /var/sadm/patch/120185-09/log for details
Patchadd is terminating.
14:29 filesrv1:/home/mets1/wcohrs>more /var/sadm/patch/120185-09/log
Package not patched:
PKG=SUNWstaroffice-es
Original package not installed.
Package not patched:
PKG=SUNWstaroffice-es-help
Original package not installed.
Package not patched:
PKG=SUNWstaroffice-es-res
Original package not installed.
Package not patched:
PKG=SUNWstaroffice-fr
Original package not installed.
Package not patched:
PKG=SUNWstaroffice-fr-help
Original package not installed.
Package not patched:
PKG=SUNWstaroffice-fr-res
Original package not installed.
Package not patched:
PKG=SUNWstaroffice-hu
Original package not installed.
Package not patched:
PKG=SUNWstaroffice-hu-help
Original package not installed.
Package not patched:
PKG=SUNWstaroffice-hu-res
Original package not installed.
Package not patched:
PKG=SUNWstaroffice-it
Original package not installed.
Package not patched:
PKG=SUNWstaroffice-it-help
Original package not installed.
Package not patched:
PKG=SUNWstaroffice-it-res
Original package not installed.
Package not patched:
PKG=SUNWstaroffice-nl
Original package not installed.
Package not patched:
PKG=SUNWstaroffice-nl-help
Original package not installed.
Package not patched:
PKG=SUNWstaroffice-nl-res
Original package not installed.
Package not patched:
PKG=SUNWstaroffice-onlineupdate
Original package not installed.
Package not patched:
PKG=SUNWstaroffice-pl
Original package not installed.
Package not patched:
PKG=SUNWstaroffice-pl-help
Original package not installed.
Package not patched:
PKG=SUNWstaroffice-pl-res
Original package not installed.
Package not patched:
PKG=SUNWstaroffice-pt-BR
Original package not installed.
Package not patched:
PKG=SUNWstaroffice-pt-BR-help
Original package not installed.
Package not patched:
PKG=SUNWstaroffice-pt-BR-res
Original package not installed.
Package not patched:
PKG=SUNWstaroffice-ru
Original package not installed.
Package not patched:
PKG=SUNWstaroffice-ru-help
Original package not installed.
Package not patched:
PKG=SUNWstaroffice-ru-res
Original package not installed.
Package not patched:
PKG=SUNWstaroffice-sv
Original package not installed.
Package not patched:
PKG=SUNWstaroffice-sv-help
Original package not installed.
Package not patched:
PKG=SUNWstaroffice-sv-res
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.
/mets1/user3/wcohrs/tmp/120185-09/SUNWstaroffice-base/install/checkinstall: /mets1/user3/wcohrs/tmp/1
20185-09/SUNWstaroffice-base/install/checkinstall: cannot open
pkgadd: ERROR: checkinstall script did not complete successfully
Dryrun complete.
No changes were made to the system.
please help
regards
Wolfgang
Message was edited by:
kasimong
solved
see
http://forum.java.sun.com/thread.jspa?threadID=5066286&tstart=0

The StarOffice patches are most likely being recommended as there are one or more SUNWstaroffice packages installed on the system, but the patch installation cannot complete due to an incomplete installation of StarOffice. Check for any installed StarOffice packages and remove them if present:
# pkginfo | grep SUNWstaroffice

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

How to merge these patches EBS: R12.1 Oracle Financials Recommended Patches

Dear Experts,
Please note that we have implemented the following modules on E-Business Suit 11.5.10.2 .
SCM Modules:
1.     Inventory
2.     Purchasing
3.     Order Management
Finance Modules:
1.     General Ledger
2.     Fixed Assets
3.     Accounts Receivables
4.     Accounts Payables
5.     Cash Management
We have also upgraded our database from 9.2.0.6 to 11g R2 as per the latest metalink interoperablity notes. Currently our EBS Version on test Enviroment is 11.5.10.2 with 11g R2
please note that as per the metalink note id EBS: R12.1 Oracle Financials Recommended Patches [ID 954704.1], We are in process of analysing the patches.
Please let us know how to merge these patches and proceed with our R12.1 upgrade driver.
Please also let us know are there any steps which needs to be performed after the below steps.
Run the Accounting Health Check and resolve data issues (Note 416699.1)
Complete all Period Close Actions/Processes. Validate and account as much data as possible and make sure everything is transferred to GL.
Run your standard reconciliation and account balance reports after period close and resolve issues.
Run the Accounting Health Check again. Resolve all remaining data issues (Note 416699.1)
If upgrading to R12.0.x, apply Patch 7653100 (Note 557869.1)
If upgrading to R12.1.x, apply Patch 8773483:R12.FIN_PF.B (Note 880275.1)
Proceed with the next steps of the upgrade.
Your quick action in this regards will be highly appreciated.
Regards
Mohammed.

Mohammed,
I am not an expert although I have significant experience upgrading the database and applications from 11.5.10.2 to 12.1.1 and 12.1.3 in both test and production environments. The following are a few thoughts as you continue down the upgrade path:
Patch 8773483 will need to be installed in pre-install mode along with a number of other pre-install mode patches. If you haven't looked at the following note you will need to since it contains information you need:
Oracle Applications Release Notes, Release 12.1.1 [ID 798258.1]
Pay particular attention to the README.txt instructions for patch 9179588 since it wants you to merge other patches with it before applying.
Another note you need to be aware of, especially if you want reconcile past the 6 month window used for accrual write offs during the upgrade, is:
R12.0 and R12.1: FAQ for the SLA Upgrade: SLA Pre-Upgrade, Post-Upgrade, and Hot Patch [ID 604893.1]
Other good sources of information for financials are:
Impact of R12 Design in Procure To Pay Accounting Flow [ID 429105.1]
Projects Uptake of the TCA Architecture in Release 12 [ID 417511.1] <--- AR/TCA (HZ) table join information that is very good
Payments In Order Management In R12 [ID 1164613.1]
If you don't have XLE and ZX currently licensed in your 11.5.10.2 instance, you will need to license them so the tax conversion runs successfully.
If you have legal entity identifications that are more than 30 characters, you will want to be aware of the size limitation imposed on the column LEGAL_ENTITY_IDENTIFIER in the table XLE.XLE_ENTITY_PROFILES, The following job will fail if the combined values exceed the LEGAL_ENTITY_IDENTIFIER column length which is shortened in R12:
xleupg01.sql
There are lots of potential pitfalls in an R12 upgrade. You simply need to test, test, and test again everything you use, read the RCD's and R12 documentation as much as possible, etc ... Having said that, there are many good things about an R12 upgrade too, from both the functional and technical perspectives.
Riley

Patch 124171-01 fails to install

Patch 124171-01 fails to install on an Ultra-80 and a V210 models. I installed it manually to get the message that the "SUNWscnbase-r" package is not installed so the patch is aborted.
The Ultra-80 runs Solaris 10 release 03/2005. The V210 runs Solaris 10 01/2006. I typically load everything in the installs so this patch should not have been recommended to them.

root hypert /var/sadm/spool # smpatch analyze
124187-01 SunOS 5.10_x86: flash issue with SUNWscn-base due to broken package
Maybe the patchinfo wasn't specific enough?
root hypert /var/sadm/spool/124187-01.jar.dir/124187-01 # more patchinfo
PATCHINFOVERSION="1.0"
PATCHID=124187-01
PATCH_CORRECTS='BaseOS.SolarisCore-5.10'
PATCH_ARCH='i386'
PATCH_OS='SunOS'
PATCH_OSRELEASE='5.10'
PATCH_PROPERTIES='clientroot'
This seems to indicate all Solaris 10 systems would need this patch - but I don't know if UM uses this info when deciding which patches to recommend.

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

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[cpu0]/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>
[...at the Solaris boot prompt; enable kmdb, debugging, and single-user
so that you can remove the patch and reboot...]
boot -kds
[...wait for it to boot...]
physmax:w
:c
[...you'll see 'stop on write of'...]
physmax/X
[...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...]
physxmax/W bff80
:c
[...system will boot and go into single user mode...
now, go toss those patches...]
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>

Recommended patches on oracle 10.2.0.4 RAC database and CRS

Hi,
This week I am planning to upgrade my oracle 10.2.0.2 RAC database oracle 10.2.0.4.
Also, I want to apply if any recommended patches we can apply on 10.2.0.4 database or on CRS 10.2.0.4
I searched in metalink, but in vain i didn't get any exact patches recommended on 10.2.0.4.
If you have any patch numbers that need to be applied on oracle 10.2.0.4 RAC database, please provide me.
Thanks,
Mahi

Check out MOS Doc 756671.1 - Oracle Recommended Patches -- Oracle Database
HTH
Srini

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.

Performace problem in oracle DB after Solaris 10 recommended patching

Dear All,
We are facing some performance problems in our oracle DB qerries and reports recently. We applied Solaris 10 recommended patchset on april 24th. Our monthly report generation acitivity is now running for last 3 days i.e may 11,12,13 and application team is complaining of degraded performance. I can see that the cpu usage on the server is about 100% during the report generation , but everything else is fine. Free memory is 15gb , all mountpoints are under 80% and there is no other hardware issue as well.
Now app team is suspecting that last month patching could be the cause of the problem, because till last month they were performing this activity without having a performance degradtion.
I just need to be sure that solaris 10 recommended patches are not causing this issue. Any of you ever faced such an issue after patch installation ?
The server is V490 with 8 cpu / 32gb RAM. Any hints will be appreciated ?
Thanks in Advance.
Edited by: 1005720 on May 13, 2013 9:58 PM

I did not archive the o/p of prstat but have o/p of top with me
195 processes: 175 sleeping, 13 running, 1 zombie, 6 on cpu
CPU states: 0.0% idle, 78.4% user, 21.6% kernel, 0.0% iowait, 0.0% swap
Memory: 32G phys mem, 16G free mem, 70G total swap, 70G free swap
PID USERNAME LWP PRI NICE SIZE RES STATE TIME CPU COMMAND
18964 oracle 39 41 0 6389M 5488M cpu/1 2:50 15.04% oracle
19638 oracle 26 59 0 6390M 5490M run 0:27 8.58% oracle
19648 oracle 36 31 0 6418M 5516M run 0:21 5.92% oracle
19023 oracle 34 30 0 6398M 5498M run 0:37 5.88% oracle
7229 oracle 38 30 0 6427M 5514M run 234:24 5.69% oracle
6912 oracle 45 31 0 6395M 5483M cpu/16 218:04 5.31% oracle
7216 oracle 28 31 0 6430M 5517M run 232:40 5.04% oracle
19644 oracle 35 40 0 6390M 5490M cpu/17 0:24 4.74% oracle
6897 oracle 112 30 0 6392M 5479M run 236:38 4.52% oracle
3813 oracle 106 31 0 6428M 5528M run 100:11 4.43% oracle
18970 oracle 234 31 0 6398M 5499M cpu/0 1:45 4.15% oracle
19749 oracle 1 32 0 6386M 5486M run 0:00 4.05% oracle
19646 oracle 23 31 0 6405M 5505M run 0:25 3.61% oracle
18972 oracle 11 32 0 6398M 5497M run 2:18 3.61% oracle
7220 oracle 258 32 0 6468M 5555M cpu/3 113:13 3.56% oracle
During the entire issue there was no %iowait.

How to apply 3 RPC (Recommended Patch Collection)

Dear,
I am fresher in the field of Oracle EBS R12. As per recurrence of the create accounting issues on PAYABLE module: the Metalink representative recommends to apply the following patch collection:
We strongly recommends to apply the following 3 RPC (Recommended Patch Collection):
Patch 13563472:R12.AP.B
Patch 13563481:R12.AP.B
Patch 13563489:R12.AP.B
So I want to know how to apply these patches, one by one or collectively. I shall be very thankful if you share all steps to apply these patches with me.
Stay blessed.
Best Regards,
Ahmed.

I have corrected some of you steps and made below:-
1. Stop applicaiton services.
2. Stop Database Services or bring database in hot backup mode.
3. Take backup(both apps and DB).
4) Start Database or bring database out of backup mode.
6) Bring application in maintenance mode.
7) Extract the patch into a folder.
8)Follow readme document of the patch.
9) use adpatch utility to apply the patch.
10) disable maintenance mode
11) start application services and test the application functionality.
I need your help at step # 5. In this scenario, will i take cold backup of data files only or whole backup of DB Tier & Application Tier. Whole backup of DB and apps Tier.
And Please also tell me if i want to reverse the patch operation, what do i need ? only restore the data files. Please tell me step by step. I shall be very thank full to you. Your posts are always helpful for us.restore complete db and apps tier.
If you have taken cold backup prior to patching activity then to undo a patch use below steps:-
1)Stop apps and db tier.
2)Clear all apps and db mount points.
3) Restore backup taken prior to patching activity.
4) Start database and listener.
5) Start application.
If you have taken hot backup then after step 3 you need to recover the database and rest all steps remain same.
Also check below metalink note:-
How to uninstall backout rollback an Oracle Applications 11i or R12 Patch [ID 343987.1]
Thanks,
JD
Thanks,
JD

Recommended Patch 118918-24 fails

Similar Messages

Maybe you are looking for