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.

Similar Messages

Live Upgrade from 8 to 10 keeping Oracle install

Hi everyone,
I'm trying to figure out how to do a Live Upgrade from Solaris 8 (SPARC) to 10 and still keep my Oracle available after the reboot.
Since all of the Oracle datafiles are on /un or /opt/oracle I figure I can just create a new BE for /, /etc and /var. From there I'd just need to edit /etc/vfstab, /etc/init.d/ (for db startups), copy over /var/opt/oracle/, mount /opt/oracle.
Does that sound right? Has anyone done this?
On a side note, I'm still trying to figure out Live Update. My system is configed with RAID 1 under Solstice (metatool). I'm concerened about being able to access the MetaDB once the BE switch goes through. Should I set up a new mirror for the new BE prior to running LU? Or should I configure the mirror for the new BE once the switchover has gone through?

Hello dfkoch,
To upgrade from ColdfFusion 8/ColdfFusion 9 to ColdfFusion 10, please download the setup for ColdfFusion 10 from http://www.adobe.com/support/coldfusion/downloads.html#cf10productdownloads and install the same with the serial number.
The upgrade price can be checked at www.adobe.com or alternatively you can call our sales team.
Hope this helps.
Regards,
Anit Kumar

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

Live upgrade from solaris 8 to 10

how do i upgrade from solaris 8 to 10 using live upgrade on a sun netra t1 machine?

THere is a good intro to LU at
http://www.sun.com/bigadmin/collections/installation.html
beyond that, see docs.sun.com

Sun Live Upgrade with local zones Solaris 10

I have M800 server running global root (/) fs on local disk and running 6 local zones on another local disk. I am running solaris 5.10 8/07.
I used live upgrade to patch the system and created new BE (lucreate). Both root fs are mirror as RAID-1.
When I ran lucreate, it copies all 6 local zones root fs to the global root fs and failed no enogh space.
What is the best procedure to use lu with local zones.
Note: I used lu with global zone only, and worked without any problem.
regards,

I have been trying to use luupgrade for Solaris10 on Sparc, 05/09 -> 10/09.
lucreate is successful, but luactivate directs me to install 'the rest of the packages' in order to make the BE stable enough to activate. I try to find the packages indicated , but find only "virtual packages" which contain only pkgmap.
I installed upgrade 6 on a spare disk to make sure my u7 installation was not defective, but got similar results.
I got beyond luactivate on x86 a while ago, but had other snags which I left unattended.

IDS5.1 SP1 upgrade from 5.1 - Solaris

Hi,
We are trying to upgrade from 5.1 to 5.1 SP1 on Solaris. Ran the idsktune, and installed necessary patches. Made sure that admin server and slapd is running before istallation. Got the following error
ERROR: Could not update Directory Server Instance
URL ldap://ldaptest.server.com:389/o=NetscapeRoot user id admin DN cn=slapd-ldaptest-ldap01-389, cn=iPlanet Directory Server, cn=Server Group, cn=ldaptest.server.com, ou=server.com, o=NetscapeRoot (19:Constraint violation)
ERROR. Failure installing iPlanet Directory Server. Do you want to continue [n]?
Any Ideas ?
Thanks
Chandra mouli.

Hi,
Was this problem ever resolved? I'm having an almost identical problem when upgrading 5.1 to 5.1sp1 (gives a 153:unknown error rather than 19). We're running Solaris 8, local hosts, no NIS, no DNS.
Cheers
Simon

Any patch required to apply upgrading from 12.1.1 (rapid install) to 12.1.3

As subject, do anyone know are there essential (MUST-applied) patch during upgrade?

Hi;
As subject, do anyone know are there essential (MUST-applied) patch during upgrade?All steps&required patches mention in R12.1.3 patching. Similar issue already mention here before. Please see:
r12.1.1 to r12.1.3
Re: Questions about patching in eBS 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...

Removing a slice from Live Upgrade

Some time ago I used Live Upgrade to update a Solaris 9 4/04 V490 to Solaris 10 6/06. The internal disks (2 146GB) are mirrored using SVM. I used a couple of extra slices for the upgrade (/ & /var). I need to setup a new filesystem for an Oracle grid control install. I need to to reallocate one of the slices currently allocated to Solaris 9 (/var). I assume that I need to remove the slice/metadevice from Live Upgrade and then delete the SVM submirrors and mirror.
What steps/commands are needed to cleanup Live Upgrade and reuse the meta disk?
Thanks,
sysglen

assuming you have a filesystem on the volume, then you can't.
Solaris has no support for shrinking filesystems.
Well not until ZFS, but thats a different issue.
If you don't have a filesystem on the volume, you should be able to use metaclear to scrap the volume. Then readd the devices you do want.

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.

C6150 won't print after upgrade from Vista to Win 7

Hello.
I have a C6150 AIO that worked fine under Vista. Since I've upgraded to Win 7, I cannot get a printout from any application or the Windows test print. The HP Solution Center test print works fine.
- Printer is hooked up wirelessly
- I've installed the latest driver from HP that is supposed to be Win 7 ready
- I've also installed the patch they recommend after upgrading from Vista
There is no error. Print job shows up briefly in the print manager window, then disappears as though it printed. I'm at a loss, any help would be appreciated.
Paul
This question was solved.
View Solution.

I hope I have now sorted this problem.....
After numerous atems to install HP Windows 7 drivers & apps and failing I decided to restore the PCs to the day before I first installed the Drivers etc.
Then I unistall HP software and reinstalled the new drivers etc. This I had to do a couple of times on the Laptop (restore 3 days back).
After installing the HP software you can print a test page, print OK. Then goto printer properties and ty to print a test page from there, if this is unsuccessful restore system and start again. Most it took me was three attemps.
Now allI have to do is hope that the windows updates dont mess it all up again!
Hope this helps you......... Good luck

Upgrading from Solaris 10 s10_72 (beta) so patches work

Hi,
What is the recommended way to go from
Solaris 10 s10_72 X86 (beta) to a release that I can actually patch?
Thanks!

So I took the upgrade option from the 6/05 release I downloaded today from the Express program.
Now:
god@irt-v20z-01:autopatch 4:35pm 56 # cat /etc/release
Solaris 11 nv_15 X86
Copyright 2005 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 17 May 2005
Can I assume pca does not identify any patches for Solaris 11.
Am I now on a patchable a supportable platform?
(Previous threads had said there was no upgrading from Beta - but I appear to have done it with 6/05)
Thanks!

How to upgrade from Solaris 10 u2 to Solaris 10 u3 using Live Upgrade?

Does anyone know how I can use "live upgrade" (or any other method) for upgrading my solaris 10 u2 to Solaris 10 u3?
I can't find instructions anywhere! ugh.
Thank you for your help!

Try the following documentation:
http://docs.sun.com/app/docs/doc/819-6396
For future reference, I found this by going to sun.com -> documentation -> Solaris Operating Systems -> Solaris 10 Operating System -> Solaris 10 11/06 Release and Installation Collection.
-- Alan

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.

Solaris 10 5/08 live upgrade only for customers with serviceplan ?

Live upgrade fails due to missing /usr/bin/7za
Which seems to be installed by adding patch 137322-01 on x86 according to release notes http://docs.sun.com/app/docs/doc/820-4078/installbugs-114?l=en&a=view
But this patch (may also be the case for Sparc patch) are only available for customers with a valid serviceplan.
Does this mean that from now on its required to purchase a serviceplan if you would run Solaris 10 and use the normal procedures for system upgrades ?
A bit disappointing ...
Regards
/Flemming

Live upgrade fails due to missing /usr/bin/7za
Which seems to be installed by adding patch 137322-01 on x86 according to release notes http://docs.sun.com/app/docs/doc/820-4078/installbugs-114?l=en&a=view
But this patch (may also be the case for Sparc patch) are only available for customers with a valid serviceplan.
Does this mean that from now on its required to purchase a serviceplan if you would run Solaris 10 and use the normal procedures for system upgrades ?
A bit disappointing ...
Regards
/Flemming

Patching broken in Live Upgrade from Solaris 9 to Solaris 10

Similar Messages

Maybe you are looking for