Patch 26635834 - Oracle JavaVM Component 11.2.0.4.171017 Database PSU
This document describes how you can install Patch 26635834 - Oracle JavaVM Component 11.2.0.4.171017 Database PSU on your Oracle Database 11g Release 2 (11.2.0.4.0).
This patch is not Oracle RAC Rolling installable. However, starting with the Jan2017 OJVM PSU patchset for 11.2.0.4, the OJVM PSU may be installed in a "Conditional Rolling Install" fashion for the following use cases:
No OJVM usage
OJVM used by non-critical jobs and programs
OJVM used by critical functions isolated as services
OJVM used extensively, not isolated, and downtime is tolerated
OJVM used by critical functions and minimal downtime is required
See My Oracle Support Document 2217053.1 for more details.
This patch is Database Vault installable. Review My Oracle Support Document 1195205.1 for details on how to apply this patch to a Database Vault environment.
This patch is not Data Guard Standby First Installable.
This patch requires any one of the following Oct2014 or greater to be already installed prior to installing this patch:
Database PSU 11.2.0.4.4 (Oct2014)
Database SPU 11.2.0.4 (CPUOct2014)
Database patch for Exadata 11.2.0.4.12 (Oct2014)
This document is accurate at the time of release. For any changes and additional information regarding Oracle JavaVM Component 11.2.0.4.171017 Database PSU, see these related documents that are available at My Oracle Support (http://support.oracle.com/):
Document 2297782.1 Oracle JavaVM Component 11.2.0.4.171017 Database PSU Known Issues
This document includes the following sections:
From CPUJan2016 onwards, the 5th digit of the version number will be changed to reflect the release date in the format YYMMDD. See My Oracle Support Document 2061926.1 for more information.
The Oracle JavaVM Component 11.2.0.4.171017 Database PSU is cumulative and includes the Database CPU program security content including Oracle JavaVM Component 11.2.0.4.171017 Database PSU - Generic JDBC Patch.
Table 1 describes installation types and security content. For each installation type, it indicates the most recent patches, which includes new security fixes that are pertinent to that installation type. If there are no security fixes to be applied to an installation type, then "None" is indicated. If a specific patch is listed, then apply that or any later patch to be current with security fixes.
Table 1 Installation Types and Security Content
| Installation Type | Latest Database Patch with Security Fixes |
|---|---|
|
Server homes |
Oracle JavaVM Component 11.2.0.4.171017 Database PSU |
|
Grid Infrastructure home |
Oracle JavaVM Component 11.2.0.4.160719 Database PSU - Generic JDBC Patch 23727132 |
|
Client-Only Installations |
Oracle JavaVM Component 11.2.0.4.160719 Database PSU - Generic JDBC Patch 23727132 |
|
Instant Client Installations |
Oracle JavaVM Component 11.2.0.4.160719 Database PSU - Generic JDBC Patch 23727132 (The Instant Client installation is not the same as the client-only Installation. For additional information about Instant Client installations, see Oracle Call Interface Programmer's Guide.) |
Before you install or deinstall the patch, ensure that you meet the following requirements. For an Oracle RAC environment, meet these prerequisites on each of the nodes.
Read My Oracle Support Document 1929745.1 Oracle Recommended Patches -- "Oracle JavaVM Component Database PSU and RU" (OJVM PSU and OJVM RU) Patches.
Ensure that the Oracle Database on which you are installing the patch or from which you are rolling back the patch is Oracle Database 11g Release 2 (11.2.0.4.0).
Ensure that the following Oct2014 or greater to be already installed prior to installing this patch:
Database PSU 11.2.0.4.4 (Oct2014) (Patch number: 19121551)
Database SPU 11.2.0.4 (CPUOct2014)
Database patch for Exadata 11.2.0.4.12 (Oct2014)
You must use the OPatch utility version 11.2.0.3.5 or later to apply this patch. Oracle recommends that you use the latest released OPatch version for 11.2, which is available for download from My Oracle Support patch 6880880 by selecting the 11.2.0.0.0 release.
For information about OPatch documentation, including any known issues, see My Oracle Support Document 293369.1 OPatch documentation list.
Ensure that you set the ORACLE_HOME environment variable to the Oracle home of the Oracle Database.
Ensure that the $PATH definition has the following executables: make, ar, ld and nm. The location of these executables depends on your operating system. On many operating systems, they are located in /usr/ccs/bin.
Ensure that you verify the Oracle Inventory because OPatch accesses it to install the patches. To verify the inventory, run the following command. If the command displays some errors, then contact Oracle Support and resolve the issue.
$ opatch lsinventory
(Only for Installation) Maintain a location for storing the contents of the patch ZIP file. In the rest of the document, this location (absolute path) is referred to as PATCH_TOP_DIR. Extract the contents of the patch ZIP file to the location (PATCH_TOP_DIR) you have created above. To do so, run the following command:
$ unzip -d <PATCH_TOP_DIR> p26635834_11204_<PLATFORM_NAME>.zip
(Only for Installation) Determine whether any currently installed interim patches conflict with this patch 26635834 as shown as follows:
$ cd <PATCH_TOP_DIR>/26635834 $ opatch prereq CheckConflictAgainstOHWithDetail -ph ./
The report will indicate the patches that conflict with this patch and the patches for which the current 26635834 is a superset.
|
Note: When OPatch starts, it validates the patch and ensures that there are no conflicts with the software already installed in theORACLE_HOME. OPatch categorizes conflicts into the following types:
|
Ensure that you shut down all the services running from the Oracle home.
For a Non Oracle RAC environment, shut down all databases and listeners associated with the Oracle home that you are updating. For more information, see Oracle Database Administrator's Guide.
For an Oracle RAC environment, shut down all the services (database) running from the Oracle home on all the nodes you want to patch. After all nodes are patched, start all services. OPatch is used on only one node at a time.
To install the patch, follow these steps.
Set your current directory to the directory where the patch is located and then run the OPatch utility by entering the following commands:
$ cd <PATCH_TOP_DIR>/26635834
Install the patch by running the following command:
$ opatch apply
Verify whether the patch has been successfully installed by running the following command:
$ opatch lsinventory
If apply fails for make target jox_refresh_knlopt when applying the patch to the database home, see Issue #1 in Section 8, "Known Issues" for more information.
Start the services from the Oracle home after all the nodes are patched.
If there are errors, see Section 8, "Known Issues".
Beginning with the Jan2017 OJVM PSU patchset for 11.2.0.4 and for 12.1.0.2, Oracle Development is relaxing the requirement to restart the database in upgrade mode. Prior to the Jan2017 OJVM PSU patchsets, the installation of the OJVM PSU patchset into the $ORACLE_HOME binaries was required to be followed by a postinstallation of the OJVM PSU patchset into each associated database while in restricted startup upgrade mode.
Beginning with the Jan2017 OJVM PSU patchset for 11.2.0.4 and for 12.1.0.2, Oracle Development is defining a few very specific situations and prerequisites where the OJVM PSU patchset can be postinstalled into each database while the database remains in unrestricted startup mode. If your business needs are compatible with the legacy requirement to restart each database into restricted startup upgrade mode, then Oracle recommends that you continue to postinstall the OJVM PSU patchset into each database while it is in restricted startup upgrade mode. In this case, you should skip the next two paragraphs, and continue to Section 4.1, "Loading Modified SQL Files Into the Database".
The very specific situations and prerequisites where the OJVM PSU patchset can be postinstalled into each database in unrestricted ”startup” mode are defined and detailed in My Oracle Support Document 2217053.1, RAC Rolling Install Process for the "Oracle JavaVM Component Database PSU" (OJVM PSU) Patches. At a high level, the ability to use unrestricted startup mode involves a two-part decision tree for OJVM PSU for each database; is OJVM installed and is OJVM used? The Appendix to My Oracle Support Document 2217053.1 provides detailed procedures for each specific situation where it is possible to use unrestricted startup mode.
There are pros and cons to each of the very specific situations and prerequisites are discussed in My Oracle Support Document 2217053.1. Therefore, Oracle recommends that the legacy requirement to restart each database into restricted startup upgrade mode be observed when possible.
The following steps load modified SQL files into the database. For an Oracle RAC environment, perform these steps on only one node.
Install the SQL portion of the patch by running the following command for a single instance environment.
cd $ORACLE_HOME/sqlpatch/26635834 sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> startup upgrade SQL> @postinstall.sql SQL> shutdown SQL> startup
For an Oracle RAC environment, reload the packages on one of the nodes using the following commands. Make sure no other instance of the database is up on the remote nodes.
cd $ORACLE_HOME/sqlpatch/26635834 sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> STARTUP SQL> alter system set cluster_database=false scope=spfile; SQL> SHUTDOWN SQL> STARTUP UPGRADE SQL> @postinstall.sql SQL> alter system set cluster_database=true scope=spfile; SQL> SHUTDOWN SQL> STARTUP
After installing the SQL portion of the patch, some packages could become INVALID. This will get recompiled upon access or you can run utlrp.sql to get them back into a VALID state.
cd $ORACLE_HOME/rdbms/admin sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> @utlrp.sql
If there are errors, see Section 8, "Known Issues".
You must execute the steps in Section 4, "Postinstallation" for any new database or upgraded database.
Ensure to follow the Prerequisites as described in Section 2, "Prerequisites". To deinstall the patch, follow these steps. For an Oracle RAC environment, perform these steps on any one of the nodes:
Deinstall the patch by running the following command:
$ opatch rollback -id 26635834
If rollback fails for make target jox_refresh_knlopt when deinstalling the patch from the database home, see Issue #1 in Section 8, "Known Issues" for more information.
Start the services from the Oracle home.
Ensure that you verify the Oracle Inventory and compare the output with the one run before the patch installation and re-apply any patches that were rolled back as part of this patch apply. To verify the inventory, run the following command:
$ opatch lsinventory
Beginning with the Jan2017 OJVM PSU patchset for 11.2.0.4 and for 12.1.0.2, Oracle Development is relaxing the requirement to restart the database in upgrade mode. Prior to the Jan2017 OJVM PSU patchsets, the deinstallation of the OJVM PSU patchset from the $ORACLE_HOME binaries was required to be followed by a post deinstallation of the OJVM PSU patchset from each associated database while in restricted ”startup upgrade” mode.
Beginning with the Jan2017 OJVM PSU patchset for 11.2.0.4 and for 12.1.0.2, Oracle Development is defining a few very specific situations and prerequisites where the OJVM PSU patchset can be post deinstalled from each database while the database remains in unrestricted startup mode. If your business needs are compatible with the legacy requirement to restart each database into restricted startup upgrade mode, then Oracle recommends that you continue to post deinstall the OJVM PSU patchset from each database while it is in restricted startup upgrade mode. In this case, you should skip the next two paragraphs, and continue to Section 7.1, "Loading Modified SQL Files Into the Database".
The very specific situations and prerequisites where the OJVM PSU patchset can be post deinstalled from each database in unrestricted startup mode are defined and detailed in My Oracle Support Document 2217053.1, RAC Rolling Install Process for the "Oracle JavaVM Component Database PSU" (OJVM PSU) Patches. At a high level, the ability to use unrestricted startup mode involves a two-part decision tree for OJVM PSU for each database; is OJVM installed and is OJVM used? The Appendix to My Oracle Support Document 2217053.1 provides detailed procedures for each specific situation where it is possible to use unrestricted startup mode.
There are pros and cons to each of the very specific situations and prerequisites are discussed in My Oracle Support Document 2217053.1. Therefore, Oracle recommends that the legacy requirement to restart each database into restricted startup upgrade mode be observed when possible.
The following steps load modified SQL files into the database. For an Oracle RAC environment, perform these steps on only one node.
Install the SQL portion of the patch by running the following command for a single instance environment.
cd $ORACLE_HOME/sqlpatch/26635834 sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> startup upgrade SQL> @postdeinstall.sql SQL> shutdown SQL> startup
For an Oracle RAC environment, reload the packages on one of the nodes using the following commands. Make sure no other instance of the database is up on the remote nodes.
cd $ORACLE_HOME/sqlpatch/26635834 sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> STARTUP SQL> alter system set cluster_database=false scope=spfile; SQL> SHUTDOWN SQL> STARTUP UPGRADE SQL> @postdeinstall.sql SQL> alter system set cluster_database=true scope=spfile; SQL> SHUTDOWN SQL> STARTUP
After installing the SQL portion of the patch, some packages could become INVALID. This will get recompiled upon access or you can run utlrp.sql to get them back into a VALID state.
cd $ORACLE_HOME/rdbms/admin sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> @utlrp.sql
If there are errors, see Section 8, "Known Issues".
For information about OPatch issues, see My Oracle Support Document 293369.1 OPatch documentation list.
For issues documented after the release of this Oracle JavaVM Component 11.2.0.4.171017 Database PSU, see My Oracle Support Document 2297782.1 Oracle JavaVM Component 11.2.0.4.171017 Database PSU Known Issues.
The known issues are as follows.
Relink fails for make target jox_refresh_knlopt when applying or rolling back this Oracle JavaVM Component 11.2.0.4.171017 Database PSU patch to or from a database home.
See My Oracle Support Document 1933203.1 Relink Fails for make target 'jox_refresh_knlopt' with "Oracle JavaVM Component Database PSU" Patch for more information.
There could be errors seen if postinstallation or postdeinstallation steps have not been run correctly. This happens when the Java system classes.bin in the database does not match that of the oracle executable.
To recover from this issue, complete the postinstallation (see Section 4, "Postinstallation") or postdeinstallation (see Section 7, "Post Deinstallation"), which will load updated classes.bin into memory and resolves the inconsistency.
If Oracle Database Vault is enabled, the following error can occur during the execution of the Post Installation or Deinstallation steps:
initjvmaux.drop_sros(); EXECUTE IMMEDIATE 'create or replace java system'; ... ORA-01031: insufficient privileges ORA-06512: at "SYS.INITJVMAUX", line 535 ORA-06512: at line 3
To recover from this issue, see the following My Oracle Support Document 1935120.1 ORA-01031 during Post Install / De-install for Database PSU or OJVM PSU
This patch includes the following bug fixes.
Oracle JavaVM Component 11.2.0.4.171017 Database PSU contains the following new fixes:
JavaVM
26637592 - Fix for Bug 26637592
The following bug fixes were provided in previous Oracle JavaVM Component releases:
JavaVM
26023002 - Fix for Bug 26023002 25494379 - Fix for Bug 25494379 25076732 - Fix for Bug 25076732 25067795 - ORA-29548 CONTINUES TO OCCUR ON A RAC NODE EVEN AFTER OJVM PSU POST-INSTALL 24534298 - EXIT THE SESSION WHILE ROLLING PATCHING FOR AN OJVM SESSION THAT MISMATCHES 24448240 - Fix for Bug 24448240 23265914 - Fix for Bug 23265914 22670385 - Fix for Bug 22670385 22253904 - ORA-07445[JOEVM_INVOKEVIRTUAL()+584] AFTER APPLYING THE COMBO PATCH 21744343 21911849 - ORA-29548 EVEN AFTER OJVM PSU POST-INSTALL IS RUN 22118835 - Fix for bug 22118835 21811517 - UPDATE NEEDED TO VERSION FILES FOR OJVM PSU5 21566944 - Fix for Bug 21566944 19176885 - Fix for Bug 19176885 21047766 - Fix for Bug 21047766 17528315 - ORA-29532 ON JAVAMAIL API AFTER UPGRADE TO 11.2.0.4 20408829 - Fix for Bug 20408829 19909862 - IMPROVEMENTS NEEDED FOR OJVM PSU 19895326 - Fix for Bug 19895326 19374518 - JAVAVM RELEASE VERSION NOT CORRECTLY PARSED FROM PSU LABEL NAMES 19699946 - REMOVE CHECK FROM JVMPSU.SQL FOR JAVAVM BEING VALID 19554117 - FIX TO ADDRESS JOX.O CONFLICT BETWEEN OJVM AND OTHER BUNDLES [JAVAVM SIDE FIX] 18933818 - ORA-29532: JAVA CALL TERMINATED BY UNCAUGHT JAVA EXCEPTION: JAVA.LANG.ILLEGALMON 18458318 - LOW QUALITY FONT IMAGE FILE CREATED USING JAVA CLASS AFTER UPGRADE TO 11.2.0.4 18166577 - JAVA STORED PROCEDURE FAILS WITH ORA-29532 IN 11.2.0.4 19231857 - Fix for Bug 19231857 19153980 - Fix for Bug 19153980 19058059 - Fix for Bug 19058059 17285560 - Fix for Bug 17285560 17201047 - Fix for Bug 17201047 17056813 - Fix for Bug 17056813 19223010 - Fix for Bug 19223010
JDBC
22675136 - Fix for Bug 22675136 17804361 - SET COLLECTION TYPE AS A BIND VARIABLE IS VERY SLOW AFTER UPGRADE TO 11.2.0.4 19006757 - Fix for Bug 19006757 14774730 - Fix for Bug 14774730
J/SQL
19007266 - Fix for Bug 19007266
Thin
19187988 - QUERIES FROM JDBC DRIVER RESULT IN CURSOR LEAK
Perform the steps in the following sections to upgrade an Oracle RAC database:
Perform the folowing steps to start the Oracle RAC database in upgrade mode.
Connect to SQL*Plus as sysdba on any of the nodes.
Execute the following command:
SQL> alter system set cluster_database=false scope=spfile;
Stop the database using the srvctl command:
$ srvctl stop database -d <dbname>
Connect to SQL*Plus on one of the nodes as sysdba.
Start the database in upgrade mode:
SQL> startup upgrade
Perform the following steps to start the Oracle RAC database in upgrade mode:
Connect to SQL*Plus as sysdba on the node where the instance was started in upgrade mode.
Execute the following command:
SQL> alter system set cluster_database=true scope=spfile;
Shut down the database:
SQL> shutdown
Start the database using the srvctl command:
$ srvctl start database -d <dbname>
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/us/corporate/accessibility/index.html.
Access to Oracle Support
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/support/contact.html or visit http://www.oracle.com/accessibility/support.html if you are hearing impaired.
Patch 26635834 - Oracle JavaVM Component 11.2.0.4.171017 Database PSU for UNIX
Copyright © 2006, 2017, Oracle and/or its affiliates. All rights reserved.
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.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
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.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark licensed through X/Open Company, Ltd.
This software or hardware and documentation may provide access to or information about 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 unless otherwise set forth in an applicable agreement between you and Oracle. 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, except as set forth in an applicable agreement between you and Oracle.