Skip Headers
My Oracle Support Help
Release 14.3

E25224-44
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

6 Patches and Updates

This document contains the following topics:

Note:

To access Patches & Updates from https://support.oracle.com, the following sites must be accessible through your firewall:
  • support.oracle.com (https, port 443)

  • updates.oracle.com (https, port 443)

  • aru-akam.oracle.com (port 80)

6.1 Patching Quick Links

The Patching Quick Links region provides quick access to other media sources, patch sources, or documents related to patches. The Sun Product link provides access to Knowledge Document 1289614.1, "Sun Patches and Updates Information Center":

https://support.oracle.com/rs?type=doc&id=1289614.1

Note:

If you do not have download privileges, you will see only the Oracle Software Delivery Cloud (formerly eDelivery) and Sun links.

6.2 Patch Searches

You can use the Patch Search region to search for patches for Oracle, PeopleSoft, Sun, Siebel, and Hyperion products. The advanced search option enables you to create complex searches for patches for these products.

Note:

For information about how to find and download a Siebel maintenance release, fix pack, or quick fix from My Oracle Support, see Knowledge Document 975535.1:
https://support.oracle.com/rs?type=doc&id=975535.1

6.2.1 Searching by Patch Name, Number, or Bug Number (Simple)

If you already know the patch number, this is the fastest way to retrieve the corresponding patch. It is also possible to search for multiple patches by entering multiple patch numbers separated by commas.

Note:

When searching for Sun patches in the 6-2 format, you can use an asterisk (*), the percent sign (%), or nothing after the - as wildcards in the form XXXXXX-*, XXXXXX-%, or XXXXXX-, for example: 112233-*, 112233-%, or 112233-.

To search for a patch using the patch number:

  1. In the Patch Search region, select Name/Number or Bug Number (Simple). For the filter, select Patch Name or Number.

  2. Enter one or more patch numbers in the text entry field. If multiple numbers are entered then they must be separated by commas.

  3. If desired, select either Platform or Language. You may need to click the plus (+) sign to add this filter.

    Note:

    You can search by either platform or language, but not both. If you select Platform, you can specify up to five platforms.
  4. To view only the patches that have not been replaced with a later patch, select Exclude Superseded Patches. After you perform the search, no superseded patches are listed in the Patch Search Results window

  5. Click Search. The Patch Search Results list appears.

    If you click a row, the context bar appears which enables you to view the readme file, download the patch, and if you have configurations create a plan. If you select more than one row by using the control or shift keys, you can download multiple patches or add multiple patches to a plan. When multiple rows are selected the Readme button is disabled on the context bar.

  6. Click the patch number link to view detailed information about a patch in the results list.

    From the patch details area, you can download the patch, view the readme, view bugs resolved by the patch, and if you have configurations create a patch plan. You can also view replacement or superseded information, related Knowledge documents and Community reviews, and download trends and certification and recommendation information for that patch if applicable. You can also view patches with the same name for different releases, platform, or languages where applicable.

6.2.2 Searching by Product or Family (Advanced)

If you do not know the patch numbers, you can search for patches that are specific to a particular release of a product or product family. There is no difference in the way the search is performed for products or product families, only the results of the search differ. To search by product/product family:

  1. In the Patch Search region, select Product or Family (Advanced).

  2. If desired, select:

    • Include all Products in a Family

    • Exclude Superseded Patches

      After you perform the search, no superseded patches are listed in the Patch Search Results window

  3. Click in the Product box, enter a product or partial product name, then select a product from the Product menu (required).

    Note:

    In the past, slightly different names were used for a product in different parts of My Oracle Support, for example, Oracle Database was RDBMS Server in Patches & Updates Advanced Search and Oracle Database - Enterprise Edition in Service Requests.

    Oracle has updated product names to make them consistent across My Oracle Support. For example, now Oracle Database is Oracle Database - Enterprise Edition in most parts of Patches & Updates and Service Requests. However, if you previously saved a patch search with a previous name, for example RDBMS Server 12.1.0.1.0, in most cases My Oracle Support automatically maps to the new name.

  4. Select up to 10 releases from the Release menu (required). This menu is disabled until a valid product or family name has been selected.

  5. If desired, select up to five platforms from the Platform filter.

  6. If desired, specify additional filters. Click the plus (+) sign to add more filters.

  7. Click Search. The Patch Search Results list appears.

    If you click a row, the context bar appears which enables you to view the readme file, download the patch, and if you have configurations create a plan. If you select more than one row by using the control or shift keys, you can download multiple patches or add multiple patches to a plan. When multiple rows are selected the Readme button is disabled on the context bar.

  8. Click the patch number link to view detailed information about a patch in the results list.

    From the patch details area, you can download the patch, view the readme, view bugs resolved by the patch, and if you have configurations create a patch plan. You can also view replacement or superseded information, related Knowledge documents and Community reviews, and download trends and certification and recommendation information for that patch if applicable. You can also view patches with the same name for different releases, platform, or languages where applicable.

    Note:

    It is highly recommended that users install Patchsets, Patch Set Updates (PSUs), Software Patch Updates (SPUs) (formerly known as Critical Patch Updates (CPUs)), and Mini and Maintenance Packs instead of patches that include only a single update. Patches that include only a single update should be installed only when the update addresses a specific issue that has been identified on the target system.

6.2.2.1 How do I limit my search to patches updated since a specified time or within a date range?

To search for patches updated in the last n days, weeks, or months:

  1. In the Advanced Search area, select the Updated filter.

  2. Select In the Last.

  3. Select Days, Weeks, or Months from the menu, then enter a number in box next to the menu.

To search for patches within a specified date range:

  1. In the Advanced Search area, select the Updated filter.

  2. Change In the Last to Between.

  3. Enter a start and finish date. You can enter the dates directly in the date boxes, or click the calendar icon to specify the date range.

Your search is now constrained to patches updated in the time or between the dates specified.

6.2.2.2 What do I enter for Product or Product Family?

The product name used by the patch system is the same as the product name used for service requests or the Knowledge base. To find the product name, start entering the product name that you are looking for in the Product box and the product selector will narrow down the choices to help you find the right product. For example, to find the product Oracle Database - Enterprise Edition, you can enter ”Oracle Database”, ”Database”, or even the alias ”RDBMS” and the product selector will offer choices that match the terms that you entered. It is not possible to select multiple products or product families for a search.

6.2.2.3 Why can't Platform and Language be selected at the same time?

Platform and Language refer to the system that is being patched. Patches are specific either to a platform or a language. This setting is optional. If it is not set then all platforms and languages for a patch will appear.

Use the drop-down menu to select the platform (operating system and hardware architecture) used to deploy your Applications. The platform patch is by default the English language patch. You can choose multiple platforms or multiple languages.

The platform does not necessarily match the word-size of the operating system. For example, you can have 32-bit software installed on a Solaris 64-bit OS. The correct platform to select in this case is Solaris 32-bit because the patch MUST match the word-size of the installation, not the word-size of the operating system.

By default, patches for Generic Platform will be included in the search results. Patches for Generic Platform are platform independent and can be applied to any platform.

Tip: Search for the language for a patch when you know the patch also has language packs.

Note:

For Oracle Applications Release 11i on HP-UX PA-RISC, IBM AIX, and Sun Solaris SPARC, queries will return a 32-bit patch. This patch may be applied to both 32-bit and 64-bit operating systems.

For Oracle Applications Release 12 on Linux x86-64, queries will return a Linux x86 patch. This patch may be applied to both 32-bit and 64-bit operating systems.

6.2.2.4 When searching by Product or Family, are patch search product names identical to Knowledge product names?

Yes. Patch search product names are identical to Knowledge product names.

6.2.3 Filtering Search Results

To filter search results, click the plus (+) icon to add search filters. You can filter by language or platform in the simple search. Use the advanced search for more filters.

6.2.4 Searching for Specific Products or Platforms

6.2.4.1 How do I search for BEA Smart Update patches in My Oracle Support?

For information about searching for BEA Smart Update patches, see Knowledge Document 1302053.1, "How to Locate and Download Patches for WebLogic Using MOS?":

https://support.oracle.com/rs?type=doc&id=1302053.1

6.2.4.2 How do I search for Sun patches in My Oracle Support?

Most Sun patches have migrated to My Oracle Support and are available for searching and downloading. In the Patch Search region, use Advanced Search to search by product or product family.

Note:

Searches for Sun patches using the simple search support exact matches. In addition, when searching for Sun patches in the 6-2 format, you can use an asterisk (*), the percent sign (%), or nothing after the - as wildcards in the form XXXXXX-*, XXXXXX-%, or XXXXXX-, for example: 112233-*, 112233-%., or 112233-.

For information about available Sun patches, see Knowledge Document 1289614.1, "Sun Patches and Updates Information Center".

https://support.oracle.com/rs?type=doc&id=1289614.1

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.

Some Oracle terminology differs from Sun terminology, for example:

  • An obsolete patch for Sun products corresponds to a superseded patch for Oracle products. A superseded patch is a patch for which a later revision is available. Patches are cumulative, so newer patches contain all of the fixes and features of the patches which they supersede.

  • A withdrawn patch in Sun terminology is called an obsolete patch in Oracle terminology. An obsolete patch (using Oracle terminology) is a patch which is no longer available for download, for example, because it was defective.

Note that the naming convention and content of the Sun patches have not changed. For example, a Sun patch in My Oracle Support may have the classification superseded within My Oracle Support, but Sun's SVR4-based patch architecture uses the pre-existing terminology, SUNW_OBSOLETE, in the pkginfo files and the patch read me file.

The following table maps Sun search methodologies to My Oracle Support patch searches:

Sun Microsystems Search My Oracle Support Search
Search by Sun Patch ID Search by Patch Name or Number (simple search)
Search by OS Release Search by Product & Release (advanced search)
Search by Architecture Search by Platform (simple/advanced search)
Search by CR number (Bugster BugID) Search by Bug Number (simple search)
Search by Product Search by Product (advanced search)
Search by Synopsis Search by Description (advanced search)
Search by Released After date Search by Last Updated (advanced search)
Search for patch clusters Search for patchsets (advanced search)
Search for firmware Search by Product & Release (advanced search)

To search for Sun patchsets (formerly Sun patch clusters):

  1. In the Patch Search region, click the Product or Family (Advanced Search) link. The Advanced Search window appears.

  2. Set Product to Solaris Operating System.

  3. Select a release.

  4. Select Type from the third menu.

  5. Set the type to Patchset, then click Search.

    Note:

    You can find the recommended patchsets for Solaris 9 and 10 in the Patches & Updates Recommended Patch Advisor

    Note:

    For more information about Sun patchsets, see Knowledge Document 1272947.1:
    https://support.oracle.com/rs?type=doc&id=1272947.1
    

6.2.4.3 Can I search for patches for products that are part of a specific release of E-Business Suite R12?

To search for patches for E-Business Suite R12 products, click Product or Family (Advanced Search) in the Patch Search region. Select a product name from the Product menu, then select Applications R12.1, Applications R12.0, Applications R12 (Other), or Applications 11i from the Release menu.

For E-Business Suite R12 products, sometimes patches for different releases have the same patch number. Use the Release column in the search results to verify the correct release. In addition, the release is listed on the right side of the patch details page. If there is more than one release available you can use the list to switch to the other available releases.

6.2.4.4 Can I search for JD Edwards patches?

Yes. You can find patch searches for JD Edwards products in the Patching Quick Links region. Searches performed using this interface will not result in updates in the Recent Activity or Recent Search regions. You cannot find JD Edwards patches by searching from the Patch Search region.

6.2.4.5 Where do I search for Sun Firmware, BIOS and related updates, Solaris patches, and Solaris recommended patch sets?

You can search for Sun patches and updates from both the simple and advanced searches in the Patch Search region. In addition, the Quick Links region includes a Sun link which takes you to Knowledge Document 1289614.1, "Sun Patches and Updates Information Center":

https://support.oracle.com/rs?type=doc&id=1289614.1

Note:

Use simple search to search for a revision of a 6-2 patch. You can use an asterisk (*) or the percent sign (%) as a wildcard in the form patchid-* or patchid-%, for example: 112233-* or 112233-%.

6.2.4.6 Where do I search for Sun patches and updates?

You can search for Sun patches and updates from both the simple and advanced searches in the Patch Search region. In addition, the Quick Links region includes a Sun link which takes you to the Sun Patches and Updates Information Center:

https://support.oracle.com/rs?type=doc&id=1289614.1

6.2.4.7 Where can I find the Sun patch readmes?

Patch readmes are available from the Patch Details page and from the context bar from the Patch Search results listing when only one patch is selected.

6.2.5 Searching Using Configurations Based Recommendations

Note: Patch recommendations are only available to customers using the configuration manager release 10.3.2 or higher. This feature is available as part of your support contract.

6.2.5.1 View Recommendations

Patch recommendations identify configurations that are uploaded through the configuration manager release 10.3.2 or higher that are missing recommended patches issued by Oracle. Oracle compares the patches installed in your configuration with what Oracle recommends, and identifies any missing patches. It is important to ensure that the configuration manager send updates to Oracle daily. Check the status of your configuration managers from the Targets and Systems regions on the Dashboard tab.

For example, an SPU released quarterly, is a bundle of patches that provides security fixes for Oracle products. Oracle issues SPUs for vulnerabilities in supported products that compromise data confidentiality, data integrity, and system availability. To ensure a secure environment, Oracle urges you to acquire and implement SPUs promptly. Patch recommendations will show if the SPU is missing from your systems that were uploaded using the configuration manager.

As part of the initial planning phase, use Patch Recommendations to identify and prioritize targets missing an SPU. Using Patch Recommendations details, review the SPU Advisory to assess the criticality of a patch and any pre-requisite patches. Use My Oracle Support to download the patches. You can then deploy the required patches using Enterprise Manager or similar product.

6.2.5.1.1 What is the Patch Recommendations region?

The Patch Recommendations region provides a portal to all recommended patches that are applicable to uploaded configurations. From the bar graph, you can drill down to a list of recommended patches, view details about those patches, download the patches, or add them to a patch plan. The bar graph summarizes the number of issues found (for example, if there is one issue, then there is one recommendation for one target).

For more information about patch recommendations, see "Searching Using Configurations Based Recommendations".

6.2.5.1.2 Why are there no recommendations? I am sure there should be some.

While we hope you have zero recommendations because all recommended patches are applied, there can be other reasons no recommendations appear.

  • The targets on which you have configuration managers do not have published recommendations. Currently, recommendations are available for Database, Enterprise Manager, and Application Server targets. Future releases will include other Oracle products.

  • The product, platform, and version do not have any patch recommendations (for example Oracle Database 10.2.0.3 on Windows).

  • For Oracle Database, the configuration manager is installed but the database is not instrumented. The Oracle Home is present but feature usage metrics are not available which are needed to provide recommendations. See the Oracle Configuration Manager Installation and Administration Guide for more information. This section does not apply if you are accessing My Oracle Support from within Oracle Enterprise Manager.

  • You have suppressed all of the recommendations. If you see the View Suppression link, then some patches are suppressed. Click View Suppression to review and un suppress recommendations, as required.

  • You must use configuration manager 10.3.2 or higher. If you have turned off automatic updates, it is possible that an older version of the configuration manager is being used.

  • All applicable patch recommendations are applied.

  • If you edit the Patch Recommendations region to show recommendations for target types that are not support by patch recommendations, the number of recommendations is zero.

  • There is no uploaded configuration information.

Note: Currently, My Oracle Support provides patch recommendations for the following product lines:

  • Oracle Database

  • Oracle Application Server

  • Enterprise Manager Cloud Control (Management Agent/Oracle Management Service)

  • Oracle Fusion Applications

  • Oracle Fusion Middleware

  • Oracle SOA Suite

  • Oracle Real Applications Clusters

  • Oracle Real Applications Clusters with Clusterware

  • Oracle Dataguard

  • Oracle Exadata Database Machine and Exadata Storage Serve

  • Oracle Exalogic

  • Oracle Coherence, Oracle WebLogic Server, Oracle JRockit for non-Exalogic systems

  • Oracle Business Process Management

  • Application Development Framework Runtime

Oracle is committed to expanding coverage to other product lines. In the meantime, use the Patching Quick Links region to access the legacy patch searching sites to get patch information for other product lines.

6.2.5.1.3 How can I view all patches associated with a target type or a classification?

The Patch Recommendations region displays a graphical and numeric summary of patches either by patch classification or by target type. Click a bar graph to drill down to a full list of patches for a target type or classification.

Click All Recommendations to view the complete list of all available patches on the Patch Recommendations page. If you have suppressed any patches, click View Suppressed Items to view a list of patches that you have suppressed.

Use the filter on the Patch Recommendations page to select a particular classification.

6.2.5.1.4 How can I filter patch recommendations?

To filter patch recommendations, select options from the filter menu. You can select more than one filter. Select an option again to deselect the option.

6.2.5.1.5 How can I search for a patch recommendation?

To search for a patch recommendation:

  1. Select a category from the search menu, for example Target Name.

  2. Enter search criteria in the search box, then click the search icon.

6.2.5.1.6 Why is configuration manager version 10.3.2 or higher required for patch recommendations?

Configuration manager 10.3.2 and higher collects additional information about patches applied to your environment, which is critical for providing patch recommendations. Without the additional information, Oracle cannot provide patch recommendations or replacement patches to resolve conflicts through the Patch Plan tool. The configuration manager usually updates automatically. If it does not update automatically, update the configuration manager manually by following the instructions in the Oracle Configuration Manager Installation and Administration Guide:

http://www.oracle.com/technetwork/documentation/ocm-092152.html

To determine what configuration manager version you have:

  1. From the Targets region on available on the Dashboard tab, find all targets of type Oracle Configuration Manager.

  2. Click each link to the target's home page.

  3. Note the Oracle home and host information to understand which configuration manager the information applies to.

  4. Select the CCR Package Versions metric in the Configuration region.

  5. Look at the scripts Package Name row for the value in the Package Version column. This is the version of the configuration manager. It should be 10.3.2 or higher.

6.2.5.2 Suppress Recommendations

6.2.5.2.1 Learn about patch recommendation suppression

Suppression enables you to either temporarily or permanently hide a patch recommendation. It is simply a method of hiding recommendations that you do not want to look at right now. For example, you may chose to suppress patches for a development system or called an issue. Suppression reduces the number of recommendations which appear in the Patch Recommendations region.

There are three suppression options:

  • Suppressed Targets- all recommendations for a specific target

  • Suppressed Patches - a specific patch for all targets

  • Suppressed Issues - a specific patch found on a specific target

Depending on which option is selected, suppressed items will appear in the appropriate tab when View Suppressed Items is selected.

You can select one or more rows. Or you can use the standard Control and Shift key combinations to select a range of recommendations by clicking anywhere else on the rows (except on a link). The Suppress button menu will keep track of the number of unique issues, targets and recommendations you have selected.

Additional information about the three types of suppression:

  • Suppressed Issue: Suppression of a specific issue means you will not see this recommendation for this target. This is the smallest type of suppression: One patch recommendation for one target. So, you might suppress a recommendation for a development target, but keep it active for a production target. Being the smallest type of suppression, it can be over-ridden by the other two types of suppression. When this suppression is done, the issue is suppressed only for that target

  • All Patch Recommendations for Target: You will not see any patch recommendations for that target. This is most useful for a development server. No matter what you do on this target, you will not see recommendations now or in the future unless the recommendations are unsuppressed.

  • All Occurrences of the Recommendation: Suppress any occurrence of a specific recommendation. This is useful when the patch recommendation will never apply to your environment. Maybe you are in a secure location with no direct Internet connection so patch recommendations related to Internet security might be suppressed. This means even new targets added to your environment at a later date would not show this recommendation.

On the Suppressed Targets and Suppressed Recommendations tabs on the Suppression page, each item listed will have a number which is linked. It will show you the number of recommendations or targets suppressed. Clicking the number will list the details. This way, you can check on a recommendations impact without unsuppressing it.

6.2.5.2.2 How do I suppress patch recommendations?

To suppress patch recommendations:

  1. On the Patch Recommendations page, click a patch recommendation row to select the patch recommendation. Select more than one patch, if desired.

  2. Click Suppress on the context menu.

  3. Choose to suppress the selected patches (Issues), patch recommendations for the targets of the selected patches, or all occurrences of the selected patches.

  4. Click View Suppressed Items, then click on the relevant tab to view the suppressed patches.

Tips for Suppression

  • Triage your issues for inclusion into your next patch deployment window. Use suppression to hide items which you want to do in a later window. Use the Suppressed Since column in the Suppression tables to multiple select and unsuppressed a collection of issues you deferred previously.

  • Suppress targets which you do not manage so your focus is on your targets and systems. You can multiple select recommendations from different groups that you do not manage, and then choose the Suppress button menu and choose the second option (All Patch Recommendations (Current & Future) for the Targets).

6.2.5.2.3 How do I unsuppress patch recommendations?

To unsuppress patch recommendations:

  1. Click View Suppressed Items.

  2. Select the relevant tab.

  3. Select a patch recommendation to unsuppress.

  4. Click Restore Recommendation.

6.2.5.2.4 Will my suppressions be seen by others on my team?

No. Your suppression settings affect only your account.

6.2.5.2.5 How does suppression affect the counts on the patch recommendation charts?

Suppression enables you to either temporarily or permanently hide a patch recommendation. It is simply a method of hiding recommendations that you do not want to look at right now. For example, you may chose to suppress patches for a development system or called an issue. Suppression reduces the number of recommendations which appear in the Patch Recommendations region.

The counts on the patch recommendation charts are for issues. That is one issue equals a specific recommendation for one target. So suppressing an entire target could result in a large reduction in issues in the count. Likewise, suppressing a patch recommendation could result in many issues being removed from the counts.

Click View Suppressed Items to view the Suppressed Recommendations page.

6.2.5.3 Print Recommendations

To print recommendations, drill down into the Patch Recommendations bar to display the table of recommendations. Click the table icon in the far left to print. Doing this will generate a printer-friendly table of patch recommendations.

6.2.6 Using the Recommended Patch Advisor

The Recommended Patch Advisor enables you to quickly find recommended and mandatory patches for standalone products, product combinations, or products for a product stack. There is currently a limited set of data available. Additional data will be added in the future. If a product or release is not selectable, that means that no data is currently available.

Type ahead features are support so that you can enter a partial product name rather than searching through the full list.

If you select a product from the list, the search will return at least one result. When a product selection is made for products used together and the first product selected does not have any recommended patches, a second product selection must be made. If the product is not found, then no patch recommendations exist in the Recommended Patch Advisor.

6.2.6.1 What do I do if I cannot find the product I am interested in under the Recommended Patch Advisor selection?

You can use the Product or Family (Advanced Search) to search for recommended patches for products not available under the Recommended Patch Advisor search. To do this, search using Product or Family (Advanced Search) and ensure that the Classification filter is used with values set for one or more of the Critical, Security, Legislative, or Other Recommendations categories.

6.2.6.2 Are there shortcuts for finding recommended patches?

Recommend patches for some products are linked in the Patching Quick Links region, including:

  • Recommended R12 Patches -provides the list of recommended patches for the E-Business Suite R12 product

  • Recommended 11i Patches - provides the list of recommended patches for E-Business Suite 11i product

6.2.6.3 How do I find mandatory patches for certifications?

In addition to returning recommended patches, an icon in the Recommended Patch Advisor search results indicates that a patch is mandatory for certification. Often, a patch is listed as mandatory when you search for a product used with another product. There is no special query for mandatory patches; they are returned automatically as part of a search. Select a patch to drill down to the Recommendations / Certifications section for more information about the patch.

6.2.6.4 What do I do if I do not want to perform a search but I would like to know exactly what recommended patches I am missing?

You can use the Oracle Configuration Manager to upload configurations to Oracle Support. After an upload is completed, Oracle Support will assess the configuration uploaded and identify all missing recommended patches at the point of upload. The recommended patches can then be viewed through the Patch Recommendations region in the Dashboard or in the Patches & Updates tab. Click All Recommendations to view missing recommended patches for the configurations uploaded.

6.2.6.5 How can I use aliases to find products in the Recommended Patch Advisor?

Understanding the names of the products can sometimes be challenging. For example, you might be used to referring to Oracle Database, but from the patching perspective Oracle Database is called RDBMS Server. Oracle is working to ensure that you can enter multiple terms to find a single product. In many My Oracle Support systems, aliases enable you to find a product even if Oracle changed the name of the product. In addition, many shorthand terms, for example DB for Oracle Database, are included as aliases so you can enter common shorthand terms to find the correct product.You can use these aliases through the type ahead feature to narrow the product search, or use the aliases to identify products from the product list.

Note: Product names in the Recommended Patch Advisor search may be different from the product names in the Product or Family (Advanced Search) or from the results for Number/Name or Bug Number (Simple) search.

6.2.7 Sharing a Search Results Link

To save or share a link to the Patch Search Results page for a specific patch search, click Share Link. A window opens with a link to your specific search. You can copy this link and store it in a document or email it to a coworker, for example.

6.2.8 Frequently Asked Search Questions

6.2.8.1 Why do I search for a product by one name and then use another name elsewhere?

Oracle is in the process of standardizing product names. Until then, product names might vary in different areas. For example, you might see "Oracle Database - Enterprise Edition" in one place, but search for "Oracle Database" in another. If you don't find a product, try searching by another name that you might use for the product.

6.2.8.2 How can I see a list of my previous searches?

In the Patch Search region, click the Recent tab to view a list of searches that you have run. The historical list of searches provides the search method (number or product family), patches searched for, along with a time stamp.

The Recent tab in Patch Search displays the previous 20 searches. The search list can be sorted alphabetically or chronologically.

You can save up to 20 searches. Access saved searches through the Saved Searches tab.

6.2.8.3 Why search by patch type?

The Patches and Updates tab enables you to view and download recommended patches and updates for your Oracle products. You can download the following patch types:

  • Interim patches - contain a single bug fix or a collection of bug fixes provided as required

  • Interim patches for security bug fixes - contain customer-specific security bug fixes

  • Diagnostic patches - intended to help diagnose or verify a fix or a collection of bug fixes

  • Bundle Patch Updates (BPUs) - a cumulative collection of fixes for a specific product or component

  • Patch Set Updates (PSUs) - a cumulative collection of high impact, low risk, and proven fixes for a specific product or component

  • Security Patch Updates - a cumulative collection of security bug fixes

  • Sun hardware and firmware

Oracle recommends that users apply patchsets instead of individual patches. Because of the very large number of individual patches, limiting the search for patchsets provides faster results.

6.2.8.4 Is searching by description the same as the title of the patch?

Yes. Patch search automatically implements a 'contains' search which finds any word that matches your entry in the description of the patch. It will not search the patch name or ID field. Some examples are, SPU, ORA-00600, Incorrect Value.

Note:

Searching by Description should not be relied upon as the only way for finding patches because the naming conventions for patches can change over time.

6.2.8.5 How do I find the latest PSU or SPU?

To find the latest PSU or SPU, do one of the following:

  • Select Recommended Patch Advisor, select Oracle Database or RDBMS from the Product list, select a release, then select a platform (optional).

  • Select Advanced Search, select Oracle Database or RDBMS from the Product list, select a release. select a platform (optional), then set the description to contains PSU or SPU.

  • Select Advanced Search, select Oracle Database or RDBMS from the Product list, select a release. select a platform (optional), then select Security (for SPU) or Other Recommendations (for PSU) from the Classifications list.

You can also use the Critical Patch Updates and Security Alerts link in the Patching Quick Links region. This link will take you to the latest information on CPUs and security alerts.

6.2.8.6 What are the different patch classifications?

Patches are categorized into the following types:

  • Critical: An E-Business Suite patch which is necessary for smooth functioning of the application. Critical patches should be installed immediately. Critical patches are always recommended.

  • General: A patch which is not in any other classification, typically these are one-off patches which solve a specific business issue for a customer.

  • Other Recommendations: Any Security, Legislative, and Recommended patches. It is highly recommended that users apply all recommended patches.

    Note:

    This does not apply to PeopleSoft.
  • Security: Patches that address security vulnerabilities in a product.

  • Legislative: These patches are necessary for accurate calculation of values which might have changed over time in the application (for example, tax tables for the new year, or withholding calculations for salaries).

  • Superseded: A patch that has been replaced by a more recent patch. The Superseded region lists the superseded patch and the replacement patch. You should use the replacement patch.

    Note:

    You can search for a superseded patch if you know the bug number or patch ID. In addition, a product search will find a superseded patch.
  • Obsolete: A patch that has been retired. Use the patch listed under Replacement Options.

    Note:

    You can search for an obsolete patch if you know the bug number or patch ID. Product searches do not find obsolete patches.

6.2.8.7 What are the different search filters?

You can specify criteria for the following search filters. Only the Platform and Language filter are available for Number/Name or Bug Number (Simple) searches. For the Product or Family (Advanced) search, not all filters are applicable depending on the product that you specify.

Note:

The default filter is Any. If a filter is not set or selected that filter is not included in the search criteria.

Classification

Classification limits the results by the importance of the patch. If you do not set a classification then all patches are searched including patches which have a the general classification. The searchable classifications are:

  • Critical: A patch which is necessary for smooth functioning of the application. Critical patches should be installed immediately and are always recommended.

  • Security: Patches that address security vulnerabilities in a product.

  • Legislative: Patches required for accurate calculation of values which might have changed over time in the application (for example, tax tables for the new year, or withholding calculations for salaries).

  • Other Recommendations: Any recommended patch not covered by the Critical, Security or Legislative classifications. You should apply all recommended patches.

  • General: A patch which is not in any other classification.

Compatible Codeline (R12 Only)

Compatible Codeline limits results to patches that are compatible with the codeline of your Oracle E-Business Suite (application) installation, for example, R12.FIN_PF.A or R12.SCM_PF.B.

Note:

This is an optional filter. If you do not choose a codeline, the search returns all of the patches for the selected release.

Description

Specify text in the Description box to limit the search results to patches with a description (or synopsis in the case of Sun patches) containing the entered text. For example Patch 11i.MSD or 5.9_x86 or booking. The Description field is not case-sensitive search. Wild cards such as * or % are not needed.

Note:

Because patch naming conventions can change over time, limiting results by text occurring in the description or synopsis should not be used as the sole filtering parameter.

Includes File (Applications Only)

Includes File limits the results to patches containing a specific file, a match on a partial file name, or a specific version of a file. This filter is only valid for Oracle E-Business Suite (application) searches, for example GenCartComm.java; version: 11.5.3.

The search can be further limited by specifying the exact file version. No wildcards are allowed for the version filter. Leave Version empty to match all file versions.

Language

Specify one or more languages to limit the results to patches for the specified languages. Use the drop list to select the languages of your application instance.

Note:

English is always included with a platform-specific patch and must be installed before installing any language patches expect for PeopleSoft products where you must select either American English or one of the translations (including UK English) but not both.

Not Included in Patchset (11i & R12 Only)

Not Included in Patchset is only valid for Oracle Applications searches. It limits the search to patches that are known to not be include in, or are superseded by, the specified patchset. This search filter helps return results that are still relevant after installing a larger patchset. Select one or more items from the list.

Patch Target

Patch Target limits the results to patches for feature, component, or task selected.

For example, choose Data Guard when you are only interested in Data Guard patches for the database. Select FMW - OC4J when you are searching for Fusion Middleware (iAS) patches related to OC4J.

Note:

Use caution when specifying a patch target. If you use patch target, you may not receive the results expected.

Platform

Specify up to five platforms to limit the results to specific operating systems.

Note:

Oracle Applications release 11i 32-bit patches returned on HP-UX PA-RISC, IBM AIX, and Sun Solaris SPARC may be applied to both 32-bit and 64-bit operating systems.Linux x86 patches returned when searching Oracle Applications Release 12 on Linux x86-64 may be applied to both 32-bit and 64-bit operating systems.

Product

Product is a required field. Select a product from the list of values.

Type

Specify a type to limit the search results to either patches or patchsets.

  • Patch: A single update addressing a single issue. Patches should only be installed when an issue is listed in the Read Me that is not resolved by an existing Patchset.

  • Patchset: A collection of updates, for example, a Sun patch cluster/bundle.

Note:

Where possible, you should apply patchsets instead of individual patches.

Updated

Updated restricts the search to patches that were updated within a specified timeframe.

Note:

An update can be as minor as a change to the readme.

6.3 Patch Details

6.3.1 Viewing Related Knowledge Documents

6.3.1.1 What is related knowledge for a patch?

Oracle tries to provide any and all information which might help you make an informed decision about when and what patches to apply. We expose the bugs resolved by this patch and do a search against the knowledge base to see if any articles or documents might relate to this patch. You can read these and then quickly return to the patch to make an informed decision.

6.3.1.2 What is the Recommendations / Certifications section on the Patch Details page?

The Recommendations / Certifications section in the Patch Details page lists information about which products the patch is recommended for and whether the patch is mandatory for certification. For patches with certification information, click a certification link to view the certification. The section appears only if a patch being viewed has related recommendation or certification information.

6.3.2 Viewing Trends and Downloads

6.3.2.1 Why do some patches have download trend data, some do not?

When possible, we show the recent history of how many times a patch has been downloaded by our customers. You might find this useful to help determine when and if to install a patch. For security patches, this information is not shared with the community.

6.3.3 Viewing Community Feedback

6.3.3.1 What is a patch review and why display them?

Patch reviews are feedback from customers regarding individual patches and platform combinations. To help ensure Oracle provides patches that work in the largest number of customer environments, we have provided patch reviews as a feedback channel that connects you with the development and support teams responsible for patch development.

6.3.3.2 Can I reply to an existing posted review? I see a number of great responses to my original review.

Yes. From the Community Discussion area in the Patch Details region, click Reply to Discussion then add your additional comments.

You can also reply from the main Community site. Search for the patch and reply to the thread. Note that each patch and platform combination has a separate thread. After you locate the thread, you can reply to any of the posts.

6.3.3.3 Why show community feedback on a patch page?

It can be difficult finding the right patch. We encourage you to voice your opinion and expertise in the community spaces. By linking the spaces directly to a patch, we want to encourage the community to help improve patch quality and share any tips and tricks which might help other community members. Oracle will also work to incorporate your feedback.

6.3.3.4 I posted to the community and now I don't see it?

Patch spaces are created to group each patch by product for each platform. This is to avoid comments which are platform specific (such as install instructions) from cluttering the posts. Make sure you are looking at the correct platform for this patch.

Patch threads are automatically generated by a customer's first post. A patch thread for a specific patch/platform can only be created from within the Patches Detail page. The space is also available in the main Community site. Any additional threads from the main Community site will also appear on the Patch Details page. If you created your own topic thread in the main Community site, it would not be linked to this page. Also, if you posted something inappropriate, it might have been removed.

6.4 My Oracle Support Conflict Checker Tool

The My Oracle Support Conflict Checker tool, available from the Patch Search results page, enables you to upload an OPatch inventory and check the patches that you want to apply to your environment for conflicts.

If no conflicts are found, you can download the patches. If conflicts are found, the tool finds an existing resolution to download. If no resolution is found, you can request a solution and monitor your request in the Plans region.

For more information, see Knowledge Document 1091294.1, "How to use the My Oracle Support Conflict Checker Tool".

https://support.oracle.com/rs?type=doc&id=1091294.1

6.5 Patch and Upgrade Plans

6.5.1 Working with Plans

There are two types of plans, patch plans and upgrade plans.

Note:

Patch plans are currently not available for hardware system or operating system patching.

Note:

Plans are only available when using the configuration manager 10.3.2 or higher. See Chapter 9, "Collector" for more information.

If you are not using the configuration manager, you can still use the My Oracle Support Conflict Checker Tool against an OPatch inventory file, which could result in a plan. See the "My Oracle Support Conflict Checker Tool" section for more information.

Patch Plan

A patch plan is a collection of patches which you might want to consider applying as a group to one or more targets. Each target can have a separate group of patches. A patch plan can include a description and a deployment date for the plan and one or more patches. A patch can be added to a target in a plan only if the patch has the same release and platform as the target to which it is being added. You will receive a warning if the product for the patch being added is different from the product associated with the target to which the patch is being added. The warning does not prevent you from adding the patch to the plan.

You can include any patch for any target in a plan. The plan also validates Oracle Database, Fusion Middleware, and Enterprise Manager patches against your environment to check for conflicts with installed patches.

Upgrade Plan

An upgrade plan is similar to a patch plan. It is primarily used for planning an upgrade from a one release to another release of the same product on the same platform. In addition to including patches, it contains the media and patch sets required for the upgrade. Upgrade plans can only be created for a single target.

Upgrade planning enables you to determine the patches and software required to upgrade from an installed product release to another product release on the same platform. Upgrade planning is only available for customers who use the collector, unless you are accessing My Oracle Support from within Oracle Enterprise Manager. Not all target types are currently supported, but targets are constantly added. When you specify a target, the Upgrade Planner will analyze the configuration details of the selected target and provide you with:

Upgrade planning uses a target as the starting point for creating a plan. When you specify a target, the Upgrade Planner analyzes the configuration information of the target and provides you with:

  • Required Software

  • Recommended Patches

  • Patches for the new release to match existing patches found on your old release

After you select an upgradable target, the list of currently supported releases available for you to upgrade to is displayed. When you select a release from the list, support details are displayed to help you choose an appropriate release. For example, if the release has the status Terminal Release, you know that no new releases on this line of products will be produced. The patch information is provided to help you judge the impact of your upgrade decision.

As with patch plans, upgrade plans are analyzed for conflicts. If conflicts are found, users can request a new patch and replace the current patch when the requested replacement patch becomes available. Upon replacement, re-analysis is required.

6.5.2 Using the Plan Wizard

The Plan Wizard enables you to create, view, and modify plans. When you create an upgrade plan, select an upgrade or patch plan from the Plans region, or view a plan, the Plan Wizard opens.You can open the wizard by clicking View Plan from the message center after you create a patch plan from patch recommendations, the patch search region, and the patch details region.

6.5.2.1 Step 1: Plan Information

Note:

You must use a unique name for each plan.

To update general information about the plan, click Step 1: Plan Information. If you know the planned deployment date, you can enter it here.

Step 1 also provides a list of documents relevant to the plan, if available. Click a document link to view the document in the Knowledge Base. For Upgrade Plans, view the "Oracle Support Upgrade Advisor" document for a list of available upgrade advisors:

https://support.oracle.com/rs?type=doc&id=250.1

Upgrade advisors are dynamic documents that guide you through an upgrade lifecycle using step by step instructions. Each upgrade advisor is specific to a particular upgrade path of a product or suite between specific versions.

6.5.2.2 Step 2: Patches

For upgrade plans, any recommended patches for your configuration are automatically added to your plan, in Step 2: Patches. In addition any patches that you added manually are listed as well as suppressed patches, (patches that you want to keep in the plan for now, but do not want to be used in validation).

To manually add patches to your plan:

  1. Click Add Patch.. in Step 2: Patches. The Edit Search box appears.

  2. Enter search criteria, then click Search. See "Patch Searches" for information about searching options.

  3. Select the patches that you want to add, then click Add to this Plan. The Plan Wizard validates the selected patches and reports any problems associating the patches to targets in the plan. You cannot add invalid patches to the plan, for example patches for a different platform, but you can add patches with warnings, for example patches for different releases or products.

    Note: You should evaluate any warning before adding them to a plan.

6.5.2.2.1 What are the reasons that patches are added to a plan?

The Reason column in the table in the Plan Wizard lists the following reasons for including a patch:

  • Recommended - Oracle has flagged this patch as recommended for your new environment.

  • Customer Added - Someone has manually searched for a patch and added it to the plan.

  • Ignored - Another patch in the plan contains all of the fixes, so this patch is not necessary. This happens typically with an SPU when a PSU is also included in the plan.

  • Replacement Patch - The system found that the patch recommended or added to the plan will not install correctly, so a patch that fixes the same issues replaced it.

  • Manually Removed - The customer has suppressed the patch, so it is still in the plan but not part of the analysis and will not appear on the review and download screen.

  • Maintains Existing Fix - A patch added by the analysis which fixes the same issues solved by a patch installed with the original release. This happens because the fixes patched were not fixed in the new release to which you are upgrading.

6.5.2.2.2 How do I remove a recommended patch from the plan?

To delete or suppress a recommended patch, click the patch row in Step 2: Patches, then select Suppress or Delete from the menu. If you choose Delete, the patch is removed from the plan. If you choose Suppress, the patch is still included in the plan but is not analyzed in Step 3: Validation. You can restore a suppressed patch by clicking Restore to the Plan on the menu.

6.5.2.2.3 Why suppress patches in a plan?

You can suppress patches to create a "what if" scenario. Maybe you don't have time to wait for a merge patch, so by suppressing patches you can see how your analysis would change. You might decide to perform a patch in a later maintenance window because of a merge patch.

6.5.2.2.4 What happens if I try to switch releases for an upgrade plan while in an existing upgrade plan?

If you switch releases, the patches in the plan which no longer apply to the new release move to the Suppressed table in Step 2. If you switch back to the original release, the plan automatically moves those patches back into the plan.

6.5.2.2.5 Can I suppress a patch with the status Maintain Existing Fix?

Patches found to be installed in your original release and then added to the new release to maintain the same fix level cannot be suppressed in this release.

6.5.2.3 Step 3: Validation

Validation determines whether the combination of new software and patches will result in an installation which maintains your existing fixes and will install correctly. For upgrade plans, you have run the analysis in Step 3: Validation, any patches identified in the old environment that are not present in the new environment that need to be reapplied are also listed.

The most important function of the wizard is to validate the plan. When My Oracle Support validates a plan, it checks for conflicts using patch information from Oracle, the inventory of patches on your system (gathered by the configuration manager), and information from the candidate patches. In addition to checking patch merge conflicts between patches listed in the plan, the validation function also checks for conflicts between the listed plan patches and patches that have already been applied.

For upgrade plans, any patches that are applied in the old environment that are not present in the new environment are listed in the Added from Analysis table. These added patches are also listed in Step 2: Patches.

Any patch that is ignored is listed in the Informational Messages table for one of the following reasons:

  • The patch fixes the same issues as the installed patch it replaces.

  • The patch is ignored because another patch fixes the same issues.

  • The patch is part of another patch used during analysis.

6.5.2.3.1 Analyze Patches

Why should I validate a plan?

It is not possible to validate plans for all products. Currently, the validate function is available only for Oracle Database, Oracle Fusion Middleware, and Oracle Enterprise Manager products. You should validate the patches for these products to help you later when you want to deploy the patches. The validation process can catch a variety of problems which are easier to resolve now then when you are trying to deploy the patches. Validation identifies patches that conflict and require a replacement patch (also referred to as a Merged Patch, or MLR), missing prerequisites, patches not intended for a specific release, and other conditions that will cause problems at installation time.

Can I apply a plan without validating the plan first?

If validation is available for your product, you should validate your plan. If you do not validate, when you try to install the patch you may encounter issues that prevent you from completing the installation that could have been identified in the Plan Wizard.

6.5.2.3.2 Identify and Request Merge Patches

What is a patch request?

A patch request is a request for Oracle to create a patch to suit your specific configuration requirements. You should make a patch request when a patch that you previously installed will conflict with a patch that you are going to install or when a patch that you previously installed and still need is not yet available for a release to which you are upgrading. Because attempting to install the new patch over the old patch will cause problems, and backing out of the old patch is usually not an option, you must request a replacement patch which can be safely installed, maintain any bug fixes of the existing patch, and address the issues fixed by the new patch. If you want to maintain the existing bug fixes in an upgrade, sometimes you must request the patch for the release to which you are moving.

In the Plan Wizard, Step 3: Validation, if a patch is not available for the target release this is noted in the Issue column of the Issues to Resolve table. If the patch has not yet been requested, the Request Patch button is available in the Solution column of the table, on the same line as the patch number. Click Request Patch to request the patch for the selected target. Typically patch requests are completed within a week. However, most Database patch requests are completed within one day. When the patch is available, Replacement Available appears in the Solution column. Select the patch, then click Analyze to analyze the patch and add it to your plan.

What is a replacement patch?

When Oracle analyzes your system, support engineers might find that a patch that you installed already would conflict with a patch that you need to install now. Because attempting to install the new patch over the old patch will cause problems, and backing out the old patch is usually not an option, you must request a replacement patch which can be safely installed, maintain any bug fixes of the existing patch, and address the issues fixed by the new patch. After you request the replacement patch, the replacement patch is created. When the replacement patch is created, it is listed in the plan. You must then add the replacement patch to the plan and rerun the analysis.

What is a blocked patch?

The patch plan may report that a patch that you want to install is blocked. This occurs when a component of the patch conflicts with one or more other patches being analyzed

When will the replacement patch appear in my plan?

Typically this takes less than a week. In some cases, it can be immediate. If you request a replacement patch that was created previously (as might be the case if another customer encountered the same situation), it will immediately replace the other patches in your plan. If you do have to wait for the patch, the Patch Requests tab in the Plan region lists all replacement patch requests and their status.

Why can't I get a replacement patch for my Windows environment?

You can, however, it is just not part of the automation process. In addition, there is no patch conflict checking support for Windows. You need to follow the existing process of filing a Service Request. In future releases, your Plans will allow for the automated request of replacement patches for Windows.

6.5.2.4 Step 4: Review and Download

Note:

If the Review and Download table is empty in Step 4, verify that you are using the configuration manager release 10.3.2 or higher.

Review the details you have provided for the patch plan, then click Deploy.

If your Customer User Administrator (CUA) has given you download privileges, you can download patches from Oracle.

Select one or more items, or click Download All to download all patches, patch sets, and media displayed. For more information about download options, see "Patch Downloads".

When is a plan complete?

A plan is complete when all replacement patches (and software for upgrade plans) are placed in your plan. This means that the validation check is successful, you can download all of the patches and software in the plan, and install them.

6.5.3 Viewing Patch and Upgrade Plans

You can view plans from the Patch Recommendations and the Plan regions. The second tab of the region called "Replacement Patches" keeps track of all outstanding patch requests for all of your plans.

To view only the plans that you created, click the icon of a person, next to the favorites icon.

Plans Region

To view patch and upgrade plans from the Plans region, select a patch or upgrade plan. Doing this starts the Plan Wizard, an intuitive tool that enables you to edit your plan and ensure there are no merge conflicts between any patches within the a plan.

  • Select All Plan Types, Patching, or Upgrade from the menu to filter the plans table.

  • To search for a plan, enter a plan name or partial plan name in the search box, then click the search button.

  • Click a table heading to sort the table by that heading.

Patch Recommendations Table

Note: If you do not see the Patch Recommendations region on the dashboard, click Customize Page, then drag the Patch Recommendations region onto the dashboard. For more information about the Patch Recommendations region, see "Searching Using Configurations Based Recommendations".

In the Patch Recommendation table, a patch that is already part of a plan is shown with the plan icon in the In Plan column. Click the icon to display all plans with which the patch is associated, then click a plan to open the Plan Wizard.

Doing this enables you to add patches to more than one plan (for example, add a patch to one plan, remove it from another). Typically you would only expect to see a patch for a specific target in one plan.

For information about the Plan Wizard, see the "Patch and Upgrade Plans" help.

6.5.4 Miscellaneous Plans Questions

6.5.4.1 Why don't I see a particular release in the Release list in the Upgrade Planner region?

The Upgrade Planner uses the configuration information for the specified target collected by the configuration manager to produce a list of valid releases. If a release does not appear, either:

  • The upgrade path is not feasible.

  • It is possible to upgrade to the release. However, the release does not appear in the list because the software or patches have not been loaded by Oracle. Oracle will focus on the most popular upgrade plans first.

Note: Oracle Database release 10.2.0.4 is not available from the Select Release menu, in the Upgrade to Release section of the Upgrade Planner. For Windows, the Upgrade to Release, Select Release menu supports Oracle Database release 11.2.0.1 and higher.

6.5.4.2 Can I add any patch to a plan?

When you add a patch to a plan, you must associate patches with targets. Only patches which have a corresponding target can be added.

Select any patch from either Patch Recommendations or Patch Search results and choose one of the Add to Plan options. Follow the instructions to either add the patch to a new plan or to an existing plan.

When you add a patch to a plan from the Patch Recommendations region, My Oracle Support knows which target the patch applies to and correctly adds it to the plan. If you add it to the wrong plan, just click Undo when the confirmation message appears, or click the Patch Plan icon and click the remove from plan x.

6.5.4.3 How do I add a plan to my favorites?

To add a plan to your favorites, click the star on the row of the plan that you want to add or set it as a favorite in step 1 of the Plan Wizard.To view your favorites, click the favorites icon next to the plans menu.

6.5.4.4 Why can't I see specific targets in a plan?

You do not have the required view permissions for those targets. One possibility is that another user in your organization has view privileges to more targets than you (they may have more support identifiers in their profile) and may have added some patches to this plan for those targets.

Note: If your administrator removes an SI from your account then you will not have access to any target on that SI. This note does not apply if you are accessing My Oracle Support from within Oracle Enterprise Manager.

6.6 Patch Downloads

You can download patches from the Details page if:

  • You are granted the Download permission by your CUA. The CUA can set your permission for downloading patches based on your company's policies. If you do not have patch download privileges (you have View Only privileges), you will still be able to view patch details and readme documents from the Patch Search region.

    To find your CUA, go to the Settings tab, then select My Account. In the Support Identifiers table (Administrators column), click the View... link for any Support ID to display a list of administrators. Select one of the names to send an e-mail and request download privileges.

  • You have the required level of support associated with the Support Identifiers (SIs) in your account. The Patch Download Access value of the patch must be included in the list of Patch Download Access values in your account. For example, if the Patch Download Access value is Operating System, but your SI does not have access to download operating system patches, then you cannot download the patch.

For more information about patch download privileges, see Knowledge Document 1369860.1, "How Patches and Updates Entitlement Works".

https://support.oracle.com/rs?type=doc&id=1369860.1

Some patches require a license to be accepted before these patches can be downloaded. When downloading a patch in this category (identified by a lock icon), click Accept License from the Download pop up. The license for the patch will be shown. Accept the license. After accepting the license, the patch can be downloaded

6.6.1 What is Extended Support?

Some patches require an Extended Support contract from Oracle for permission to download the patch. Without an Extended Support contract, you can view the patch details and patch readme file for an Extended Support patch but you cannot download the Extended Support patch.

You can find out more about Extended Support at:

http://www.oracle.com/us/support/lifetime-support/index.html

6.6.2 Download Direct

You can download patches directly from the Patch Search results page or the Patch Details page.

6.6.2.1 Download from the Patch Search Results Page

To download a single patch:

  1. In the Patch Search Results table, select the patch by clicking the first column of the row that contains the patch that you want to download.

  2. In the row that contains the patch that you want to download, click anywhere except the patch name link. The context menu appears.

  3. Click Download.

  4. In the File Download window, click the patch file name link.

To download more than one patch, in the Patch Search Results table select the patches that you want to download by clicking the first column of the rows that contains the patches. In the File Download window, you can download the patches by clicking the path name links one at a time. Alternatively, use the WGET options.

6.6.2.2 Download from the Patch Details Page

To download a patch from the patch details page:

  1. In the Patch Search Results table, click the patch name link to view the patch details page.

  2. Click Download.

  3. In the File Download window, click the patch file name link.

6.6.3 Download Using WGET

WGET is a UNIX download utility. The WGET options enable you to create a WGET download script that you can save as a file or copy to the clipboard.

Note:

The WGET download script is intended for advanced users. In most cases, there are no messages to indicate that an error has occurred. Before using the WGET script, you should be familiar with the WGET command and WGET log files. You should also be familiar with UNIX file management, know how to edit, delete, and copy UNIX files, create and edit shell scripts, change execute privileges in UNIX, and understand HTTP error codes. Alternatively, use a download manager to download multiple patches. If you do this, you must maintain and active My Oracle Support session while you download the patches.

Note:

Currently, the WGET script generated by My Oracle Support does not support Sun patches. See Note 1199543.1, Patch Download Automation for Sun Products Using WGET, for information about using the WGET utility outside of My Oracle Support to download Sun patches:

https://support.oracle.com/rs?type=doc&id=1199543.1

  1. In the File Download window, click WGET Options. The WGET Options window appears. Note the time that the authentication token expires, where applicable. You cannot use this script after that time.

  2. Click Download .sh to download a shell script (sh.) file, or click Copy to Clipboard to copy the script content to the clipboard. If you clicked Download.sh, the download dialog box opens.

  3. Click Return to File Window in the WGET Options window.

  4. Open the .sh file in a text editor or copy the contents of the clipboard to a text editor.

  5. Find the SSO_PASSWORD= line and enter your SSO password. This is the password that you used to login to My Oracle Support. You will see your username already populated on the SSO_USERNAME= line. If you do not enter the correct password, you will receive an error message when you run the script. Note that the password is case sensitive.

  6. If you included a controlled patch in the WGET script, enter the patch password on the PASSWORD_patchnumber= line, where patchnumber is the number of the controlled patch you are downloading. If you do not enter the correct password, you will receive an error message when you run the script.

  7. If necessary, edit the path on the WGET=/usr/bin/wget line, Edit this line if WGET is installed in a different location in your environment.

  8. If necessary, edit the path of the log directory.

  9. Save the WGET script.

  10. Use the chmod command to add execute privileges to the script, for example chmod u+x filename.sh where filename is the name of the WGET.sh file.

  11. Enter the following command to run the script and download the patches:$sh filename.sh

Note: The WGET download script does not provide feedback of whether or not the script was successful. View the log file to verify that the download was successful or to troubleshoot problems. The log file location is recorded in the script, on the LOGFILE= line.

Possible outcomes of the WGET script:

  • Download was successful.

  • A zero byte file is returned. A zero byte file indicates that the script failed, for example: -rw-r--r-- 1 userx g920 0 Sep 2 17:10 p8290402_111060_SOLARIS64.zip.

    Note: Delete any zero byte files before rerunning the script.

  • Some patch files are downloaded successfully but several zero byte files are returned. If you exceed the number of connections allowed by Oracle, any subsequent requests are rejected. The following message will appear in the log file: Proxy request sent, awaiting response... 403 Forbidden

  • A message appears indicating that the SSO password is blank.

  • Password is incorrect or the wrong case. The following message appears: HTTP request sent, awaiting response... 401 Unauthorized Authorization failed.

  • Your company's firewall may prevent WGET from downloading the patches.

6.6.4 Download Multiple Patches

To download more than one patch, in the Patch Search Results table select the patches that you want to download by clicking the first column of the rows that contains the patches. In the File Download window, you can download the patches by clicking the path name links one at a time. Alternatively, use the WGET options.

6.6.5 Download Language Patches

From any patch detail page, you can chose the languages for the patches you want to download.

Note:

You can choose languages or platform, but not both

6.6.6 Frequently Asked Download Questions

6.6.6.1 Why is the Download button disabled?

A patch has one or more of the following download access types:

  • Software

  • Operating system

  • Firmware

  • Vintage Solaris

  • Extended Support

A patch's download access type is listed on the Patch Details page. If your SI does not have the required patch download access, you cannot download the patch. For example, if a patch has Operating System download access, but your SI does not have access to download Operating System patches, then you cannot download the patch. Contact your Customer User Administrator (CUA) to request the required download access.

In addition, if the CUA has set the download patches privilege to No (View Only) for an SI in your profile, you cannot download patches unless another SI in your profile has the download patches privilege set to Yes (Download).

For more information about patch download privileges, see Knowledge Document 1369860.1, "How Patches and Updates Entitlement Works".

6.6.6.2 What is the fastest way to download all of the files and language packs for a patch?

If the language menu appears, then the language packs are available for this patch. You must install the platform patch (English version) first, then select the applicable language. To download a patch, click Download, then click each patch file link to download and save them in a location of your choosing, or use a download manager to help speed the process. Alternatively, you can generate the wget script for all patches selected from the Download window.

Note:

For PeopleSoft products, you must select either American English or one of the translations (including UK English) but not both.

6.6.6.3 How do I download a patch from the Patch Details page?

Every Patch Detail page provides options to view the patch readme as well as download the patch. You can also select individual patches on the patch search results from either the Patch Search or Patch Recommendations pages.

To download a patch from the Patch Details page:

  1. In the Patch Search Results table, click the patch name link to view the patch details page.

  2. Click Download.

  3. In the File Download window, click the patch file name link.

The context bar for each patch provides a download option. Note that you can select multiple patches from a list by using Ctrl or Shift.

6.6.6.4 Why do you recommend using a download manager?

Many customers feel it is the most effective way to download many files. The size of the files can be large, and if you need to download many of them, it could be easier and more convenient over time to use a download manager. There are many download managers available. Oracle has no specific recommendation on which download manager to use.

6.6.6.5 How can I download more than one patch from the list on the left when looking at a single patch?

To download more than one patch:

  1. Choose the Close link above the patch details to return to the patch search results.

  2. From the patch search results, click anywhere in the row except a link to select that row. Use Ctrl or Shift to select multiple rows.

  3. Choose the Download button from the context bar.

  4. Click each file and save it.

6.6.6.6 When I download a patch, why am I asked for a password?

Some patches have a limited distribution. These patches have the classification Controlled and are password protected. If you try to download a controlled patch, you are prompted for the password. Log a technical service request (SR) to request the password for a controlled patch.

6.6.6.7 What hardware-related downloads are available from Patches & Updates?

In addition to patches, you can also use Advanced Search to download firmware updates, drivers, and the following support-related downloads:

  • Auto Service Request (ASR)

  • Services Tools Bundle (STB which includes Explorer, SNEEP, LWAC and RDA)

  • Sun Automated Service Manager (SASM)

  • Secure File Transport (SFT)

For more information about Sun disk storage patches and updates, see Knowledge Document 1350703.1:

https://support.oracle.com/rs?type=doc&id=1350703.1

6.7 Patch Related Activity

The Patch Related Activity region lists recent activity related to patching. Click a patch link to view the patch details. This region has the following tabs:

  • Downloaded - lists patches that have been downloaded. Select the star icon to mark a patch as a favorite. Favorite patches are listed in the Favorites tab.

  • Viewed - lists patches that have been viewed. Select the star icon to mark a patch as a favorite. Favorite patches are listed in the Favorites tab.

  • Discussed - lists patches for which the user posted messages.

  • Favorites- lists favorite patches. Click the star icon to remove the patch from Favorites. Click the patch link to view the patch. For more information about favorites, "Favorites".