Upgrade Solaris 8 to Solaris 10 (Jan 2006) with METASTAT

Hi..
On a v240 server running Solaris 8, I attempted many times to upgrade to Solaris 10 using the Jan 2006 Cd's. However. because a 3310 disk array that was striped, then mirrored using METASTAT and no spare blank disk...all upgrade attempts failed. I had a case open with Sun Support for quite a while and the work around was to unplug the array (containing Oracle 9i databases and 11i Oracle Apps) then do a fresh install of Sol 10, then reconfigure the metastat exactly the same as previously under Solaris 8 so that the databases and applications would become visible again.
So upgrading to Sol 10 from 8 was not simply and easy as one might think (and the marketing hype indicated). Also, I thought the new zfx file system as included with the Jan 2006 release, but sadly, it was not. So there is probably another upgrade from ufs to zfx that will not work because the Solaris 10 upgrade has difficulty with Sun's METASTAT software.
So I wonder out there...is there anyone else that had a similar issue, or solved it easily? And Sol 10 with zfx was to be release in June 2006 sometime...and June is disappearing fast...so any recent update to it?
Roger Sager
Sydney, Aus

Without the case and an explorer we can't comment much on this, but I have seen it before that this behavior is normal when people only patch the software and forget about the hardware connected or firmware. But again that is guessing. Also SVM was changed with the Solaris 9 release.
And for ZFS, its was not part of the release of sol10 1/06 as described in the release notes. Solaris 10 Update 2 is still on the testbed as far as I know and it will be release as soon as its ready (and not sooner then that I hope). As for ZFS, its cool and funny, but I would wait for the Solaris 11 release next year (?) when you want to put it to use in production. But if you really want ZFS hot and spicy then you could go for SXCR ;-)

Similar Messages

Live upgrade - solaris 8/07 (U4) , with non-global zones and SC 3.2

Dears,
I need to use live upgrade for SC3.2 with non-global zones, solaris 10 U4 to Solaris 10 10/09 (latest release) and update the cluster to 3.2 U3.
i dont know where to start, i've read lots of documents, but couldn't find one complete document to cover the whole process.
i know that upgrade for solaris 10 with non-global zones is supported since my soalris 10 release, but i am not sure if its supported with SC.
Appreciate your help

Hi,
I am not sure whether this document:
http://wikis.sun.com/display/BluePrints/Maintaining+Solaris+with+Live+Upgrade+and+Update+On+Attach
has been on the list of docs you found already.
If you click on the download link, it won't work. But if you use the Tools icon on the upper right hand corner and click on attachements, you'll find the document. Its content is solely based on configurations with ZFS as root and zone root, but should have valuable information for other deployments as well.
Regards
Hartmut

Will Solaris 10 (Jun/2006) zfs edition consider DiskSuite

Hi..
I previously upgraded a Sol8 server to Sol10 (Jan/06 without zfs), but it could not perform a upgrade as the disk array had to be unplugged (which was a metastat configuration). So I had to perform a fresh install, and reconfigure DiskSuite which picked up the data and databases correctly for use after the install. This was all with help from a SUN Support case. Anyways..does anyone know if the zfs version of the O/S is smarter and knows how to deal with metastat during an upgrade? I have a production box that is still on Sol 8, with a complex metastat configuration that I will have to upgrade one day soon. But the test box that I took from Sol 8 to Sol 10 (Jun/2006) O/S was difficult as that version of the upgrade could not deal with the DiskSuite configured 3310 disk array.
Please email me at [email protected] if anyone has an update or suggestions
Thanks for reading...Cheers...Roger

Hi Darren...
Well I raise CASE: 10815118 with support. On the LIVE Upgrade from Sol 8 to 10 (Jan 2006) attempt and the install_log produced the following...
=========>
Error opening file /a/var/sadm/system/admin/CLUSTER.
getInstalledPkgs: Unable to access /a/var/sadm/pkg
copyOldClustertoc: could not copy /a/var/sadm/system/admin/.clustertoc to /tmp/clustertocs/.old.clustertoc
Error:
Error: ERROR: The specified root and/or boot was not found or was not upgradeable
Pfinstall failed. Exit stat= java.lang.UNIXProcess@20ca8b 2
word must be specified if an upgrade with disk space reallocation is required
Processing profile
Checking c2t0d0s0 for an upgradeable Solaris image
Unable to start Solaris Volume Manager for unknown, c2t0d0s0 is not upgradeable
ERROR: The specified root and/or boot was not found or was not upgradeable
===============<
It seems to look for a disk (controller c2) that did not exist. I copied the DiskSuite files and other system files to another server. the /etc/lvm/md.tab under Sol 8 looked like the following...
================>
# root (on O/S disks 5 GB)
d0 -m d10
d10 1 1 c1t0d0s0
d20 1 1 c1t1d0s0
# swap (on O/S disks 8 GB)
d1 -m d11
d11 1 1 c1t0d0s1
d21 1 1 c1t1d0s1
# var (on O/S disks 4 GB)
d3 -m d13
d13 1 1 c1t0d0s3
d23 1 1 c1t1d0s3
# archive (on O/S disks 5 GB)
d4 -m d14
d14 1 1 c1t0d0s4
d24 1 1 c1t1d0s4
# usr/openv (on O/S disks 9 GB)
d6 -m d16
d16 1 1 c1t0d0s6
d26 1 1 c1t1d0s6
# /export/home (on O/S disks 3.7 GB)
d7 -m d17
d17 1 1 c1t0d0s7
d27 1 1 c1t1d0s7
# array 3310
# /software ( approx 140 GB)
d30 -m d40
d40 1 6 c3t8d0s1 c3t9d0s1 c3t10d0s1 c3t11d0s1 c3t12d0s1 c3t13d0s1 -i 128b
d50 1 6 c4t8d0s1 c4t9d0s1 c4t10d0s1 c4t11d0s1 c4t12d0s1 c4t13d0s1 -i 128b
# /databases ( approx 204 GB)
d31 -m d41
d41 1 6 c3t8d0s3 c3t9d0s3 c3t10d0s3 c3t11d0s3 c3t12d0s3 c3t13d0s3 -i 128b
d51 1 6 c4t8d0s3 c4t9d0s3 c4t10d0s3 c4t11d0s3 c4t12d0s3 c4t13d0s3 -i 128b
# /spare ( approx 92 GB)
d32 -m d42
d42 1 6 c3t8d0s4 c3t9d0s4 c3t10d0s4 c3t11d0s4 c3t12d0s4 c3t13d0s4 -i 128b
d52 1 6 c4t8d0s4 c4t9d0s4 c4t10d0s4 c4t11d0s4 c4t12d0s4 c4t13d0s4 -i 128b
===============<
We had c1 for the O/S disks and c3 & c4 for the 3310 array. Why it was looking for c2 was never determined???
The Sun support mob under that CASE ID suggested after many attempts to perform an upgrade...
=================>
In this situation, I recommend:
1. Remove Disk Array from Server i.e detach the connecting cable
2. Please check if Internal Disks are visible at OK prompt.:
ok probe-scsi-all
==================<
So I unplugged the array, but because there was no spare disk, I had to end up performing a fresh install, then attach and reconfigure the array exactly as before then the data, and more importantly, the Oracle databases and applications where recovered and useable.
So the question now is ... the server is on sol 10 and I have now rec'd the sol 10 Jun 2006 media...is it possible to perform an upgrade and how will zfs deal with the disksuite defs, because it have real problems under Sol 10 Jan 2006 edition.
Also, with the SUN engineers, on that CASE ID...we never got to the bottom of the problem with upgrading from sol 8 to 10 with disksuite implemented.
Cheers...Roger

Upgrading Solaris 10 from 32-bit to 64-bit in a VirtualBox VM

Hello,
I am running 32-bit Sol 10 u5 x86 as a guest in a Sun VirtualBox (Vbox) virtual machine on a 32-bit WinXP host with 64-bit VT-capable Xeon processors, and am considering upgrading Solaris 10 to 64-bit using the latest version of Vbox (2.0.0). After installing WinXP Professional x64 and the 64-bit version of Vbox, will I have to completely re-install Sol 10 to get it to run in 64-bit, or is there some way to get it to 64-bit without a re-install? The Vbox forums suggested that I post this question on a Solaris forum, as they don't know the answer.
They apparently also do not know if Windows XP x64 is a compatible host OS on which to run 64-bit guests. They list only Vista, Linux, and OpenSolaris as supported 64-bit host OSs. Has anyone used WinXP x64 as a host for Vbox 64-bit guests? Due to policy, Vista is not available to me on my system/network.
Thank you...

The x86 installer will place both 32-bit and 64-bit code on the disk.
The loader fired by GRUB will attempt to detect the proper hardware and launch the correct kernel.
Other portions of the upgrade could conceivably cause a problem, but having the CPUs go from 32-bit only to 64-bit capable shouldn't be an issue. You don't have to make any changes.
Darren

Upgrading Solaris 8 to Solaris 10 on SUN Sparc E2900 server

Hi,
We have a Sparc E2900 server which has Solaris 8 & Veritas Volume Manager 4.0. UFS & VXFS filesystems are under Veritas control.
We are planning to upgrade Solaris 8 to Solaris 10.
My questions are as follows
1) Can we upgrade from Solaris 8 to Solaris 10 directly ?
2) If Yes does Solaris 10 support Veritas Filesystem ?
3) Which is the best site to get information regarding upgradation ?
Regards,
Tejas J Raval

2) If Yes does Solaris 10 support Veritas Filesystem ?No, it dows not. If you want to use VxFS you still need to have Veritas products installed on this server

Upgrade Solaris 8 from 10/01 to 02/02

Hi all, I need to upgrade some systems from Solaris 8 10/01 to 02/02. I use VxVM 3.2 and VxFS 3.4. I don't need to upgrade Veritas Software. I want use Live Upgrade and in all example I find (2.6 ==> 8) I have to reinstall VxVM. In my situation, is Veritas products reinstallaton mandatory?? Can I use unencapsulation and encapsulation??

Hi,
You have to get volume manager out of the way before you upgrade solaris. You can un-encapsulate the root disk, upgrade then re-encapsulate if you want.
The way I do is as follows:
boot up normally from the vxroot disk.
touch /etc/vx/reconfig.d/state.d/install-db
#This will stop volume manager from starting up in a normal mode. Basically stops all the volume management stuff from interferring
remove the root entries in /etc/system for veritas (e.g. rootdev:/psuedo/vxio@0:0 and set vxio:vol_rootdev_is_volume=1)
#this line tells solaris that the root volume is a veritas device. Without this removed Solaris will try to mount up the root disk as a veritas volume and fail.
cp /etc/vfstab /etc/vfstab.old
cp /etc/vfstab.prevm /etc/vfstab
#replaces the /etc/vfstab file with the pre-volume-manager one
reboot the system.
It will now reboot without volume manager. Boot it all up to make sure there are no problems / errors, the do an init 0, then a boot cdrom - install or whatever to install solaris. upgrade solaris.
Machine will then reboot after Solaris has been upgraded. Re-install volume manager (might not be required if you're on the same solaris version) and re-encapsulate the root disk. Initalise the root-mirror, and mirror the root disk to the mirror (after the 2 reboots that volume manager needs)
Much easier to do the upgrade this way ;)
There are some infodocs on this procedure on the support.veritas.com knowledge base as well, if you want the `preferred veritas endorsed` method..

Upgrading Solaris OS (9 to 10) in sun cluster 3.1 environment

Hi all ,
I have to upgrade the solaris OS 9 to 10 in Sun cluster 3.1.
Sun Cluster 3.1
data service - Netbackup 5.1
Questions:
1 .Best ways to upgrade the Solaris 9 to 10 and the Problems while upgrading the OS?
2 .Sun Trunking support in Sun Cluster 3.1?
Regards
Ramana

Hi Ramana
We had used the live upgrade for upgrading Solaris 9 to 10 and its the best method for less downtime and risk but you have to follow the proper procedure as it is not the same for normal solaris. Live upgrade with sun cluster is different . you have to take into consideration about global devices and veritas volume manager. while creating new boot environment.
Thanks/Regards
Sadiq

Upgrading Solaris 9 to Solaris 10

Hi, I need to upgrade my workstation from solaris 9 to solaris 10 by CD. And also upgrade solaris 8 to solaris 9.
Do u have any idea how to do it? Can giv step by step?
Thanks
regards,
raymond

You do not need to use liveupgrade to upgrade, unless you want to learn it--it's complicated. It's good for servers and if you wish to go back to pre-upgrade. You need plenty of spare disk space.
First backup your data on your system to another hard disk or DVD.
Then stick in the installation DVD and select "Upgrade" instead of "Initial Install" when asked.

Sun Java Application Server 8.1 Upgrade Solaris 9 to Solaris 10

I have Sun Java Application Server 8.1 (version 8.1_02 (build b06-fcs) ) and HA which are currently installed on Solaris 9 box (Sparc).
Now, I plan to upgrade Solaris 9 to Solaris 10. What should I need to do before and after migration?
Thanks.

Before I start, disclaimer -- I have no knowledge of Hibernate and the following comments are based on the stack trace you have included.
I think your permissions might be set all right but you might have an error in the hibernate query. It looks like hibernate uses antlr to parse the queries. While parsing the query, antlr is encountering an exceptional condition and is trying to exit the VM (by calling System.exit()). Obviously, the hibernate code does not have that permission and therefore the exception is logged.
My guess is if you fix the query such that hibernate/antlr can parse it, you will not run into this error.
Hope this helps,

Upgrading Solaris 8 to Solaris10

Dear all
Can i upgrade Solaris 8 to Solaris 10 directly or i have to upgrade to solaris 9 first
any documentation specfic to upgrade will be help
Regards

2) If Yes does Solaris 10 support Veritas Filesystem ?No, it dows not. If you want to use VxFS you still need to have Veritas products installed on this server

Sunscreen upgrade Solaris 2.7 fails

I just rec. my new copy of Solaris 9.
I am attempting to upgrade a previous version of SunScreen
firewall running on Solaris 2.7.
So I kicked off the upgrade script and everything
seemed to be working good. The old Firewall was backed up
and removed. But during the install of the new Sunscreen
packages it failed. The problem is that the upgrade script tried
to install the following package: SUNWhttp as part of the upgrade
process. The problem is it doesn't exist on the CD in the 'sparc' directory.
As a result, the upgrade script terminated with an error complaining that
the package was not found.
Now I have a Solaris 2.7 system with no Firewall and the upgrade will not
continue.
As far as I know, SUNWhttp is not required for SunScreen 3.2 so I think
the upgrade script needs fixing.
Does anyone know of a modified/patched upgrade script that
will allow me to continue the upgrade or at least can someone tell me how best to
proceed? I want to be able to retain my old Sunscreen config.
that was backed up.
I would rather not have to go through the whole install from scratch.
Any help on this would be great.
Thanks.
Ken Kempster.

http://sunsolve.Sun.COM/pub-cgi/show.pl?target=patches/patch-license&nav=pub-patches

Solaris 10 - Jan 2005 release

Hi,
I need to download Solaris 10 Jan 2005 release for sparc platform.I am unable to find that release in the sun site.Only latest release of solaris10 is available.
Is there any archive available in sun site to download older solaris10 release.Also anybody is having iso image of solaris10 jan 2005 release for sparc platform.
Kindly let me know.
Thanks and regards,
dhiyan

My bad...
When reading the initial posts, I only saw "older releases".
I must have only used one eye to read them and somehow thought the inquiry was for Solaris 8.
I just didn't see any of those references to Solaris 10 in the posting.
Yes. the March 2005 release is the first General Availability (GA) release of Solaris 10.
While it may have first become available in a limited form to some people, sometime in January of that year, the official date on the GA Release is 3/05.
Glance through Docs.Sun.Com
[Solaris 10 Release and Installation Collection|http://docs.sun.com/app/docs/coll/1236.1?l=en]

Upgrading Solaris with Zones

I have just found the following statement in the Solaris 10 Install Guide, section "Upgrade Limitations":
"If you have configured Solaris Zones on your system, you are not able to upgrade until you have unconfigured and uninstalled your non-global zones"
I have a serious problem with this limitation. It seems to be impossible to upgrade a Solaris 10 system with zones configured. I would have to shut down and uninstall my zones and applications to upgrade the OS.
There's not even a way to move the affected zones to another system to keep the application running if the host with the global zone needs maintenance due to OS upgrade, HW maintenance or if simply has too many zones configured on it and all resources are exhausted.
With these limitations I don't see much reasonable use for zones. In particular, once a zone and an application is set up on a physical box with a particular OS release I am stuck with it for all times.
How are you going to solve these problems. And when? What are zones good for in the current implementation? I am still waiting for convincing arguments to use zones ...

I guess I'll state for the record, lest anyone should be confused by my last post, that LiveUpgrade doesn't allow upgrade anymore. I guess I got away with it before LU was upgraded to restrict such activity.
ERROR: Unable to upgrade boot environment <Solaris10-B58>.
INFORMATION: Boot environment <Solaris10-B58> has one or more non-global
zones installed. This version of Live Upgrade cannot upgrade a boot
Guess I'd better figure out how to backup my zones so I clean remove them. A simple tar will probly do the trick for now.
benr.

Upgrading Solaris with Zones installed

So Solaris 5/09 was released. Previously I have upgraded Solaris the simplest way by simply downloading the DVD, throwing it in and running the upgrade. However that was before we started using the zones feature and I'm not sure if there is anything special I have to take into account now.
They're simply native zones. Is there anything special I have to do or will the simple disk upgrade work still?

Upgrading 10/08 to 5/09, including zones, should be very clean, with or without Live Upgrade. The advantage is Live upgrade is minimal downtime and a safe backout if the upgrade does cause something to break. If you use ZFS root filesystems, it is even easier and 'wastes' very little disk space.
Mark

Solaris 10 on 280R with A1000

We have loaded solaris 10 ( 3/05) on our server i.e. Sunfire 280R with A1000 storage connected to it thru SCSI cable. We have addon SCSI card installed in server. Our A1000 is having only one controller.
Afterthat we have loaded sun storage RAID Manager 6.22 software to configure A1000 , we have made slices using RAID 5 & using RM6 utility. While rebooting the server we are getting following two errors & keeps scrolling on screen for about 10 minutes , though we are able to access A1000;
1. Warning : mod_load : cannot load module 'rdriver'
2. /kernel/drv/spark9/rdriver:undefined symbol 'dev_get_dev_info'
Is any solution to above errors? Is any patch / upgrade / firmware etc for above errors ?
Will it recommended to upgrade to solaris 10 or continue with solaris 9. we are using this as a database server with oracle 10G.

FYI, I think Sun discontinued support for the A1000 h/w in Solaris 10... should be documented.
I only mention this in case you want to have Sun support help you... if it works fine, I generally wouldn't worry. But it is a production system, I might have second thoughts about using Solaris 10 with unsupported h/w.
My $.02, YMMV.
David Strom

Upgrade Solaris 8 to Solaris 10 (Jan 2006) with METASTAT

Similar Messages

Maybe you are looking for