Go to primary content

Oracle® Database

Patch 23177541 - Oracle JavaVM Component 12.1.0.1.160719 Database PSU (Jul2016)

Released: July 19, 2016

This document describes how you can install Patch 23177541 - Oracle JavaVM Component 12.1.0.1.160719 Database PSU on your Oracle Database 12c Release 1 (12.1.0.1.0).

This patch is not Oracle RAC Rolling installable.

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 Database PSU 12.1.0.1.5 (Oct2014) or greater to be already installed.

This document is accurate at the time of release. For any changes and additional information regarding Oracle JavaVM Component 12.1.0.1.160719 Database PSU, see these related documents that are available at My Oracle Support (http://support.oracle.com/):

This document includes the following sections:

1 Patch Information

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 12.1.0.1.160719 Database PSU is cumulative and includes the Database CPU program security content including Oracle JavaVM Component 11.2.0.4.160719 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 12.1.0.1.160719 Database PSU (Jul2016)

Grid Infrastructure home

Oracle JavaVM Component 12.1.0.1.160719 Database PSU - Generic JDBC Patch 23727043

Client-Only Installations

Oracle JavaVM Component 12.1.0.1.160719 Database PSU - Generic JDBC Patch 23727043

Instant Client Installations

Oracle JavaVM Component 12.1.0.1.160719 Database PSU - Generic JDBC Patch 23727043

(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.)


2 Prerequisites

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.

  1. Read My Oracle Support Document 1929745.1 Oracle Recommended Patches -- "Oracle JavaVM Component Database PSU" (OJVM PSU) Patches.

  2. Ensure that the Oracle Database on which you are installing the patch or from which you are rolling back the patch is Oracle Database 12c Release 1 (12.1.0.1.0).

  3. Ensure that the 12.1.0.1.5 Patch Set Update (PSU) Oct2014 (Patch number: 19303936) or greater is already applied on the Oracle Database.

  4. You must use the OPatch utility version 12.1.0.1.1 or later to apply this patch. Oracle recommends that you use the latest released OPatch version for 12.1, which is available for download from My Oracle Support patch 6880880 by selecting the 12.1.0.1.1 release.

    For information about OPatch documentation, including any known issues, see My Oracle Support Document 293369.1 OPatch documentation list.

  5. Ensure that you set the ORACLE_HOME environment variable to the Oracle home of the Oracle Database.

  6. 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.

  7. 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
    
  8. (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> p23177541_12101_<PLATFORM_NAME>.zip
    
  9. (Only for Installation) Determine whether any currently installed interim patches conflict with this patch 23177541 as shown as follows:

    $ cd <PATCH_TOP_DIR>/23177541
    $ opatch prereq CheckConflictAgainstOHWithDetail -ph ./
    

    The report will indicate the patches that conflict with this patch and the patches for which the current 23177541 is a superset.


    Note:

    When OPatch starts, it validates the patch and ensures that there are no conflicts with the software already installed in the ORACLE_HOME. OPatch categorizes conflicts into the following types:
    • Conflicts with a patch already applied to the ORACLE_HOME, that is a subset of the patch you are trying to apply - In this case, continue with the patch installation because the new patch contains all the fixes from the existing patch in the ORACLE_HOME. The subset patch will automatically be rolled back prior to the installation of the new patch.

    • Conflicts with a patch already applied to the ORACLE_HOME - In this case, stop the patch installation and contact Oracle Support Services.


  10. 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, ASM, listeners, nodeapps, and CRS daemons) 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.

3 Installation

To install the patch, follow these steps.

  1. 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>/23177541
    
  2. Install the patch by running the following command:

    $ opatch apply
    

    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.

  3. Verify whether the patch has been successfully installed by running the following command:

    $ opatch lsinventory
    
  4. Start the services from the Oracle home.

  5. If there are errors, see Section 8, "Known Issues".

4 Postinstallation

To perform the postinstallation, follow these steps:

  1. The following steps load modified SQL files into the database.

    Datapatch is run to complete the post-install SQL deployment for the PSU. For further details about Datapatch, including Known Issues and workarounds to common problems, see: Database 12c Post Patch SQL Automation (Doc ID 1585822.1).

    1. For each separate database running on the same shared Oracle home being patched, run the datapatch utility as described in Table 2.

      Table 2 Steps to Run the Datapatch Utility for Standalone DB Versus Single/Multitenant (CDB/PDB) DB

      Steps Standalone DB Steps Single/Multitenant (CDB/PDB) DB

      1

      % sqlplus /nolog

      1

      % sqlplus /nolog

      2

      SQL> Connect / as sysdba

      2

      SQL> Connect / as sysdba

      3

      SQL> startup upgradeFoot 1 

      3

      SQL> startup upgradeFootref 1

      4

      SQL> quit

      4

      SQL> alter pluggable database all open upgrade;Foot 2 

      5

      % cd $ORACLE_HOME/OPatch

      5

      SQL> quit

      6

      % ./datapatch -verbose

      6

      % cd $ORACLE_HOME/OPatch

      7

      % sqlplus /nolog

      7

      % ./datapatch -verbose

      8

      SQL> Connect / as sysdba

      8

      % sqlplus /nolog

      9

      SQL> shutdown

      9

      SQL> Connect / as sysdba

      10

      SQL> startupFoot 3 

      10

      SQL> shutdown



      11

      SQL> startupFootref 3



      12

      SQL> alter pluggable database all open;


      Footnote 1 For an Oracle RAC environment, see Starting the Database for Post Installation Steps in an Oracle RAC Environment.

      Footnote 2 It is recommend the Post Install step be run on all pluggable databases; however, the following command (SQL> alter pluggable database PDB_NAME open upgrade) could be substituted to only open certain PDBs in the single/multitenant database. Doing so will result in the Post Install step only being run on the CDB and opened PDB's. To update a pluggable database at a later date (skipped or newly plugged in), open the database using the alter pluggable database command mentioned previously and rerun the datapatch utility. See My Oracle Support Document 1935365.1 Multitenant Unplug/Plug Best Practices for more information about the procedure for unplugging/plugging with different patch releases (in both directions).

      Footnote 3 For an Oracle RAC environment, see Restarting the Database after Running the Post Installation Steps in an Oracle RAC Environment.

      Starting the Database for Post Installation Steps in an Oracle RAC Environment

      On only one node, perform the following steps to start an Oracle RAC database in startup upgrade mode.

      sqlplus /nolog
      SQL> CONNECT / AS SYSDBA
      SQL> STARTUP
      SQL> alter system set cluster_database=false scope=spfile;
      
      $ORACLE_HOME/bin/srvctl stop database -d <dbname>
      sqlplus /nolog
      SQL> CONNECT / AS SYSDBA
      SQL> STARTUP UPGRADE
      

      Restarting the Database after Running the Post Installation Steps in an Oracle RAC Environment

      To start the database back in normal mode

      sqlplus /nolog
      SQL> CONNECT / AS SYSDBA
      SQL> alter system set cluster_database=true scope=spfile;
      SQL> SHUTDOWN
      $ORACLE_HOME/bin/srvctl start database -d <dbname>
      

      The datapatch utility will then run the necessary apply scripts to load the modified SQL files into the database. An entry will be added to the dba_registry_history and dba_registry_sqlpatch views reflecting the patch application. In the dba_registry_sqlpatch view, verify the Status for the APPLY is "SUCCESS". For any other status, refer to the following My Oracle Support note for additional information and actions: Document 1609718.1 Datapatch Known Issues.

    2. Check the following log files in $ORACLE_HOME/sqlpatch/23177541/ for errors:

      23177541_apply_<database SID>_<CDB name>_<timestamp>.log
      

      where database SID is the database SID, CDB name is the name of the multitenant container database, and timestamp is of the form YYYYMMMDD_HH_MM_SS.

      In addition, you can check the log files for catbundle in $ORACLE_HOME/cfgtoollogs/catbundle or $ORACLE_BASE/cfgtoollogs/catbundle for any errors:

      catbundle_PSU_<database SID>_APPLY_<TIMESTAMP>.log
      catbundle_PSU_<database SID>_GENERATE_<TIMESTAMP>.log
      

      where TIMESTAMP is of the form YYYYMMMDD_HH_MM_SS. If there are errors, refer to Section 8, "Known Issues".

  2. 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
    
  3. If there are errors, see Section 8, "Known Issues".

5 Post Installation Instructions for Databases Created or Upgraded after Installation of OJVM PSU in the Oracle Home

You must execute the steps in Section 4, "Postinstallation" for any new or upgraded database.

6 Deinstallation

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 each of the nodes:

  1. Deinstall the patch by running the following command:

    $ opatch rollback -id 23177541
    

    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.

  2. Start the services from the Oracle home.

  3. 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
    

7 Post Deinstallation

Perform the following steps:

  1. For each separate database running on the same shared Oracle home being patched, run the datapatch utility as described in Table 3.

    Table 3 Steps to Run the datapatch Utility for Standalone DB Versus Single/Multitenant (CDB/PDB) DB

    Steps Standalone DB Steps Multitenant (CDB/PDB)

    1

    % sqlplus /nolog

    1

    % sqlplus /nolog

    2

    SQL> Connect / as sysdba

    2

    SQL> Connect / as sysdba

    3

    SQL> startup upgradeFoot 1 

    3

    SQL> startup upgradeFootref 1

    4

    SQL> quit

    4

    SQL> alter pluggable database all open upgrade;Foot 2 

    5

    % cd $ORACLE_HOME/OPatch

    5

    SQL> quit

    6

    % ./datapatch -verbose

    6

    % cd $ORACLE_HOME/OPatch

    7

    % sqlplus /nolog

    7

    % ./datapatch -verbose

    8

    SQL> Connect / as sysdba

    8

    % sqlplus /nolog

    9

    SQL> shutdown

    9

    SQL> Connect / as sysdba

    10

    SQL> startupFoot 3 

    10

    SQL> shutdown



    11

    SQL> startupFootref 3



    12

    SQL> alter pluggable database all open;


    Footnote 1 For an Oracle RAC environment, see Starting the Database for Post Deinstallation Steps in an Oracle RAC Environment.

    Footnote 2 It is recommended the Post Install step be run on all pluggable databases; however, the following command (SQL> alter pluggable database PDB_NAME open upgrade) could be substituted to only open certain PDBs in the single/multitenant database. Doing so will result in the Post Install step only being run on the CDB and opened PDB's. To update a pluggable database at a later date (skipped or newly plugged in), open the database using the alter pluggable database command mentioned previously and rerun the datapatch utility. See My Oracle Support Document 1935365.1 Multitenant Unplug/Plug Best Practices for more information about the procedure for unplugging/plugging with different patch releases (in both directions).

    Footnote 3 For an Oracle RAC environment, see Restarting the Database after Running the Post Deinstallation Steps in an Oracle RAC Environment.

    Starting the Database for Post Deinstallation Steps in an Oracle RAC Environment

    On only one node, perform the following steps to start an Oracle RAC database in startup upgrade mode.

    sqlplus /nolog
    SQL> CONNECT / AS SYSDBA
    SQL> STARTUP
    SQL> alter system set cluster_database=false scope=spfile
    
    $ORACLE_HOME/bin/srvctl stop database -d <dbname>
    sqlplus /nolog
    SQL> CONNECT / AS SYSDBA
    SQL> STARTUP UPGRADE
    

    Restarting the Database after Running the Post Deinstallation Steps in an Oracle RAC Environment

    To start the database back in normal mode

    sqlplus /nolog
    SQL> CONNECT / AS SYSDBA
    SQL> alter system set cluster_database=true scope=spfile
    SQL> SHUTDOWN
    $ORACLE_HOME/bin/srvctl start database -d <dbname>
    

    The datapatch utility will then run the necessary apply scripts to load the modified SQL files into the database. An entry will be added to the dba_registry_history and dba_registry_sqlpatch views reflecting the patch application. In the dba_registry_sqlpatch view, verify the Status for the APPLY is "SUCCESS". For any other status, refer to the following My Oracle Support note for additional information and actions: Document 1609718.1 Datapatch Known Issues.

  2. Check the following log files in $ORACLE_HOME/sqlpatch/23177541/ for errors:

    23177541_rollback_<database SID>_<CDB name>_<timestamp>.log
    

    where database SID is the database SID, CDB name is the name of the multitenant container database, and timestamp is of the form YYYYMMMDD_HH_MM_SS.

    In addition, you can check the log files for catbundle in $ORACLE_HOME/cfgtoollogs/catbundle or $ORACLE_BASE/cfgtoollogs/catbundle for any errors:

    catbundle_PSU_<database SID>_APPLY_<TIMESTAMP>.log
    catbundle_PSU_<database SID>_GENERATE_<TIMESTAMP>.log
    

    where TIMESTAMP is of the form YYYYMMMDD_HH_MM_SS. If there are errors, refer to Section 8, "Known Issues".

  3. 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
    
  4. If there are errors, see Section 8, "Known Issues".

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 Oracle JavaVM Component 12.1.0.1.160719 Database PSU, see My Oracle Support Document 2136783.1 Oracle JavaVM Component 12.1.0.1.160719 Database PSU Known Issues.

The known issues are as follows.

Issue 1   

Relink fails for make target jox_refresh_knlopt when applying or rolling back this Oracle JavaVM Component 12.1.0.1.160719 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.

Issue 2   

An ORA-29548 error is issued if postinstallation or postdeinstallation steps have not been run correctly. This causes a mismatch error that occurs if you now tried to use Java as follows: ORA-29548: Java system class reported: release of 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.

9 Bugs Fixed by This Patch

This patch includes the following bug fixes.

9.1 Bug Fixes

Oracle JavaVM Component 12.1.0.1.160719 Database PSU contains the following new fixes:

JavaVM

   23265965 - Fix for Bug 23265965
   23265914 - Fix for Bug 23265914

JDBC

   22675136 - Fix for Bug 22675136

9.2 Bug Fixes in Previous Releases

The following bug fixes were provided in previous Oracle JavaVM Component releases:

JavaVM

   22670413 - Fix for Bug 22670413
   22670385 - Fix for Bug 22670385
   22118835 - Fix for Bug 22118835
   22118851 - Fix for Bug 22118851
   21811517 - UPDATE NEEDED TO VERSION FILES FOR OJVM PSU5
   19623450 - MISSING JAVA CLASSES AFTER UPGRADE TO JDK 7
   21566993 - Fix for Bug 21566993
   21566944 - Fix for Bug 21566944
   19176885 - Fix for Bug 19176885
   21047803 - Fix for Bug 21047803
   21047766 - Fix for Bug 21047766
   20408829 - Fix for Bug 20408829
   20408866 - Fix for Bug 20408866
   17615204 - ORA-7445 [PC:0X20001647D01] [SIGILL]
   17907157 - INCORRECTLY COMPILED JAVA STORED PROCEDURES ON HPUX.IA64
   19909862 - IMPROVEMENTS NEEDED FOR OJVM PSU
   19895362 - Fix for Bug 19895362
   19699946 - REMOVE CHECK FROM JVMPSU.SQL FOR JAVAVM BEING VALID
   16746190 - Fix for Bug 16746190
   19554117 - FIX TO ADDRESS JOX.O CONFLICT BETWEEN OJVM AND OTHER BUNDLES [JAVAVM SIDE FIX]
   17070459 - XF12.1.0.2FBA - TRC - JOXLU_DOLOOKUP
   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
   19245191 - Fix for Bug 19245191

JDBC

   19006757 - Fix for Bug 19006757
   14774730 - Fix for Bug 14774730

J/SQL

   19007266 - Fix for Bug 19007266

10 Documentation Accessibility

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 23177541 - Oracle JavaVM Component 12.1.0.1.160719 Database PSU (Jul2016) for UNIX

Copyright © 2006, 2016, 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 RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. 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 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

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 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.