Wednesday Apr 18, 2012

Resolving stale links to SunSolve documentation on My Oracle Support

A couple of folks have posted comments on old blog entries complaining that they can't resolve links to old SunSolve content.

SunSolve was decommissioned as part of the integration into Oracle.  Documentation which is still relevant was migrated.  The URIs changed in the process.  So did the document IDs.

On the basis that it's better to teach a man how to fish than to just give him a fish, here's a tip on how to do find the current links to such migrated documentation.  At least, this is how I do it:

If you're looking to find the current URI for a document for which you have a stale URI such as http://sunsolve.sun.com/search/document.do?assetkey=1-79-250526.1-1 , simply search MOS using the "core" document number in the old SunSolve URI - for example "250526" in this example.  Enter this in the "Search Knowledge Base" search box. 

If the document is still relevant, MOS will usually return the corresponding new Document ID.  For example, in this case Document 1019995.1.  The top line of the document 1019995.1 states "Migrated ID: 250526".

I've updated the Doc IDs for a number of my old blog postings.  Apologies for the inconvenience caused.

Friday May 08, 2009

How to analyze patch failures and other useful info

My colleague, Enda O'Connor, has published 3 more patching articles on Big Admin which I hope you will find useful:

I think the first article is particularly useful to help customers and support engineers understand what data to gather to enable analysis of a patching issue.  Even if you are not able to analysis the issue yourself, providing this data to Sun Support when you log a call will help speed up the issue analysis by Sun.
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