Oracle Sun patches now available from My Oracle Support (MOS)

As you may already know, Oracle Sun patches are now available from My Oracle Support (MOS).

We've uploaded over 30,000 6-2 digit PatchIDs to MOS, including all Solaris 8, 9, and 10 patches, SunCluster, and patches for over a thousand other products.  Any patch for these products which was available on SunSolve is now also available from MOS, making MOS your one stop support shop for all Oracle products.

My colleague David F. Campbell has also completed the upload of all patch and firmware update content to MOS from CDS (Content Delivery System, formerly the Sun DownLoad Center (SDLC)).

Any another colleague, Tom Murray, has completed the upload of StorageTek patch content natively to MOS too. Most StorageTek patches are in a mainframe patch format and are not applied using the Solaris 'patchadd' utility.  To host them on SunSolve after the StorageTek acquistion, we wrapped them in a 6-2 digit PatchID.  However, it doesn't make sense to wrap these StorageTek 6-2 digit PatchIDs in Oracle BugDB IDs which would be a second level of indirection.  Therefore, Tom has uploaded them in their native format to MOS.

Customers with an Oracle support contract can log into My Oracle Support.  The full functionality version is Flash based, https://support.oracle.com.   There is also a limited functionality html version, https://supporthtml.oracle.com .

Click on the "Patches & Updates" tab and you'll see that the Patch Search options have been expanded to "Patch Name, Number or Sun CR ID".  As it suggests, you can search by the 6-2 digit PatchID or a Sun CR (Change Request) number (i.e. 7 digit BugID).

Please note that you can see all revisions of a patch by searching with the format 119254-% .  The "-" (dash) is required in the current version of MOS.

To get the Solaris patch clusters and patch bundles, use the "Product or Family (Advanced Search)" option on the "Patches & Updates" tab. Select:

  • Product is Solaris Operating System
  • Release is Solaris 10 Operating System
  • Select "Type" instead of "Platform" and Type is "Patchset"

...and it'll return all Solaris 10 patch clusters and patch bundles. This includes the Solaris OS Recommended Patch Clusters, the Solaris Update Patch Bundles, the Solaris OS Critical Patch Updates (CPUs), Live Upgrade (LU) Zones Patch Bundle, etc.

You can add further search filters, e.g. Platform is Oracle Solaris on SPARC (64-bit), to further refine the results.

Using "Platform" is useful to eliminate the double-entries for 32-bit and 64-bit.  These dual returns are a pet peeve of mine and I'm continuing to work with the MOS team to get this "fixed" in a future release.  They are an historical artifact from Oracle DB platform porting and are not relevant to the Solaris OS.

Note that the alternative option for "Type" is "Patch", which can be used to search for individual patches.

For example:

  • Product is Solaris Operating System
  • Release is Solaris 10 Operating System
  • Type is Patch
  • Platform is Oracle Solaris on SPARC (64-bit)
  • Description contains patch utilities

In the example above, the Description option searches for the phrase "patch utilities" in the Synopsis line of patches. This returns the Solaris 10 SPARC patch utility patches.

Since the synopsis line of patches is free format, some guesswork is involved in searching using this method. For example "patch utility" returns nothing. "IP" returns more than just TCP/IP related patches. "firmware" returns any patch with the word "firmware" in its Synopsis.

Alternatively, you can use "Classification", which can be set to "Security" to return Security patches.

Click on the "Updated" column in the search returns to get these listed from earliest to latest or vice versa.

My understanding is that MOS currently limits search results to 100 entries in the current version and again I'm discussing "fixing" this with the MOS team in a later release.

Searches can be edited and saved for reuse at a later date.

A "Classification" of "Other Recommended" rather logically will give other non-security recommended patches included in the Solaris OS Recommended Patch Cluster. (In MOS terminology, "Security" and "Other Recommended" together are equivalent of the old Sun "Recommended" term.) But if you want to know exactly what's in the Solaris OS Recommended Patch Cluster, it's easier to simply look at the patch list in the Cluster README.

As discussed in the http://blogs.sun.com/patch/entry/solaris_10_recommended_patching_strategy which I published yesterday, we're really trying to encourage customers to move away from selecting unique patch combinations and to instead use the Solaris OS patch clusters and patch bundles as the core of your patching strategy.

If you are looking for individual patches to address a specific CR, then use "Patch Name, Number, or Sun CR ID" search option instead of "Product or Family (Advanced Search)". For example, enter Sun CR ID 6927931 and patch 119254-78 is returned which is the patch in which the CR is fixed. A CR which was fixed a long time ago, e.g. 6486471, will return all patch revisions which contain the fix, so you can decide whether you want to take the latest patch revision which fixes it or the earliest.

For firmware patches:

  • Go to the "Patches & Updates" tab
  • Click on "Produce or Family (Advanced Search)"
  • Select the hardware product in which you are interested.  For example, type "x6" and select, Product is Sun Blade X6440 Server Module.
  • Select the Release(s) you are interested in, e.g. Release is X6440 SW 2.2.0
  • Click Search.

As I say, I'm continuing to work with the MOS team to enhance the customer experience further, but I hope you find the above tips helpful.

 So which Oracle Sun patches are currently available from MOS ?:

  • Over 30,000 Oracle Sun 6-2 digit PatchIDs (i.e. of the format xxxxxx-xx) for over a thousand products and product versions.  This includes all Solaris 8, 9, and 10 patches, SunCluster patches, etc.
  • All the Oracle Sun Patch Clusters and Patch Bundles
  • All the patch and firmware update content previously hosted on CDS (Content Delivery System, formerly the Sun DownLoad Center (SDLC))
  • All StorageTek patches

What's not transitioned to MOS ?:

  • Really, really old patches, such as SunOS 1.x patches, Solaris 7 and older patches, etc.   These are utterly obsolete products so there's no point in propagating this crud forward.
  • Public patches available without a support contract, such as OpenOffice and StarOffice patches.  It is planned to support these in a future MOS release.  In the meantime, they can be downloaded from https://sspatch.oracle.com/showMe.do?page=public
  • Some patch metadata files such as the "Checksum" and "patchdiag.xref" files.  It is planned to support these in a future MOS release.  In the meantime, they can be downloaded from https://support.oracle.com/CSP/main/article=?cmd=show&type=NOT&id=1272947.1

Terminology: You say potato, I say potato, and Dan Quail says "potatoe"

There's an unfortunate patch terminology clash between Oracle and Sun patches which you need to be aware of:

  • The Sun term "obsolete" equates to the Oracle term "superseded" - i.e. a patch which is no longer the latest patch is a sequence.
  • The Sun term "withdrawn" equates to the Oracle term "obsolete" - i.e. a patch withdrawn from release due to problems with it.

Since the term "obsolete" is deeply embedded in SVR4 patching, e.g. the variable name SUNW_OBSOLETE in the pkginfo files, it is not possible for us to change it.  Neither is it likely that Oracle will change their terminology as it's well known in DB and Fusion middleware circles.  Users simply need to be aware of this terminology clash when dealing with Oracle Sun SVR4 based patches.

I hope this doesn't become a hot potato. :)

Best Wishes,

Gerry.

Comments:

I have 15+ years of experience with both Sun's support web site and Oracle's, and frankly this is not welcome news to me since I'm sure it means that the Sun sites (e.g. Sunsolve) will eventually be going away.

Sure, Sun's support site wasn't perfect, but compared to Oracle's it was a paragon.

Oracle's old support site (Metalink) was clunky, somewhat difficult to navigate and wasn't the most reliable, but was usable to some extent. The new site (My Oracle Support) plumbs new lows: it is unreliable (constant problems with logins, unresponsiveness, etc.), very difficult to search effectively (e.g. for stuff I \*KNOW\* exists because I found it previous in Metalink), and relies on non-standard technology (Flash) which causes all sorts of navigation issues. Most importantly, however, is the fact that Oracle insists on MOS as the "one size fits all" solution for all of their purchased technologies. Thus, while I'm trying to track down an Oracle RDBMS issue I'm constantly inundated with bogus hits related to "times 10 in memory DB", PeopleSoft , BEA, and Siebel. The signal to noise ratio on searches is terrible!

Previously, I only had to suffer through this while looking for Oracle support, but I can see that I'll soon be "enjoying" the experience for Sun support as well :-(

I held off criticizing MOS for over a year figuring that the problem was likely just that I wasn't used to it, but the more I use it the less I like it. I have fed this back to Oracle, but received basically a "thanks, but we think it's great" response.

While I'm sure that consolidating all of the support in one system is good for Oracle's profit margin, when I'm looking for support on a Sun issue there is no "synergy" whatsoever (from a customer perspective) in having Sun information in the same support system as Oracle/Siebel/BEA/Peoplesoft - it only reduces the support sites effectiveness.

Integrated Sun support of software+hardware was one of the key reasons why we purchased Sun equipment; if we have to put up with Oracle-level "support" I can't see this continuing in the future.

Posted by Sean Walmsley on August 03, 2010 at 01:50 PM IST #

Hi Sean,

I'll pass your feedback on to the MOS folks.

As a fairly new MOS user myself, I find some bits really good (e.g. it remembers what you searched for last time), although the use of Flash was a bit of a surprise to me and I've fed that back to the MOS folks. :)

I've been working very closely with the SunSolve folks over the last 3 years to improve the patch related content and content presentation. I think we made pretty good progress (e.g. PatchFinder, Cluster download page, etc.) but from a pretty poor starting position IMHO. Independently, they significantly improved the search experience, again from a pretty poor starting position.

I've been working closely with the MOS folks over the last 11 months and I've been impressed with their willingness to listen and commit to improvements. So while Oracle, unlike Sun, doesn't do forward looking statements about what improvements are in development, I expect some of the issues you mention will be addressed.

Feedback is good. Thanks for providing it.

Best Wishes,

Gerry.

Posted by Gerry Haskins on August 05, 2010 at 10:32 AM IST #

Thanks for this post
but this means that Oracle is transforming everything sun users are used to into oracle, most of the times I get lost when I try to download a patch from Oracle, lets hope they make it simple.

Posted by Java on August 20, 2010 at 04:24 AM IST #

Hi Java,

Apologies for my delay in responding.

I'm working with the MOS folks to try to make the experience as simple as possible.

MOS does support the entire product portfolio, so we're unlikely to see as much Solaris specific functionality as we had on SunSolve.

Your feedback on what you like/dislike is always useful and I'll pass any feedback you have on to the MOS folk.

Best Wishes,

Gerry.

Posted by Gerry Haskins on October 12, 2010 at 11:53 AM IST #

With SunSolve's execution date set, I'm trying to make the switch to MOS. In a word, MOS is: difficult.

Specific gripes:
1. Why can I not search for a Solaris patch by 6 digits (without rev)? I want to find the newest revision of a patch. Please consider either allowing a search by only 6 digits, or make a rev of "00" give me the latest revision.

2. In the list of results from a patch search, this text is shown above each Synopsis: "Solaris Operating System : Patch". Its obvious. I don't need this line. Please remove it or at least put it in a different field. It makes it very difficult to scan the Synopsis information.

3. SunSolve Advanced Search provided "Released" date. MOS has "Update". Are these equivalent?

4. When MOS patch search returns a patch result, I have to click a link to get to an intermediate page that gives me very little information (Synopsis, size, a list of bug CRs (with no summary line about each bug), etc). Then, I need to click another link to get to the README, in a separate SunSolve(!) browser window. Why? I need less clicks, not more. From a search results list, please let me download and view the README directly.

5. Why are the "Bugs Resolved by this Patch" not links? Maybe a migration issue?

6. This from the FAQ page is totally stupid:
"Note that in My Oracle Support, the same patch revision can match multiple search categories and therefore may be listed multiple times in the search results. For example, the same Sun patch may be applicable to both 32-bit and 64-bit systems or to multiple products, product versions, or operating systems (for Java based patches). The patch is the same patch in each case. "

Why show me the same patch twice?

That's all for now...

Posted by Torrey Martin on December 08, 2010 at 11:00 PM GMT #

Hi folks

It is 15 years I am working with Sun/Solaris products for big companies. Finding Patches was very simple so far and worked perfectly. Since Sunsolve has now moved to Oracle MOS it is a nightmare !! I have not found one patch so far !! Absolutely useless. Is Oracle targetting to loose Solaris customers?

Posted by Walter Brown on December 17, 2010 at 06:04 AM GMT #

Has anyone actually had any luck finding patches on the MOS page? It appears you can only find patches if you know the patch # and add a valid rev #. This appears to be the only way to find patches. I can't find anywhere with a list of patches or a better way to search. It's very frustrating. Since MOS is a POS, can they bring sunsolve back? It at least worked and was useful. MOS is at best an alpha release for being useful for Sun products.

Posted by guest on January 04, 2011 at 12:27 PM GMT #

Hi Torrey, Walter, and "192.91.172.36",

Many thanks for your feedback. I've passed your feedback onto the MOS team. Specific feedback such as Torrey's is especially useful.

While I am not a MOS expert, I can answer a couple of the points raised.

Please note that you can see all revisions of a patch by searching with the format 119254-%
The "-" (dash) is required in the current version of MOS.

To get the Solaris patch clusters and patch bundles, use the "Product or Family (Advanced Search)" option on the "Patches & Updates" tab. Select:

Product is Solaris Operating System
Release is Solaris 10 Operating System
select "Type" instead of "Platform" and Type is "Patchset"

...and it'll return all Solaris 10 patch clusters and patch bundles. This includes the Solaris OS Recommended Patch Clusters, the Solaris Update Patch Bundles, the Solaris OS Critical Patch Updates (CPUs), Live Upgrade (LU) Zones Patch Bundle, etc.

You can add further search filters, e.g. Platform is Oracle Solaris on SPARC (64-bit), to further refine the results.

Using "Platform" is useful to eliminate the double-entries for 32-bit and 64-bit. These dual returns are a pet peeve of mine and I'm continuing to work with the MOS team to get this "fixed" in a future release. They are an historical artifact from Oracle DB platform porting and are not relevant to the Solaris OS.

Note that the alternative option for "Type" is "Patch", which can be used to search for individual patches.

For example:

Product is Solaris Operating System
Release is Solaris 10 Operating System
Type is Patch
Platform is Oracle Solaris on SPARC (64-bit)
Description contains patch utilities

In the example above, the Description option searches for the phrase "patch utilities" in the Synopsis line of patches. This returns the Solaris 10 SPARC patch utility patches.

Since the synopsis line of patches is free format, some guesswork is involved in searching using this method. For example "patch utility" returns nothing. "IP" returns more than just TCP/IP related patches. "firmware" returns any patch with the word "firmware" in its Synopsis.

Alternatively, you can use "Classification", which can be set to "Security" to return Security patches.

Click on the "Updated" column in the search returns to get these listed from earliest to latest or vice versa.

My understanding is that MOS currently limits search results to 100 entries in the current version and again I'm discussing "fixing" this with the MOS team in a later release.

Searches can be edited and saved for reuse at a later date.

A "Classification" of "Other Recommended" rather logically will give other non-security recommended patches included in the Solaris OS Recommended Patch Cluster. (In MOS terminology, "Security" and "Other Recommended" together are equivalent of the old Sun "Recommended" term.) But if you want to know exactly what's in the Solaris OS Recommended Patch Cluster, it's easier to simply look at the patch list in the Cluster README.

As discussed in the http://blogs.sun.com/patch/entry/solaris_10_recommended_patching_strategy which I published yesterday, we're really trying to encourage customers to move away from selecting unique patch combinations and to instead use the Solaris OS patch clusters and patch bundles as the core of your patching strategy.

If you are looking for individual patches to address a specific CR, then use "Patch Name, Number, or Sun CR ID" search option instead of "Product or Family (Advanced Search)". For example, enter Sun CR ID 6927931 and patch 119254-78 is returned which is the patch in which the CR is fixed. A CR which was fixed a long time ago, e.g. 6486471, will return all patch revisions which contain the fix, so you can decide whether you want to take the latest patch revision which fixes it or the earliest.

As I say, I'm continuing to work with the MOS team to enhance the customer experience further, but I hope you find the above tips helpful.

Best Wishes,

Gerry.

Posted by Gerry Haskins on January 07, 2011 at 08:22 AM GMT #

Torrey, one minor item which might help. When you get results you can select the row and immediately click on the Read Me button. You don't need to drill down (which you are doing by clicking the patch link) to get to the read me.

You can also multiple select and bring up a single download window from this screen (where a wget script gets generated for your entire selection). There is a fix in for the upcoming release to make it move obvious you can do these actions.

This might help some.

Posted by Richard on January 07, 2011 at 01:18 PM GMT #

How can I get Sun Contract Number

Thanks in Advance
Swamy

Posted by Swamy on January 18, 2011 at 02:51 AM GMT #

Sunsolve used to allow me to enter System Serial Numbers to obtain contract/warranty information. This was very useful. With Sunsolve I could use this information and my account was running quite nicely.

Since Sunsolve has disappeared this feature is not available in the Oracle Support environment - I cannot get past the initial screen as I do not have the contract/warranty information to hand for our servers.

Contacting Oracle resulted in an obtuse canned response which immediately and obviously demonstrated my email had not even been read.

My old Sunsolve username/password combination do not work on the new Oracle site. Why not port this (along with contract information) over?

Don't get me started on the public pulling of Sunbook...

Posted by Ed Austin on January 27, 2011 at 08:03 AM GMT #

Hi Ed,

You need to go to the My Oracle Support (MOS) Sign In page, https://support.oracle.com (Flash) or https://supporthtml.oracle.com (html) and register there. There is a registration FAQ and Welcome Center there.

The back ends of the two systems, SunSolve and MOS, are quite different, hence the need for registration rather than automatic propagation of the Sun Online Accounts (SOAs). The two systems were available in parallel for several months to give customers time to get their MOS registrations sorted out and there were lots of notices on SunSolve of the need to get ready for the transition.

I know the transition has been a major inconvenience for everyone. I do apologize most sincerely for that. It is very hard to change such fundamental infrastructure without problems.

If you are still having problems after following the registration process, please email me and I'll try to get your issues sorted out for you.

Best Wishes,

Gerry.

Posted by Gerry Haskins on January 28, 2011 at 09:25 AM GMT #

Having used Sun products and associated support services my entire career I must say MOS and the new Oracle support structure is truly atrocious. I've had nothing but delays in accessing patches, difficulty locating the information I need, poor responses from support tickets and trouble resolving issues that would have previously been resolved in a matter of minutes under Sun management. The fact I am now at this blog looking for answers just goes to show how bad it has become.

Just one example; after a simple renewal of an existing support contract in Nov 2010 I STILL don't have access via MOS to the patches I need, since the entitlements were not entered correctly, despite constant housing of Oracle to fix it. I'm paying for something I'm not receiving and that is bad. Oracle seem incapable of customer service or contract management. Support requests are batted back and forth to different people and sections with resolution and there seems to be a lot of internal confusion (which I've seen first hand as I've been CC'd on internal comms relating to my issues!) .

I, like others here, have given MOS and Oracle time; hoping the issues I have were a result of the merger and change over, but time has improved nothing. I can no longer justify to myself, let alone the bean counters, paying Oracle for such a poor offering.

I will be looking to other vendors once refresh time is here - the industry has moved on, where there used to be but one choice, there are now other viable options for those of us willing to explore them and I am sad to say that my data centre will no longer be home to any new Oracle "products". Not that Oracle will care.

RIP Sun Microsystems - you will be missed.

Posted by Dan on March 03, 2011 at 10:11 PM GMT #

Hi Dan,

I'm sorry to hear of your issues. I have passed your feedback onto the relevant folks in Services to follow up with you to resolve your issues.

I'll post a new blog entry on Entitlement which may be useful in highlighting the potential areas where issues or misunderstandings can arise.

Best Wishes,

Gerry.

Posted by Gerry Haskins on March 15, 2011 at 02:53 AM GMT #

I agree whole heartedly with the difficulties that others have had with the Oracle patching mess. Information that was once freely available is now accessible only through a convoluted process, which suggests that Oracle is more intent on the MOS revenue stream than friendly customer service.

The unfortunate side effect of limiting access to information is that it is far more likely that companies will fall behind in their patch awareness and application.

In our case, patching is managed of an external IT provider, and since we do not own the contractual relationship with Oracle it is next to impossible for us to validate that our systems are being kept up to date. Ouch.

Posted by guest on June 22, 2011 at 08:40 AM IST #

Hi,
I was thinking of acquiring a sun certification, so I bought a couple of used server for my traing and just discovered I need a support contract also to get the OBP updated.
Will this mean my idea of self training is a mess? Did I waste my money on books and hardware?
I remember years ago sunsolve was free (at least partially) but now it seems pay only. Did I miss something?

Posted by Toni on July 28, 2011 at 06:26 PM IST #

Post a Comment:
  • HTML Syntax: NOT allowed
About

This blog is to inform customers about patching best practice, feature enhancements, and key issues. The views expressed on this blog are my own and do not necessarily reflect the views of Oracle. The Documents contained within this site may include statements about Oracle's product development plans. Many factors can materially affect these plans and the nature and timing of future product releases. Accordingly, this Information is provided to you solely for information only, is not a commitment to deliver any material code, or functionality, and SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISIONS. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle. THIS INFORMATION MAY NOT BE INCORPORATED INTO ANY CONTRACTUAL AGREEMENT WITH ORACLE OR ITS SUBSIDIARIES OR AFFILIATES. ORACLE SPECIFICALLY DISCLAIMS ANY LIABILITY WITH RESPECT TO THIS INFORMATION. ~~~~~~~~~~~~ Gerry Haskins, Director, Software Lifecycle Engineer

Search

Categories
Archives
« April 2014
MonTueWedThuFriSatSun
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
    
       
Today