Applying individual patches to a Live Upgrade Environment

Hi all
Is it possible to apply individual patches to a Live Upgrade Environment? More specifically, is it possible to apply a kernel patch to the LUE?
I was thinking that the command would look like this:
patchadd -R /alt_env_root /location/144500-19
In the README I don't find anything for patching a LUE and only mention of installing it in single user mode or when the system is close to totally idle.
Dean

yes u can apply the individul patches anad kernel patches in the lu enviornment
for that first u need to create ABE
luupgrade -n mytestBE -t -s /patchesfolder 166981-17
you can refer this below link
http://www.oracle.com/technetwork/server-storage/solaris10/solaris-live-upgrade-wp-167900.pdf
http://www.oracle.com/technetwork/systems/articles/lu-patch-jsp-139117.html

Similar Messages

Patching broken in Live Upgrade from Solaris 9 to Solaris 10

I'm using Live Upgrade to upgrade a Solaris 9 system to Solaris 10. I installed the
LU packages from Solaris 10 11/06 plus the latest Live Upgrade patches. Everything
went fine until I attempted to use `luupgrade -t' to apply Recommended and Security patches to the
Solaris 10 boot environment. It gave me this error:
ERROR: The boot environment <sol10env> supports non-global zones.The current boot environment does not support non-global zones. Releases prior to Solaris 10 cannot be used to maintain Solaris 10 and later releases that include support for non-global zones. You may only execute the specified operation on a system with Solaris 10 (or later) installed.
Can anyone tell me if there is a way to get the Recommended patches installed without having to first activate and boot up to 10?
Thanks in advance.
'chele

Tried it - got kind of excited for a couple of seconds......but then it failed:
# ./install_cluster -R /.alt.sol10env
Patch cluster install script for Solaris 10 Recommended Patch Cluster
WARNING SYSTEMS WITH LIMITED DISK SPACE SHOULD NOT INSTALL PATCHES:
.(standard stuff about space)
in only partially loaded patches. Check and be sure adequate disk space
is available before continuing.
Are you ready to continue with install? [y/n]: y
Determining if sufficient save space exists...
Sufficient save space exists, continuing...
ERROR: OS is not valid for this cluster. Exiting.

How to delete file systems from a Live Upgrade environment

How to delete non-critical file systems from a Live Upgrade boot environment?
Here is the situation.
I have a Sol 10 upd 3 machine with 3 disks which I intend to upgrade to Sol 10 upd 6.
Current layout
Disk 0: 16 GB:
/dev/dsk/c0t0d0s0 1.9G /
/dev/dsk/c0t0d0s1 692M /usr/openwin
/dev/dsk/c0t0d0s3 7.7G /var
/dev/dsk/c0t0d0s4 3.9G swap
/dev/dsk/c0t0d0s5 2.5G /tmp
Disk 1: 16 GB:
/dev/dsk/c0t1d0s0 7.7G /usr
/dev/dsk/c0t1d0s1 1.8G /opt
/dev/dsk/c0t1d0s3 3.2G /data1
/dev/dsk/c0t1d0s4 3.9G /data2
Disk 2: 33 GB:
/dev/dsk/c0t2d0s0 33G /data3
The data file systems are not in use right now, and I was thinking of
partitioning the data3 into 2 or 3 file systems and then creating
a new BE.
However, the system already has a BE (named s10) and that BE lists
all of the filesystems, incl the data ones.
# lufslist -n 's10'
boot environment name: s10
This boot environment is currently active.
This boot environment will be active on next system boot.
Filesystem fstype device size Mounted on Mount Options
/dev/dsk/c0t0d0s4 swap 4201703424 - -
/dev/dsk/c0t0d0s0 ufs 2098059264 / -
/dev/dsk/c0t1d0s0 ufs 8390375424 /usr -
/dev/dsk/c0t0d0s3 ufs 8390375424 /var -
/dev/dsk/c0t1d0s3 ufs 3505453056 /data1 -
/dev/dsk/c0t1d0s1 ufs 1997531136 /opt -
/dev/dsk/c0t1d0s4 ufs 4294785024 /data2 -
/dev/dsk/c0t2d0s0 ufs 36507484160 /data3 -
/dev/dsk/c0t0d0s5 ufs 2727290880 /tmp -
/dev/dsk/c0t0d0s1 ufs 770715648 /usr/openwin -
I browsed the Solaris 10 Installation Guide and the man pages
for the lu commands, but can not find how to remove the data
file systems from the BE.
How do I do a live upgrade on this system?
Thanks for your help.

Thanks for the tips.
I commented out the entries in /etc/vfstab, also had to remove the files /etc/lutab and /etc/lu/ICF.1
and then could create the Boot Environment from scratch.
I was also able to create another boot environment and copied into it,
but now I'm facing a different problem, error when trying to upgrade.
# lustatus
Boot Environment           Is       Active Active    Can    Copy
Name                       Complete Now    On Reboot Delete Status
s10                        yes      yes    yes       no     -
s10u6                      yes      no     no        yes    -        Now, I have the Solaris 10 Update 6 DVD image on another machine
which shares out the directory. I mounted it on this machine,
did a lofiadm and mounted that at /cdrom.
# ls -CF /cdrom /cdrom/boot /cdrom/platform
/cdrom:
Copyright                     boot/
JDS-THIRDPARTYLICENSEREADME   installer*
License/                      platform/
Solaris_10/
/cdrom/boot:
hsfs.bootblock   sparc.miniroot
/cdrom/platform:
sun4u/   sun4us/ sun4v/Now I did luupgrade and I get this error:
# luupgrade -u -n s10u6 -s /cdrom
ERROR: The media miniroot archive does not exist </cdrom/boot/x86.miniroot>.
ERROR: Cannot unmount miniroot at </cdrom/Solaris_10/Tools/Boot>.I find it strange that this sparc machine is complaining about x86.miniroot.
BTW, the machine on which the DVD image is happens to be x86 running Sol 10.
I thought that wouldn't matter, as it is just NFS sharing a directory which has a DVD image.
What am I doing wrong?
Thanks.

Unable to boot the sytem after applying kernel patch 118844-27

We have an hp ProLiant DL380 Storage server connected to HP StorageWorks Moduler Smart Array 30 via SCSI. Solaris 03/05 was installed previously on this system with kernel 118844-20. When I queried and installed all required patches with 'smpatch add -i .. ' command, all patches applied and the system is rebooted. After reboot, the system kept restarting. I followed the instructions on Sun Alert document 102087, and installed grub using 01/06 1st CDROM. It installed successfully, but problem persisted. The systems started booting, but before printing 'Configuring devices' the system rebooted again. Providing -v option to the kernel, it lastly printed a PCI device id (/pci@....) and after 2-3 seconds rebooted again.
Finally I had to reinstall the solaris (this time 01/06). The disk was accessible after booting with CD ROM, and I was able to get cylinder numbers of disk, and I installed the new system to the root partition of the other live upgrade environment. The boot disk was partitioned under linux, it was three partitions, Solaris2 (50GB),Solaris(4GB),Linux(18GB). Installation medium told that the fdisk partition was invalid, and i repartitioned the whole disk again.
System up and running Solaris 10 01/06 now, but the strange thing is that, previously hard disk (both boot disk and disks on array) locations were identified as '/dev/rdsk/c0tx' but now, the system sees that hard disks at '/dev/c1tx' and CDROM at '/dev/c0t0'.
Now I want to ask tow questions:
* Could this disk number change made the system unbootable previously?
* May I safely apply patch 118844-28 to the system
-Thanks

Here's a similar topic https://bbs.archlinux.org/viewtopic.php?pid=536210 also if that doesn't work you should install vesa as it also says it's not found in your log.

RFE: smpatch for Live Upgrade boot environments

We use smpatch extensively, along with a local patch server, to keep our Solaris servers
and workstations up to date on patches. I'm relatively satisfied with this facility.
I'd like to use smpatch to apply patches to a Live Upgrade boot environment, but it
doesn't offer that option. All I really need to do is to point it at an alternate root to do
the analysis and patch download. Live Upgrade already has the ability to apply patches
from a local directory. I've had to turn to the competition, pca, to do the analysis and
download.
Please request that this ability be added to smpatch.

Unfortunately man pages are not usually updated after an initial release. However there is a change request 6481979 to add it to the man pages. The option is now present in the smpatch help when no parameters are provided to the command only as "-b boot-env". As an example;
$ smpatch add -b altboot -i 111111-11
The relevent change requests were 6366823 for Update Connection and 4974240 historically for smpatch. As realisation detection used in an analysis may depend on active software or drivers to extract data this cannot be statically extracted from a system image so a correct analysis cannot be done which appears to be why only add, remove and update were given the boot environment option.

Which patch to apply when live upgrading to a new OS

Hello Guys,
when you use live upgrade to upgrade to a new OS level , which patches do you apply before performing the upgrade? I used prerequired patches from 10REC when performing a live upgrade patching . Do you use these same prerequired patches when upgrading to a NEW OS LEVEL?
Your response will be truely appreciated.
Thanks

Hi.
I hope it's help:
http://docs.oracle.com/cd/E26505_01/html/E28038/preconfig-17.html#luplanning-7
Ensure that you have the most recently updated patch list by consulting http://support.oracle.com (My Oracle Support). Search for the knowledge document 1004881.1 - Live Upgrade Software Patch Requirements (formerly 206844) on My Oracle Support.
The patches listed in knowledge document 1004881.1 - Live Upgrade Software Patch Requirements (formerly 206844) on My Oracle Support are subject to change at any time. These patches potentially fix defects in Live Upgrade, as well as fix defects in components that Live Upgrade depends on. If you experience any difficulties with Live Upgrade, please check and make sure that you have the latest Live Upgrade patches installed.
If you are running the Solaris 8 or Solaris 9 OS, you might not be able to run the Live Upgrade installer. These releases do not contain the set of patches needed to run the Java 2 runtime environment. You must have the recommended patch cluster for the Java 2 runtime environment recommended to run the Live Upgrade installer and install the packages. To install the Live Upgrade packages, use the pkgadd command. Or install, for the Java 2 runtime environment, the recommended patch cluster. The patch cluster is available on http://support.oracle.com (My Oracle Support).
For instructions about installing the Live Upgrade software, see Installing Live Upgrade.
Required patches available via MOS ( My Oracle Support: http://support.oracle.com).
But for access to this site you must have active service contract.
Regards.

Looking for information on best practices using Live Upgrade to patch LDOMs

This is in Solaris 10. Relatively new to the style of patching... I have a T5240 with 4 LDOMS. A control LDOM and three clients. I have some fundamental questions I'd like help with..
Namely:
#1. The Client LDOMS have zones running in them. Do I need to init 0 the zone or can I just +zoneadm zone halt+ them regardless of state? I.E. if it's running a database will halting the zone essentially snapshot it or will it attempt to shut it down. Is this even a nessessary step.
#2. What is the reccommended reboot order for the LDOMs? do I need to init 0 the client ldoms and the reboot the control ldom or can I leave the client LDOM's running and just reboot the control and then reboot the clients after the control comes up?
#3. Oracle. it's running in several of the zones on the client LDOM's what considerations need to be made for this?
I am sure other things will come up during the conversation but I have been looking for an hour on Oracle's site for this and the only thing I can find is old Sun Docs with broken links.
Thanks for any help you can provide,
pipelineadmin+*

Before you use live upgrade, or any other patching technique for Solaris, please be sure to read http://docs.oracle.com/cd/E23823_01/html/E23801/index.html which includes information on upgrading systems with non-global zones. Also, go to support.oracle.com and read Oracle Solaris Live Upgrade Information Center [ID 1364140.1]. These really are MANDATORY READING.
For the individual questions:
#1. During the actual maintenance you don't have to do anything to the zone - just operate it as normal. That's the purpose of the "live" in "live upgrade" - you're applying patches on a live, running system under normal operations. When you are finisihed with that process you can then reboot into the new "boot environment". This will become more clear after reading the above documents. Do as you normally would do before taking a planned outage: shut the databases down using the database commands for a graceful shutdown. A zone halt will abruptly stop the zone and is not a good idea for a database. Alternatively, if you can take application outages, you could (smoothly) shutdown the applications and then their domains, detach the zones (zoneadm detach) and then do a live upgrade. Some people like that because it makes things faster. After the live upgrade you would reboot and then zoneadm attach the zones again. The fact that the Solaris instance is running within a logical domain really is mostly besides the point with respect to this process.
As you can see, there are a LOT of options and choices here, so it's important to read the doc. I ***strongly*** recommend you practice on a test domain so you can get used to the procedure. That's one of the benefits of virtualization: you can easily set up test environments so you cn test out procedures. Do it! :-)
#2 First, note that you can update the domains individually at separate times, just as if they were separate physical machines. So, you could update the guest domains one week (all at once or one at a time), reboot them into the new Solaris 10 software level, and then a few weeks later (or whenever) update the control domain.
If you had set up your T5240 in a split-bus configuration with an alternate I/O domain providing virtual I/O for the guests, you would be able to upgrade the extra I/O domain and the control domain one at a time in a rolling upgrade - without ever having to reboot the guests. That's really powerful for providing continuous availability. Since you haven't done that, the answer is that at the point you reboot the control domain the guests will lose their I/O. They don't crash, and technically you could just have them continue until the control domain comes back up at which time the I/O devices reappear. For an important application like a database I wouldn't recommend that. Instead: shutdown the guests. then reboot the control domain, then bring the guest domains back up.
3. The fact that Oracle database is running in zones inside those domains really isn't an issue. You should study the zones administration guide to understand the operational aspects of running with zones, and make sure that the patches are compatible with the version of Oracle.
I STRONGLY recommend reading the documents mentioned at top, and setting up a test domain to practice on. It shouldn't be hard for you to find documentation. Go to www.oracle.com and hover your mouse over "Oracle Technology Network". You'll see a window with a menu of choices, one of which is "Documentation" - click on that. From there, click on System Software, and it takes you right to the links for Solaris 10 and 11.

Creating Boot Environment for Live Upgrade

Hello.
I'd like to upgrade a Sun Fire 280R system running Solaris 8 to Solaris 10 U4. I'd like to use Live Upgrade to do this. As that's going to be my first LU of a system, I've got some questions. Before I start, I'd like to mention that I have read the �Solaris 10 8/07 Installation Guide: Solaris Live Upgrade and Upgrade Planning� ([820-0178|http://docs.sun.com/app/docs/doc/820-0178]) document. Nonetheless, I'd also appreciate pointers to a more �hands-on� documentation/howto reg. live upgrade.
The system that I'd like to upgrade has these filesystems:
(winds02)askwar$ df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/md/dsk/d30 4129290 684412 3403586 17% /
/dev/md/dsk/d32 3096423 1467161 1567334 49% /usr
/dev/md/dsk/d33 2053605 432258 1559739 22% /var
swap 7205072 16 7205056 1% /var/run
/dev/dsk/c3t1d0s6 132188872 61847107 69019877 48% /u04
/dev/md/dsk/d34 18145961 5429315 12535187 31% /opt
/dev/md/dsk/d35 4129290 77214 4010784 2% /export/home
It has 2 built in harddisks, which form those metadevices. You can find the �metastat� at http://askwar.pastebin.ca/697380. I'm now planning to break the mirrors for /, /usr, /var and /opt. To do so, I'd run
metadetach d33 d23
metaclear d23
d23 is/used to be c1t1d0s4. I'd do this for d30, d32 and d34 as well. Plan is, that I'd be able to use these newly freed slices on c1t1d0 for LU. I know that I'm in trouble when c1t0d0 now dies. But that's okay, as that system isn't being used anyway right now...
Or wait, I can use lucreate to do that as well, can't I? So, instead of manually detaching the mirror, I could do:
lucreate -n s8_2_s10 -m /:/dev/md/dsk/d30:preserve,ufs \
-m /usr:/dev/md/dsk/d32:preserve,ufs \
-m /var:/dev/md/dsk/d33:preserve,ufs \
-m /opt:/dev/md/dsk/d34:preserve,ufs
Does that sound right? I'd assume, that I'd then have a new boot environment called �s8_2_s10�, which uses the contents of the old metadevices. Or would the correct command rather be:
lucreate -n s8_2_s10_v2 \
-m /:/dev/md/dsk/d0:mirror,ufs \
-m /:/dev/md/dsk/d20:detach,attach,preserve \
-m /usr:/dev/md/dsk/d2:mirror,ufs \
-m /usr:/dev/md/dsk/d22:detach,attach,preserve \
-m /var:/dev/md/dsk/d3:mirror,ufs \
-m /var:/dev/md/dsk/d23:detach,attach,preserve \
-m /opt:/dev/md/dsk/d4:mirror,ufs \
-m /opt:/dev/md/dsk/d24:detach,attach,preserve
What would be the correct way to create the new boot environment? As I said, I haven't done this before, so I'd really appreciate some help.
Thanks a lot,
Alexander Skwar

I replied to this thread: Re: lucreate and non-global zones as to not duplicate content, but for some reason it was locked. So I'll post here...The thread was locked because you were not replying to it.
You were hijacking that other person's discussion from 2012 to ask your own new post.
You have now properly asked your question and people can pay attention to you and not confuse you with that other person.

Applying NLS patches after upgrade to 12.1.3

Hi Experts,
Recently i install 12.1.1 and then upgrade it to 12.1.3.
Now i need to apply NLS patches(Canadian French and Spanish language).
On metalink i find pre-requisite of both patches and post patch are same.
The prerequisite patch for both is p8576725_12.1.0_R12_GENERIC.zip
and post patch is p6746000_R12_f.zip.
Can i apply it one by one or After applying french , i applied spanish patch ?
Can you please giude me.
Thanks
Mohammad

Hi;
Please see:
How to Add arabic language to exisitng 12.1.3
Re: How to Add arabic language to exisitng 12.1.3
Regard
Helios

Solaris 10 update 9 - live upgrade issues with ZFS

Hi
After doing a live upgrade from Solaris 10 update 8 to Solaris 10 update 9 the alternate boot environment I created is no longer bootable.
I have completed all the pre-upgrade steps like:
- Installing the latest version of live upgrade from the update 9 ISO.
- Create and test the new boot environment.
- Create a sysidcfg file used by the live upgrade that has auto_reg=disable in it.
There is also no errors while creating the boot environment or even when activating it.
Here is the error I get:
SunOS Release 5.10 Version Generic_14489-06 64-bit
Copyright (c) 1983, 2010, Oracle and/or its affiliates. All rights reserved.
NOTICE: zfs_parse_bootfs: error 22
Cannot mount root on altroot/37 fstype zfs
*panic[cpu0]/thread=fffffffffbc28040: vfs mountroot: cannot mount root*
ffffffffffbc4a8d0 genunix:main+107 ()
Skipping system dump - no dump device configured
Does anyone know how I can fix this?
Edited by: user12099270 on 02-Feb-2011 04:49

Found the culprit... *142910-17*... breaks it
System has findroot enabled GRUB
Updating GRUB menu default setting
GRUB menu default setting is unaffected
Saving existing file </boot/grub/menu.lst> in top level dataset for BE <s10x_u8wos_08a> as <mount-point>//boot/grub/menu.lst.prev.
File </etc/lu/GRUB_backup_menu> propagation successful
Successfully deleted entry from GRUB menu
Validating the contents of the media </admin/x86/Patches/10_x86_Recommended/patches>.
The media contains 204 software patches that can be added.
Mounting the BE <s10x_u8wos_08a_Jan2011>.
Adding patches to the BE <s10x_u8wos_08a_Jan2011>.
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 SUNWio-tools from directory SUNWio-tools in patch 142910-17 is not installed on the system. Changes for package SUNWio-tools will not be applied to the system.
Package SUNWzoneu from directory SUNWzoneu in patch 142910-17 is not installed on the system. Changes for package SUNWzoneu will not be applied to the system.
Package SUNWpsm-ipp from directory SUNWpsm-ipp in patch 142910-17 is not installed on the system. Changes for package SUNWpsm-ipp will not be applied to the system.
Package SUNWsshdu from directory SUNWsshdu in patch 142910-17 is not installed on the system. Changes for package SUNWsshdu will not be applied to the system.
Package SUNWsacom from directory SUNWsacom in patch 142910-17 is not installed on the system. Changes for package SUNWsacom will not be applied to the system.
Package SUNWmdbr from directory SUNWmdbr in patch 142910-17 is not installed on the system. Changes for package SUNWmdbr will not be applied to the system.
Package SUNWopenssl-commands from directory SUNWopenssl-commands in patch 142910-17 is not installed on the system. Changes for package SUNWopenssl-commands will not be applied to the system.
Package SUNWsshdr from directory SUNWsshdr in patch 142910-17 is not installed on the system. Changes for package SUNWsshdr will not be applied to the system.
Package SUNWsshcu from directory SUNWsshcu in patch 142910-17 is not installed on the system. Changes for package SUNWsshcu will not be applied to the system.
Package SUNWsshu from directory SUNWsshu in patch 142910-17 is not installed on the system. Changes for package SUNWsshu will not be applied to the system.
Package SUNWgrubS from directory SUNWgrubS in patch 142910-17 is not installed on the system. Changes for package SUNWgrubS will not be applied to the system.
Package SUNWzoner from directory SUNWzoner in patch 142910-17 is not installed on the system. Changes for package SUNWzoner will not be applied to the system.
Package SUNWmdb from directory SUNWmdb in patch 142910-17 is not installed on the system. Changes for package SUNWmdb will not be applied to the system.
Package SUNWpool from directory SUNWpool in patch 142910-17 is not installed on the system. Changes for package SUNWpool will not be applied to the system.
Package SUNWudfr from directory SUNWudfr in patch 142910-17 is not installed on the system. Changes for package SUNWudfr will not be applied to the system.
Package SUNWxcu4 from directory SUNWxcu4 in patch 142910-17 is not installed on the system. Changes for package SUNWxcu4 will not be applied to the system.
Package SUNWarc from directory SUNWarc in patch 142910-17 is not installed on the system. Changes for package SUNWarc will not be applied to the system.
Package SUNWtftp from directory SUNWtftp in patch 142910-17 is not installed on the system. Changes for package SUNWtftp will not be applied to the system.
Package SUNWaccu from directory SUNWaccu in patch 142910-17 is not installed on the system. Changes for package SUNWaccu will not be applied to the system.
Package SUNWppm from directory SUNWppm in patch 142910-17 is not installed on the system. Changes for package SUNWppm will not be applied to the system.
Package SUNWtoo from directory SUNWtoo in patch 142910-17 is not installed on the system. Changes for package SUNWtoo will not be applied to the system.
Package SUNWcpc from directory SUNWcpc.i in patch 142910-17 is not installed on the system. Changes for package SUNWcpc will not be applied to the system.
Package SUNWftdur from directory SUNWftdur in patch 142910-17 is not installed on the system. Changes for package SUNWftdur will not be applied to the system.
Package SUNWypr from directory SUNWypr in patch 142910-17 is not installed on the system. Changes for package SUNWypr will not be applied to the system.
Package SUNWlxr from directory SUNWlxr in patch 142910-17 is not installed on the system. Changes for package SUNWlxr will not be applied to the system.
Package SUNWdcar from directory SUNWdcar in patch 142910-17 is not installed on the system. Changes for package SUNWdcar will not be applied to the system.
Package SUNWnfssu from directory SUNWnfssu in patch 142910-17 is not installed on the system. Changes for package SUNWnfssu will not be applied to the system.
Package SUNWpcmem from directory SUNWpcmem in patch 142910-17 is not installed on the system. Changes for package SUNWpcmem will not be applied to the system.
Package SUNWlxu from directory SUNWlxu in patch 142910-17 is not installed on the system. Changes for package SUNWlxu will not be applied to the system.
Package SUNWxcu6 from directory SUNWxcu6 in patch 142910-17 is not installed on the system. Changes for package SUNWxcu6 will not be applied to the system.
Package SUNWpcmci from directory SUNWpcmci in patch 142910-17 is not installed on the system. Changes for package SUNWpcmci will not be applied to the system.
Package SUNWarcr from directory SUNWarcr in patch 142910-17 is not installed on the system. Changes for package SUNWarcr will not be applied to the system.
Package SUNWscpu from directory SUNWscpu in patch 142910-17 is not installed on the system. Changes for package SUNWscpu will not be applied to the system.
Package SUNWcpcu from directory SUNWcpcu in patch 142910-17 is not installed on the system. Changes for package SUNWcpcu will not be applied to the system.
Package SUNWopenssl-include from directory SUNWopenssl-include in patch 142910-17 is not installed on the system. Changes for package SUNWopenssl-include will not be applied to the system.
Package SUNWdtrp from directory SUNWdtrp in patch 142910-17 is not installed on the system. Changes for package SUNWdtrp will not be applied to the system.
Package SUNWhermon from directory SUNWhermon in patch 142910-17 is not installed on the system. Changes for package SUNWhermon will not be applied to the system.
Package SUNWpsm-lpd from directory SUNWpsm-lpd in patch 142910-17 is not installed on the system. Changes for package SUNWpsm-lpd will not be applied to the system.
Package SUNWdtrc from directory SUNWdtrc in patch 142910-17 is not installed on the system. Changes for package SUNWdtrc will not be applied to the system.
Package SUNWhea from directory SUNWhea in patch 142910-17 is not installed on the system. Changes for package SUNWhea will not be applied to the system.
Package SUNW1394 from directory SUNW1394 in patch 142910-17 is not installed on the system. Changes for package SUNW1394 will not be applied to the system.
Package SUNWrds from directory SUNWrds in patch 142910-17 is not installed on the system. Changes for package SUNWrds will not be applied to the system.
Package SUNWnfsskr from directory SUNWnfsskr in patch 142910-17 is not installed on the system. Changes for package SUNWnfsskr will not be applied to the system.
Package SUNWudf from directory SUNWudf in patch 142910-17 is not installed on the system. Changes for package SUNWudf will not be applied to the system.
Package SUNWixgb from directory SUNWixgb in patch 142910-17 is not installed on the system. Changes for package SUNWixgb will not be applied to the system.
Checking patches that you specified for installation.
Done!
Approved patches will be installed in this order:
142910-17
Checking installed patches...
Executing prepatch script...
Installing patch packages...
Patch 142910-17 has been successfully installed.
See /a/var/sadm/patch/142910-17/log for details
Executing postpatch script...
Creating GRUB menu in /a
Installing grub on /dev/rdsk/c2t0d0s0
stage1 written to partition 0 sector 0 (abs 16065)
stage2 written to partition 0, 273 sectors starting at 50 (abs 16115)
Patch packages installed:
BRCMbnx
SUNWaac
SUNWahci
SUNWamd8111s
SUNWcakr
SUNWckr
SUNWcry
SUNWcryr
SUNWcsd
SUNWcsl
SUNWcslr
SUNWcsr
SUNWcsu
SUNWesu
SUNWfmd
SUNWfmdr
SUNWgrub
SUNWhxge
SUNWib
SUNWigb
SUNWintgige
SUNWipoib
SUNWixgbe
SUNWmdr
SUNWmegasas
SUNWmptsas
SUNWmrsas
SUNWmv88sx
SUNWnfsckr
SUNWnfscr
SUNWnfscu
SUNWnge
SUNWnisu
SUNWntxn
SUNWnv-sata
SUNWnxge
SUNWopenssl-libraries
SUNWos86r
SUNWpapi
SUNWpcu
SUNWpiclu
SUNWpsdcr
SUNWpsdir
SUNWpsu
SUNWrge
SUNWrpcib
SUNWrsgk
SUNWses
SUNWsmapi
SUNWsndmr
SUNWsndmu
SUNWtavor
SUNWudapltu
SUNWusb
SUNWxge
SUNWxvmpv
SUNWzfskr
SUNWzfsr
SUNWzfsu
PBE GRUB has no capability information.
PBE GRUB has no versioning information.
ABE GRUB is newer than PBE GRUB. Updating GRUB.
GRUB update was successfull.
Unmounting the BE <s10x_u8wos_08a_Jan2011>.
The patch add to the BE <s10x_u8wos_08a_Jan2011> completed.
Still need to know how to resolve it though...

Solaris 9 live upgrade to solaris 10 segmentation fault

pre-upgrade work:
apply patch doc 72099
upgrade live upgrade to solaris 10.
lucreate-m /:/dev/dsk/c0t1d0s0:ufs -m /var:/dev/dsk/c0t1d0s1:ufs -m /opt:/dev/dsk/c0t1d0s3:ufs -n sol10
it works well
oot Environment Is Active Active Can Copy
Name Complete Now On Reboot Delete Status
sol9 yes yes yes no -
sol10 yes no no yes -
But luupgrade -u -n sol10 -s /sol11
Validating the contents of the media </sol11>.
The media is a standard Solaris media.
The media contains an operating system upgrade image.
The media contains <Solaris> version <11>.
Constructing upgrade profile to use.
Locating the operating system upgrade program.
Checking for existence of previously scheduled Live Upgrade requests.
Creating upgrade profile for BE <sol10>.
Determining packages to install or upgrade for BE <sol10>.
Performing the operating system upgrade of the BE <sol10>.
CAUTION: Interrupting this process may leave the boot environment unstable
or unbootable.
/usr/sbin/luupgrade[677]: 6549 Segmentation Fault(coredump)
ERROR: Installation of the packages from this media of the media failed; pfinstall returned these diagnostics:
The Solaris upgrade of the boot environment <sol10> failed.

I would break your mirror and do a liveupgrade on the available mirror. Then boot that disk.

DB upgrade during a Solaris upgrade using live upgrade feature

Hello,
Here is the scenario. We are currently upgrading our OS from Solaris 9 to Solaris 10. And there is also a major database upgrade involved too. To help mitigate downtime, the Solaris Live Upgrade feature is being used by the SA's. The DB to be upgraded is currently at 9i and the proposed upgrade end state is at 10.2.0.3.
Does anyone know if it is possible to do at least part of the database upgrade in the alternate boot environment created during the live upgrade process? So lets say that I am able to get the database partly upgraded to 10.2.0.1. Then, I want to run the patch set for 10.2.0.3 in the alternate boot environment and do the upgrade of the instance there too so that when the alternate boot environment is booted to the primary boot environment, I can, in effect, just start up the database.
That's sort of a high level simplified version of what I think may be possible.
Does anyone have any recommendations? We don't have any other high availability solutions currently in place so options such as using data guard do not apply.
Thanks in advance!

Hi magNorth,
I'm not a Solaris expert but I'd always recommend not to do both steps (OS upgrade and database upgrade) at the same time. I've seen to many live scenarios where either the one or the other has caused issues - and it's fairly tough for all three parties (You as the customer, Sun Support, Oracle Support) to find out the end what was/is causing the issues.
So my recommendation would be:
1) Do your Solaris upgrade from 9 to 10 and check for the most recent Solaris patches - once this has been finished and run for one or two weeks successfully in production then go to step 2
2) Do your database upgrade - I would suggest not going to 10.2.0.3 but directly to 10.2.0.4 because 10.2.0.4 has ~2000 bug fixes plus the security fixes from April2008 - but that's your decision. If 10.2.0.3 is a must then at least check Note:401435.1 for known issues and alert in 10.2.0.3 and for both cases the Upgrade Companion: Note:466181.1
Kind regards
Mike

Live Upgrade on Solaris 11

Following my posts on LU on Solaris 10, I now need to do the same on Solaris 11.2. The two machines are brand new - not being used in anger.
I saw the useful blog https://blogs.oracle.com/oem/entry/using_ops_center_to_update
One of our machines has the following:
beadm list
BE                 Active Mountpoint Space Policy Created
solaris            -      -          12.99M static 2014-06-21 05:39
solaris-1          NR     /          25.76G static 2014-09-10 12:00
solaris-1-backup-1 -      -          323.0K static 2014-09-29 11:45
solaris-1-backup-2 -      -          172.0K static 2014-11-12 12:26
When asked, the person who looked after the machine, he was not sure how these were created. I would like to know how do I ensure that the two boot environment are the same and if that is the case if one can be deleted. Whether the backups are required and if they are auto-generated. Essentially, I am a total newbie on Live Upgrade, but I see as the only way to apply patches and other packages.
Regards
SC

Hi,
please note that Live Upgrade is obsolete and isn't used on Solaris 11 and above. Solaris 11
uses pkg(1) and beadm(1M) to manage boot environments.
The output from beadm list shows the currently existing boot environments. Those environments
are created by pkg(1) when updating the system or in certain situations when destructive package
operations take place (the "-backup" environments).
Please see
Updating to Oracle Solaris 11.2
for more information on upgrading Solaris.
In your example output the solaris boot environment is most likely the result of an
initial installation. Then someone later updated the environment resulting in a new
environment solaris-1 (which is also the current boot environment). Some pkg
operations then caused some backup boot environments to be created. This is
done to make sure that a fall-back exists should there be a problem with the newly
installed packages. If you don't need to go back to that stage you can also remove them.
It is recommended to always keep a known-good boot environment around just in case.
If you are happy with the current one you can ask beadm to create such an environment
like this:
# beadm create my-known-good-be
Please note: When using the pkg command to update the system you can
also specify a custom name for the new boot environment, e.g.
# pkg update --be-name=s11.2
would name the new environment s11.2 instead of some generic name like "solaris-X".
Regards,
Ronald

Error in applying the patch to OBIEE 11.1.1.6.8

When I try to apply the opatch apply command,   below is the error I am getting. I am not able to find the resolution for this. I am not understanding the problem by looking at this.
optach failed with error code 1
C:\Middleware\Oracle_BI1\16094198>opatch apply
Exception in thread "main" java.lang.NoClassDefFoundError: Files\Java\jdk1/7/0_4
5\lib;;C:\MIDDLE~1\ORACLE~1/modules/oracle/jrf_11/1/1/jrf-wlstman/jar;C:\MIDDLE~
1\ORACLE~1/modules/oracle/jrf_11/1/1/jrf-wlstman/jar
Caused by: java.lang.ClassNotFoundException: Files\Java\jdk1.7.0_45\lib;;C:\MIDD
LE~1\ORACLE~1.modules.oracle.jrf_11.1.1.jrf-wlstman.jar;C:\MIDDLE~1\ORACLE~1.mod
ules.oracle.jrf_11.1.1.jrf-wlstman.jar
        at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
Could not find the main class: Files\Java\jdk1.7.0_45\lib;;C:\MIDDLE~1\ORACLE~1/
modules/oracle.jrf_11.1.1/jrf-wlstman.jar;C:\MIDDLE~1\ORACLE~1/modules/oracle.jr
f_11.1.1/jrf-wlstman.jar. Program will exit.
I have installed OBIEE 11.1.1.6.0 version on windows 64 bit machine and later on I tried to apply the patch to upgrade it to 11.1.1.6.8 . Once I received above error , I thought of cross checking the PATH & Java_Home environment variables from my machine and below are snapshots of them.
Java Home : C:\Program Files\Java\jdk1.7.0_45\bin
Path: C:\oraclexe\app\oracle\product\11.2.0\server\bin;C:\Program Files (x86)\RSA SecurID Token Common;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Intel\Services\IPT\;C:\Middleware\Oracle_BI1\products\Essbase\EssbaseServer\bin;C:\Middleware\Oracle_BI1\bin;C:\Middleware\Oracle_BI1\opmn\bin;C:\Middleware\Oracle_BI1\opmn\lib;C:\Middleware\Oracle_BI1\perl\bin;C:\Program Files\Java\jdk1.7.0_45\bin
below are the commands executed in the first step before applying opatch apply on 16094198
set ORACLE_HOME=C:\Middleware\Oracle_BI1
set PATH=%ORACLE_HOME%\bin;%PATH%
set JAVA_HOME=%ORACLE_HOME%\jdk
set PATH=%JAVA_HOME%\bin;%PATH%
set PATH=%ORACLE_HOME%\OPatch;%PATH%
Any inputs on how to resolve this opatch problem will be greatly appreciated. Please let us know if I have to make any change in the environmental variables or in these set commands stated above.
Thanks in advance.

Heelo Srini,
I have updated my JAVA_HOME system variable in environmental variables section as stated below
User variables:
JAVA_HOME : C:\Program Files\Java\jdk1.7.0_45
PATH : %JAVA_HOME%\bin
System variables:
ClassPath: C:\Program Files\Java\jdk1.7.0_45\lib;
Path: C:\oraclexe\app\oracle\product\11.2.0\server\bin;C:\Program Files (x86)\RSA SecurID Token Common;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Intel\Services\IPT\;C:\Middleware\Oracle_BI1\products\Essbase\EssbaseServer\bin;C:\Middleware\Oracle_BI1\bin;C:\Middleware\Oracle_BI1\opmn\bin;C:\Middleware\Oracle_BI1\opmn\lib;C:\Middleware\Oracle_BI1\perl\bin;C:\Program Files\Java\jdk1.7.0_45\bin
Later I tried to apply the patch but I got the below error
C:\Middleware\Oracle_BI1\16094198>opatch apply
Exception in thread "main" java.lang.NoClassDefFoundError: Files\Java\jdk1/7/0_4
5\lib;;C:\MIDDLE~1\ORACLE~1/modules/oracle/jrf_11/1/1/jrf-wlstman/jar;C:\MIDDLE~
1\ORACLE~1/modules/oracle/jrf_11/1/1/jrf-wlstman/jar
Caused by: java.lang.ClassNotFoundException: Files\Java\jdk1.7.0_45\lib;;C:\MIDD
LE~1\ORACLE~1.modules.oracle.jrf_11.1.1.jrf-wlstman.jar;C:\MIDDLE~1\ORACLE~1.mod
ules.oracle.jrf_11.1.1.jrf-wlstman.jar
        at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
Could not find the main class: Files\Java\jdk1.7.0_45\lib;;C:\MIDDLE~1\ORACLE~1/
modules/oracle.jrf_11.1.1/jrf-wlstman.jar;C:\MIDDLE~1\ORACLE~1/modules/oracle.jr
f_11.1.1/jrf-wlstman.jar. Program will exit.
OPatch failed with error code = 1
Please provide any inputs.
Thanks & regards,
karthik Vecham

Sparse zones live upgrade

Hi
I have problem with live upgrade on solaris 10 9/10 to 8/11 on sparse zone.
The installation on global zone is good but sparse zone cannnot boot because zonepath changed.
bash-3.2# zoneadm list -cv
ID NAME STATUS PATH BRAND IP
0 global running / native shared
- pbspfox1 installed /zoneprod/pbspfox1-s10u10-baseline native excl
the initial path is /zoneprod/pbspfox1
#zfs list
zoneprod/pbspfox1@s10u10-baseline 22.4M - 2.18G -
zoneprod/pbspfox1-s10u10-baseline
# luactivate zoneprod/pbspfox1@s10u10-baseline
ERROR: The boot environment Name <zoneprod/pbspfox1@s10u10-baseline> is too long - a BE name may contain no more than 30 characters.
ERROR: Unable to activate boot environment <zoneprod/pbspfox1@s10u10-baseline>.
how to upgrade pbspfox1?
Please help
Walter

I'm not exactly sure what happened here but the zone name doesn't change. If the zone patch is wrong, I'd try using zonecfg to change the zone path to the proper value and then boot the zone normally.
zonecfg -z pbspfox1
set zonepath=/zone/pbspfox1 (or whatever is the proper path)
verify
commit
exit
zoneadm -z pbspfox1 boot
If the zone didn't get properly updated, you might be able to update it by detaching the zone:
zoneadm -z pbspfox1 detach
and doing an update reattach
zoneadm -z pbspfox1 attach -u
Disclaimer: All of the above was done from memory without testing, I may have gotten some things wrong.
Hopefully this will help. I've had similar issues in the past but I'm not sure I've had exactly the same problem so I can't tell for sure whether this will help you or not. It is what I'd try. Of course, try to avoid getting yourself into a position where you can't back something out if necessary. This kind of thing can be messy and may require more than one try. If a remember correctly there were some issues with the live upgrade software as shipped with Solaris 10 8/11. I'd get it patched up to current levels ASAP to avoid additional issues.

Applying individual patches to a Live Upgrade Environment

Similar Messages

Maybe you are looking for