Override file

As sometimes happens, you might identify errors in the patchdiag.xref file downloaded from the Oracle website.

Corrections are made in a separate override file, using the default name xref_content.info, which updates the patchdiag.xref file during patch analysis. The sample file showing the format is as follows:

138194|01|Jun/11/08| | | |  |Unbundled|i386;|SUNWservicetagr:1.0,REV=2007.05.21.20.36;SUNWservicetagu:1.0,REV=2007.05.21.20.36;SUNWstosreg:1.0,REV=2007.05.21.20.36;|Service Tags SunOS 5.10_x86
138215|01|Nov/11/08| | | |  |10|sparc;|SUNWesu:11.10.0,REV=2005.01.21.15.53;SUNWxcu4:11.10.0,REV=2005.01.21.15.53;|SunOS 5.10: sort patch
138216|01|Nov/11/08| | | |  |10_x86|i386;|SUNWesu:11.10.0,REV=2005.01.21.16.34;SUNWxcu4:11.10.0,REV=2005.01.21.16.34;|SunOS 5.10_x86: sort patch

Entries in the override file must be identical to the same entries contained in the patchdiag.xref file (with corrected information inserted). Entries in the override file supersede the corresponding entries in the patchdiag.xref file during creation and update of a patch catalog. The following fields cannot be overridden:

  • Patch ID
  • Version Number
  • Release Date

All other information can be overridden. New entries, which have no corresponding entry, are added to the patchdiag.xref file.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*