Assistant: Download Reference for Oracle Database/GI PSU, SPU(CPU), Bundle Patches, Patchsets and Base Releases (Doc ID 2118136.2) It will ask for following. Oracle started Bundle Patch from April2016 by renaming ‘Database Patch for Engineered Systems and Database In-Memory’ to “Database Proactive Bundle Patch”.These were originally limited to Windows and Exadata systems and now its available to Non-windows, Non-Exadata systems as well. All future 11.1.2.x Access Server bundle patches will be part of the Identity Management Suite Bundle Patch while any ASDK and WebGate bundle patches will be delivered as individual releases. It is important to note that Access Server patch numbers listed below will reference the product Oracle Identity Management Suite which will include. If you have to create a new database now (I’m writing this in March 2017) for a migration of OLTP database with minimal risks of regression, I would recommend: The latest patchset of Oracle Database 12cR1 The latest Proactive Bundle Patch The two patches to get full control over Adaptive. Critical Patch Updates are collections of security fixes for Oracle products. They are available to customers with valid support contracts. They are released on the Tuesday closest to the 17th day of January, April, July and October.
The script content on this page is for navigation purposes only and does not alter the content in any way.
This chapter provides an introduction to Bundle Patch 1 (BP1) and the prerequisites for installation. It contains the following sections:
1.1 Overview
This document provides step by step instructions for applying Bundle Patch 1 (BP1) in to your existing Enterprise Manager Cloud Control 12.1.0.1 installation. Note BP1 is not an Enterprise Manager patch set release, and therefore does not change the Enterprise Manager version to 12.1.0.2.
1.2 Use Cases and Recommendations
The following sections provide recommendations on how to use BP1 under different use case scenarios. The scenarios are detailed under the following headings:
1.2.1 General Use Case Recommendations
General use cases and recommendations on the installation of BP1 are outlined in Table 1-1.
Table 1-1 General Use Case Recommendations
| Use Case | Recommendation |
|---|---|
If you are new to Enterprise Manager | You will need to retrieve the new Enterprise Manager 12c binaries from the Oracle Technology Network (OTN) and carry out a fresh install. The installation should include BP1 and the latest plug-in releases. |
Using Enterprise Manager Cloud Control 12.1.0.1 release in a non-production test or sandbox environment | You should analyze how much configuration setup you have done in Enterprise Manager and the number of Management Agents you have deployed. Based on this analysis, you should uninstall the existing Cloud Control and do a fresh installation if this is feasible This also means that you have to reinstall all your existing Management Agents. This is the simplest way to get to the benefits and features of the latest patched Cloud Control release, which includes BP1 and the latest plug-in releases. The Enterprise Manager uninstall instructions are available at the following location: You can get the updated Enterprise Manager binaries with BP1 from the following location: |
If you have already downloaded and installed 12.1.0.1 release in a Production environment | If you have already downloaded and installed Enterprise Manager 12c Release 12.1.0.1 in a production environment, complete the following steps Skipping steps could result in potential issues. Oracle recommends that you open a proactive service request.
If you have additional OMS instances or a disaster recovery configuration, then follow the BP1 application instructions detailed in Section 2.1, 'Applying Bundle Patch 1 on Oracle Management Service'. |
1.2.2 Upgrading to the Current Release
Use cases and recommendations related to upgrading from an Enterprise Manager Grid Control Release 10.2.0.5 or 11.1.0.1 are discussed in Table 1-2.
Table 1-2 Upgrading to the Current Release
| Use Case | Recommendation |
|---|---|
Upgrading to the current release | You can upgrade directly from Enterprise Manager Grid Control 10.2.0.5 or 11.1.0.1 releases to the current release with BP1 included by completing the following:
|
If you have applied the pre-upgrade console patch, but have not upgraded Management Agent or OMS | If you have just applied the pre-upgrade console patch, but have not yet gone ahead with Management Agent or OMS upgrade, complete the following steps:
The new version of the pre-upgrade console patch will only work with EM12c binaries (with BP1 included) and Management Agent 12.1.0.1 binaries. To ensure that you get the latest patch from OTN, refer to the last updated date on the OTN download page. Follow the Instructions provided in the Upgrade Guide from here: |
If you have applied the pre-upgrade console patch and upgraded the Management Agent or OMS | In this case you should finish your upgrade to Enterprise Manager 12c and complete the following instructions in the specified order :
Oracle recommends that you open a proactive Service Request (SR) with Oracle Support. |
1.2.3 Performing an Additional OMS Installation
Use cases and recommendations related to performing an additional OMS installation are discussed in Table 1-3.
Table 1-3 Performing an Additional OMS Installation
Oracle Bundle Patch Downloads
| Use Case | Recommendation |
|---|---|
If your first OMS is deployed with new Enterprise Manager binaries with BP1 included or if you have applied the BP1 manually | You can proceed with the additional OMS installations. The deployment procedure will clone the first OMS, so there will be no need to apply BP1 on the second OMS once the install is done. As a part of the additional OMS installation, you will be required to deploy the Management Agent on the host where you plan to have the additional OMS. Get the latest Management Agent binaries from the Self Update feature, which have BP1 included for Management Agent deployment. |
If your first OMS has not been updated with the new Enterprise Manager binaries, or if you have not applied the BP1 manually to the OMS | Select one of the following two options: Option 1:
Option 2:
|
1.3 Bundle Patch 1 Compatibility Matrix
Refer to Table 1-4, 'Bundle Patch 1 Compatibility Matrix' to understand the valid patches and version combinations of OMS, plug-ins, and Management Agents.
Table 1-4 Bundle Patch 1 Compatibility Matrix
Target Agent without Bundle Patch 1 applied and 12.1.0.1 plug-in on target Management Agent | Target Agent with BP1 and 12.1.0.1 plug-in on target Management Agent | Target Agent without BP1 and 12.1.0.2 plug-in on target Management Agent | Target Agent with BP1 applied and 12.1.0.2 plug-in on target Management Agent | |
12.1.0.1 OMS without BP1 applied | Yes | No | No | No |
12.1.0.1 OMS with BP1 Applied and 12.1.0.1 plug-in on OMS (no plug-in upgrade) | Yes | Yes | No | No |
12.1.0.1 OMS with BP1 applied and 12.1.0.2 plug-in on OMS (plug-in upgrade done) | YesFoot 1 | Yes | No | YesFoot 2 |
Footnote 1 An example for this use case is that you have Solaris Management Agents without BP1 applied, 12.1.0.1 plug-ins on agents pointing to Linux 32-bit OMS with BP1 applied, and 12.1.0.2 plug-ins on the OMS.
Footnote 2 This is a fresh install of Enterprise Manager 12c binaries with BP1 included.
1.4 Mandatory Pre-Requisites for installing Bundle Patch 1
The following are the mandatory prerequisites for installing BP1:
Software Library Configured.
All Enterprise Manager components backed up.
The Agent Patching Infrastructure set up correctly (differs for offline versus online modes).
The My Oracle Support (MOS) connection configured for Management Agent patching or the download of patches from MOS and upload to Enterprise Manager.
Make sure that you go through all of the prerequisites described in the following sections before applying Bundle Patch 1.
1.4.1 Oracle Software Library Configured
You need to verify whether you already have the Software Library configured. If not, complete the following:
From the Enterprise menu, select Provisioning and Patching, then click Software Library.
From the Actions list, select Administration, then select Add if nothing has yet been configured.
Select the OMS Shared Filesystem location.
Note:
This is a location on a shared filesystem that is visible to all OMS instances. For example, this could be an NFS mounted location and should have read/write access from all of the OMS instances.Upon addition of the location, a job executes to configure the Software Library. Under this location, all required entities for Enterprise Manager, such as Provisioning, Patching, and Cloud Management, are populated.
Once the job is successful, you will see the components configured in the Software Library.
From the Enterprise Manager menu, select Patching and Provisioning, then click Software Library to view the Software Library.
1.4.2 Backing Up Enterprise Manager Components
Before you apply BP1, be sure that you back up the following components:
Oracle Inventory
Management Repository Database
Middleware Home and Enterprise Manager domains
Instance Home where OMS is installed
Default Management Agent with OMS
Software Library
You must back up all components listed above. A failure during any stage of the BP1 process may make it necessary to restore one or more of these components.
For more information, see the Backing Up Enterprise Manager chapter in the Oracle Enterprise Manager Cloud Control Administrator's Guide. This can be found at the following location:
1.4.3 Using the Correct OPatch Version
Verify you have the right OPatch version under the OMS Oracle Home. The OPatch version required to install BP1 is 11.1.0.9.4 or higher.
Set ORACLE_HOME to OMS HOME and run the following command to verify the OPatch version:
If the OPatch version is less than 11.1.0.9.4, complete the following:
Download the latest OPatch patch (6880880) under release 11.1.0.x series from My Oracle Support (
https://support.oracle.com).The Patch Number is 6880880. Select the platform that corresponds to your OMS platform.
Figure 1-4 Correct OPatch Version
Click Search.
Select the Opatch 11.1.0.0.0 version and click Download.
Note:
Do not select OPatch 11.2.0.x as this will result in failures during patch application.Transfer the zip to the OMS Server.
Rename the existing OPatch folder under the OMS ORACLE HOME to OPatch_old_MMYY
Unzip the new Opatch patch zip under the OMS ORACLE HOME.
This creates an Opatch directory with the latest Opatch.
1.5 Troubleshooting
To learn more about troubleshooting tips and a list of known issues while applying Bundle Patch 1, refer to My Oracle Support note 1395640.1 at the following location:
On a regular basis Oracle provides patch sets that include generic and port specific fixes encountered by customers since the base product was released.
Patch sets increment the 4th digit of the release number e.g. 12.1.0.1.0 to 12.1.0.2.0, these patch sets are fully regression tested in the same way that the base release is (for example, 12.1.0.1.0). Customers are encouraged to apply these fixes.
If a customer encounters a critical problem that requires a fix prior to the next patch set becoming available, they can request that a one off fix is made available on top of the latest patch set. This delivery mechanism is similar to the Microsoft Hot Fixes and is known as an Oracle patch set exception (or interim patch). Unlike UNIX platforms, these patch set exceptions are delivered in a patch set exception bundle (cumulative patch bundle), which includes all fixes since the current patch set. Starting with Oracle Database 11g release 2 (11.2.0.4), patch bundles are described as software_version.n, where software_version is the patch set version (12.1.0.2) and n is the bundle patch version (12.1.0.2.10). You should always apply the latest patch bundle available for your release. Windows patch set exception bundles (bundled patches) are applicable to both Oracle Grid Infrastructure and Oracle Database homes.
The patch set exception bundles also include the fixes for the CPU (Critical Patch Update), DST (Daylight Saving Time), PSU (Patch Set Update) and Recommended Patch Bundles. It is not required to have the previous security patches applied before applying the patch set exception bundle. However, you must be on the stated patch set level for a given product home before applying the patch set exception bundle for that release.
- Refer to the My Oracle Support website for required patch updates for your installation.
Note:
If you are not a My Oracle Support registered user, then click Register for My Oracle Support and register.
Oracle Bundle Patch Download Torrent
See Also:
https://www.oracle.com/pls/topic/lookup?ctx=en/database/oracle/oracle-database/12.2/cwwin&id=CWWIN-GUID-DF76F201-3374-486F-9D19-06276764569F for information about how to stop database processes in preparation for installing patches