If this is a RAC environment, choose one of the patch installation methods provided by OPatch rolling, all node, or minimum downtime , and shutdown instances and listeners as appropriate for the installation method selected. If this is not a RAC environment, shut down all instances and listeners associated with the Oracle home that you are updating.
For more information, see Oracle Database Administrator's Guide. The location of these executables depends on your operating system.
Set your current directory to the directory where the patch is located and then run the OPatch utility by entering the following commands:. Should OPatch return conflicts or subsets, refer to Section 3. Do not perform the operations in this section on ASM instances. However, if you shut down ASM as part of applying the CPU, you must start ASM instances before you can perform any of the actions in this section on any database instances. Load modified SQL files into the database, as explained in Section 3.
Recompile views in the database, if necessary, as explained in Section 3. The following steps load modified SQL files into the database. For a RAC environment, perform these steps on only one node. The catbundle. For information about the catbundle. If there are errors, refer to Section 4, "Known Issues". You may skip this section if you have recompiled views for this database during the installation of a previous CPU.
The time required to recompile the views and related objects depends on the total number of objects and on your system configuration. If you want to check whether view recompilation has already been performed for the database, execute the following statement.
If the view recompilation has been performed, this statement returns one or more rows. If the view recompilation has not been performed, this statement returns no rows. The following steps recompile the views in the database. Run the pre-check script so named because it was initially released in CPUJan , which reports the maximum number of views and objects that may be recompiled:.
The purpose of this step is to help you determine whether view recompilation should be done at the same time as the CPU install, or scheduled later. If the database is not in a RAC environment, perform this step and skip the next step.
If the database is in a RAC environment, go to the next step. Run the view recompilation script. If the database is in a RAC environment, run the view recompilation script as follows. Stop all instances except the one where the view recompilation is being executed. Check the log file for any errors. These instructions are for a database that is created or upgraded after the installation of CPUOct You must execute the steps in Section 3. Cloning a database that was created by either of the two preceding methods, and if Section 3.
Upgraded databases require that you perform the steps in Section 3. If this is not the case, you must execute the steps in Section 3. Shut down all instances and listeners associated with the Oracle home that you are updating. If a molecule is not installed in the Oracle Home, the rollback will ignore it.
If a molecule is installed as part of a merge patch, it will not be rolled back. If it is desired to rollback merge patches that have been applied to your Oracle Home, the rollback needs to be issued separately. To do so, use the following command:. You may also rollback individual molecules or a list of molecules, as needed.
Refer to the OPatch documentation on the nrollback command. Start all database instances running from the Oracle home. Follow these steps for each node in the cluster, one node at a time:. Start the instance on the node. Depending on the type of home, enter the following commands or command. Follow the instructions listed in Section Section 3. All other instances can be started and accessed as usual while you are executing the deinstallation steps.
The following ignorable errors may be encountered while running the catbundle. Note that this step has no impact on the implementation of the CPU security fixes; it only affects the successful execution of the Job Scheduling system.
The view recompilation pre-check script returns different results during subsequent runs such as after the first time you ran it. The results the maximum number of views and objects that may be recompiled may be more or less than reported in the previous running of the script.
This is expected behavior, and is not a problem. If the view recompilation script has already been run, a message is displayed indicating that the script has already been applied. This is not a problem, because as the instructions note, you do not need to run the script if it has already been run.
Oracle customers have access to electronic support through My Oracle Support. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.
Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U. The Windows patch bundles include the security vulnerability bug fixes, the PSU recommended non-security bug fixes, and other customer-requested bug fixes. Oracle Database Bundle Patch For Oracle Secure Enterprise Search CPU Patch For Fusion Middleware Table 15 describes the minimum product requirements for Oracle Database Appliance.
Table 16 lists the patches for Oracle Database patch set updates. For complete security patch information, see Section 3. As Windows Bundles are cumulative, you may apply the patch indicated in the Patch Availability tables in Section 3. See My Oracle Support Note Table 19 describes the available patches for Oracle Secure Enterprise Search See Section 3.
Table 20 describes the available patches for Oracle Secure Enterprise Search Table 21 describes the minimum product requirements for Oracle TimesTen.
Section 3. Table 26 describes the available patches for Oracle Business Intelligence Publisher. Customers on earlier versions of Oracle Business Intelligence Publisher Select the patch with the build number that is indicated in Table 27 , or the patch with higher build number than what is indicated for the platform you are about to update, for example: EnterpriseJ2EE, Studio, or EnterpriseSA. Upgrade to CEP PSU Patch See Note Additional information may be found in My Oracle Support Note Table 32 describes the patch information for Oracle Fusion Middleware Table 33 describes the available patches for Oracle Fusion Middleware Unix: CPU Patch Table 34 describes the patch information for Oracle Fusion Middleware Table 35 describes the available patches for Oracle Fusion Middleware For information about the different types of installations, see My Oracle Support Note Table 36 describes the patch information for Oracle Fusion Middleware Table 37 describes the available patches for Oracle Fusion Middleware Table 38 describes the patch information for Oracle Fusion Middleware Table 39 describes the available patches for Oracle Fusion Middleware Table 40 describes the patch information for Oracle Fusion Middleware Table 41 describes the available patches for Oracle Fusion Middleware JInitiator Foot 1.
If you are using Portal It is not part of any Oracle home. It is installed by default only in homes where Oracle Forms is installed. Table 42 describes the patch information for Oracle Identity Management Table 43 describes the available patches for Oracle Identity Management Table 44 describes the patch information for Oracle Identity Management Table 45 describes the available patches for Oracle Identity Management Table 46 describes the minimum product requirements for Oracle GoldenGate Veridata.
For information, see My Oracle Support Note Table 49 describes the available patches for Oracle Outside in Technology. See also the underlying product stack tables. WebLogic Portal patches are cumulative to include all the prior published advisories. See also the underlying product stack tables JRockit for any applicable patches. For WebLogic Server releases The WebLogic plug-ins include all cumulative bug fixes and thus include fixes for all previously released advisories.
For information about WebLogic Server releases Since these products are bundled with Enterprise Manager Base Platform, the Repository Oracle Database and Oracle Management Server Oracle Fusion Middleware middle tier should be patched separately, depending on which versions are installed. The PSU Oracle Collaboration Suite homes contain database and application server homes.
Table 64 describes the available patches for Oracle Collaboration Suite. Table 65 describes the minimum product requirements for Oracle OPatch. The Oracle OPatch downloads can be found at Patch My Oracle Support Note Oracle customers have access to electronic support through My Oracle Support.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U. Government or anyone licensing it on behalf of the U. Government, the following notice is applicable:. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.
As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR Oracle America, Inc.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.
If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Other names may be trademarks of their respective owners. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. This software or hardware and documentation may provide access to or information on content, products, and services from third parties.
Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services. Back to top. Important Note: this feedback may be anonymously visible to other customers until processed by Oracle Support.
This section contains the following: Section 1. Step 1 Assess your Environments Determine the Oracle product suites and products and their release numbers for each of your environments. Step 2 Read Important Announcements Review Section 2, "What's New in October ," as it lists documentation and packaging changes along with important announcements such as upcoming final patches.
Step 3 Determine Patches to be Applied For each environment, determine which patches need to be applied by using the tables in Section 3, "Patch Availability for Oracle Products.
This may be due to several reasons including: The release version is not available on this platform. A request may be made: At any time. Critical Patch Updates are applied only on the base release version, for example Final patches scheduled for October Oracle Identity Management Table 3 Patch Information for Oracle Database Table 4 Patch Availability for Oracle Database Table 5 Patch Information for Oracle Database Table 6 Patch Availability for Oracle Database Table 7 Patch Information for Oracle Database Table 8 Patch Availability for Oracle Database Table 9 Patch Information for Oracle Database Table 10 Patch Availability for Oracle Database
0コメント