Martin, Your conclusion maybe correct but your explanation does not fit my recent experience: On June 10th I received the same error (Using /var/tmp/patchdiag.xref from Jun/09/10) - Using this patchlist.txt file 124861-19 124863-23 126495-04 124867-14 124870-03 124872-07 126995-04 127001-04 127143-03 127000-13 128225-01
The pca command found all the patches. /var/tmp/pca --list /var/tmp/patchlist.txt --patchdir="/var/tmp/pcatmp" Downloading xref file to /var/tmp/patchdiag.xref Trying https://sunsolve.sun.com/ (1/1) Using /var/tmp/patchdiag.xref from Jun/09/10 Host: robin (SunOS 5.10/Generic_142900-11/sparc/sun4u) List: 124861-19 124863-23 126495-04 124867-14 124870-03 124872-07 126995-04 127001-04 127143-03 127000-13 128225-01 (11/3873) Patch IR CR RSB Age Synopsis ------ -- - -- --- --- ------------------------------------------------------- 124861 02 < 19 --- 73 Sun Studio 12: Compiler Common patch for Sun C C++ F77 F95 124863 01 < 23 --- 48 Sun Studio 12: Patch for Sun C++ Compiler 126495 01 < 04 --- 304 Sun Studio 12: Patch for debuginfo handling 124867 01 < 14 --- 45 Sun Studio 12: Patch for C 5.9 compiler 124870 01 < 03 --- 696 Sun Studio 12: Patch for Sun Performance Library 124872 01 < 07 --- 434 Sun Studio 12: Patch for dbx 7.6 Debugger 126995 01 < 04 --- 638 Sun Studio 12: Patch for Performance Analyzer Tools 127001 01 < 04 --- 374 Sun Studio 12: Patch for Fortran 95 8.3 Dynamic Libraries 127143 01 < 03 --- 741 Sun Studio 12: Patch for Fortran 95 8.3 Support Library 127000 01 < 13 --- 119 Sun Studio 12: Patch for Fortran 95 8.3 Compiler 128225 -- < 01 --- 401 Sun Studio 12: Patch for localization of Sun C C++ F77 F95 I used the following pca command to download and display the READMEs /var/tmp/pca --pretend /var/tmp/patchlist.txt --patchdir="/var/tmp/pcatmp" --safe --readme Each patch displayed the "NOT FOUND IN CROSS REFERENCE FILE!" but did download and display each README (note: the "pretend" failed.) Here is a sample of the console output: 124861 -- = -- --- 999 NOT FOUND IN CROSS REFERENCE FILE! Looking for 124861-19 (1/11) Found patch file Installing 124861-19 (1/11) Unzipping patch Checking files for safe patch installation Use of uninitialized value in split at /var/tmp/pca line 926. Use of uninitialized value in numeric eq (==) at /var/tmp/pca line 927. Use of uninitialized value in numeric le (<=) at /var/tmp/pca line 934. Skipped - pretend (12:23:55/00:00:03/00:00:03, 1/11, 0/1/0) Downloading README for 124861-19 Trying /var/tmp/pcatmp/124861-19.zip have a good day, Glen >>> Martin Paul <[email protected]> 6/16/2010 2:34 AM >>> Hi, > I've noticed with the latest production pca and the patchdiag.xref file > data June 14th, 2010 that a lot of patches aren't seen in the cross > reference file. > ... > 119079 13 > -- --- 999 NOT FOUND IN CROSS REFERENCE FILE! > ... > I am wondering if this is OK or there is something deeper wrong with the > new patchdiag.xref format that could be causing this. Nothing to worry about. You will see such patches on any installation of a Solaris update release. These are patches which are included in the original Solaris distribution, but which are not listed in the xref file. Here's a quote from Gerry Haskin's blog: http://blogs.sun.com/patch/date/20080609 There are a number of "special" or "script" patches included in each Solaris Update release. These patches are used to correct issues in how patches are pre-applied into the Solaris Update release image and have no purpose whatsoever outside of the Solaris Update release process. Therefore, these "special" or "script" patches are not released to SunSolve ... So you can just ignore those. Martin.
