List of patches
Hello,
We have the following version :
Sun Java(tm) System Messaging Server 6.2-3.04 (built Jul 15 2005)
libimta.so 6.2-3.04 (built 01:32:55, Jul 15 2005)
SunOS mailstore-1-1 5.10 Generic_Patch i86pc i386 i86pc
and I see in some mailinglists that the version
Sun Java(tm) System Messaging Server 6.2-7.05 (built Sep 5 2006)
libimta.so 6.2-7.05 (built 12:18:44, Sep 5 2006)
is available.
How can we upgrade from version 6.2-3.04 to 6.2-7.05 ?
How can we easily find all the ptches that apply to our current version ?
Thanks
# 1
Hi,
How can we upgrade from version 6.2-3.04 to 6.2-7.05 ?
Apply patch 118208-58.
How can we easily find all the ptches that apply to our current version ?
Search for the patch number (118208) here:
http://sunsolve.sun.com/pub-cgi/show.pl?target=patchpage
This will provide you with the most recent available public patch.
Regards,
Shane.
# 2
Beware I just attempted to add the current JES Msg-serv patch on an x86 OS and got this:
ERROR:
pkgadd: ERROR: The package <SUNWmsgco> is currently installed on the system in the
global zone. To install the new instance of this package in the global
zone only, you must specify the -G option. To install the new instance
of this package in all zones you must first remove the existing instance
of this package from the global zone first (via pkgrm) and then install
the new instance of this package in all zones.
pkgadd: ERROR: package <SUNWmsgco> cannot be installed on this system/zone
It looks like one needs to remove the existing SUNWmsgco then reinstall it in order to upgrade with this patch, a little odd I'd say. Why does the JES default msg install install this pkg in a way that requires this in the first place ?
# 3
Ok, spoke a little to soon:This looks like what I needed to do: patchadd -d -G .It seems happy now!
# 4
Hi,Any reason why you use -d? This prevents the patch from being removed which I would consider to be very risky.On the -G front, this was discussed a number of times in earlier forum threads.Regards,Shane.
# 5
Shane,
this was a mistake on my part...I confused it with pkgadd's -d option
In this case this is a test box but as you say "risky" is a good way to put it.
I will also have a look at the previous posts regarding the -G option. The error at first was a little confusing in that it was not clear (to me) whether to use -G or that previous use of -G was the problem !!
-d
Does not back up the files to be patched. The patch can-
not be removed.
# 6
Shane,
As a followup on all this discussion on -ds and -Gs etc. with respect to version upgrade can you clarify a couple of things:
By default are the msg-serv pkgs installed in the global zone?
(ie when using the JES installer)
What care does one want to take in making sure that they do not deviate from the necesary defaults so as to (down the road) encounter problems with say some of the other JES components that interconnect?
I also need to read up some more on the solaris zones concept but I do not want to make an error now that will come back to bite me later.
-john
# 7
Hi,
> By default are the msg-serv pkgs installed in the
> global zone?
> (ie when using the JES installer)
Your question is the wrong way around. If you install messaging server in a global zone then of course the package is in the global zone. If you install it in a full-zone (sparse zones not yet supported) then you would run the patch in the full-zone and not in the global zone. Packages in the global zone go across all zones, packages in a full-zone are isolated to that zone.
Some of the shared components are required to be installed in the global zone, and they are then installed in the full-zones as well.
> What care does one want to take in making sure that
> they do not deviate from the necesary defaults so as
> to (down the road) encounter problems with say some
> of the other JES components that interconnect?
Perhaps you should read:
http://www.sun.com/blueprints/0806/819-7663.html
This goes through installing JES2005Q4 on a T2000 using numerous solaris containers (aka solaris zones).
I also encourage everybody to keep an eye on this blog :
http://blogs.sun.com/factotum/
This provides lots of hits/tips/new doco etc.
> I also need to read up some more on the solaris zones
> concept but I do not want to make an error now that
> will come back to bite me later.
Research is your friend. Think of this as job security, if anybody could do it then why would they need to hire you ;)
Regards,
Shane.
# 8
Shane thanks for the good tips.
>
> > By default are the msg-serv pkgs installed in the
> > global zone?
> > (ie when using the JES installer)
>
> Your question is the wrong way around. If you install
> messaging server in a global zone then of course the
> package is in the global zone. If you install it in a
> full-zone (sparse zones not yet supported) then you
> would run the patch in the full-zone and not in the
> global zone. Packages in the global zone go across
> all zones, packages in a full-zone are isolated to
> that zone.
>
> Some of the shared components are required to be
> installed in the global zone, and they are then
> installed in the full-zones as well.
This all makes sense, but b/c i did not conscientiously install the JES msg-serv in a particular zone ( i assumed the default was chosen) and It appears that this is the "global" zone. I will have a look at the blueprints piece ... Thanks!
-john
# 9
Indeed, the default install is a global one.
