Patch 23054354 - Database Patch Set Update 12.1.0.1.160719 (Jul2016)
Released: July 19, 2016
This document is accurate at the time of release. For any changes and additional information regarding PSU 12.1.0.1.160719, see these related documents that are available at My Oracle Support (http://support.oracle.com/):
Document 2136219.1 Patch Set Update and Critical Patch Update July 2016 Availability Document
Document 854428.1 Patch Set Updates for Oracle Products
Document 2136771.1 Oracle Database Patch Set Update 12.1.0.1.160719 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.
Patch Set Update (PSU) patches are cumulative. That is, the content of all previous PSUs is included in the latest PSU patch.
PSU 12.1.0.1.160719 includes the fixes listed in Section 7, "Bugs Fixed by This Patch".
To install the PSU 12.1.0.1.160719 patch, the Oracle home must have the 12.1.0.1.0 Database installed. Subsequent PSU patches can be installed on Oracle Database 12.1.0.1.0 or any PSU with a lower 5th numeral version than the one being installed.
This patch is 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 Data Guard Standby-First Installable. See My Oracle Support Document 1265700.1 Oracle Patch Assurance - Data Guard Standby-First Patch Apply for details on how to remove risk and reduce downtime when applying this patch.
This patch contains a security fix due to which a SELECT query's plan MAY change under the following conditions:
The SELECT queries a table protected with a Fined Grained Auditing policy
And the policy condition is NULL
Table 1 describes installation types and security content. For each installation type, it indicates the most recent PSU patch to include 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 PSU is listed, then apply that or any later PSU patch to be current with security fixes.
Table 1 Installation Types and Security Content
| Installation Type | Latest PSU with Security Fixes |
|---|---|
|
Server homes |
PSU 12.1.0.1.160719 |
|
Client-Only Installations |
PSU 12.1.0.1.160719 |
|
Instant Client Installations |
PSU 12.1.0.1.160719 (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.) |
This section includes the following section:
You must use the OPatch utility version 12.1.0.1.7 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.0 release.
For information about OPatch documentation, including any known issues, see My Oracle Support Document 293369.1 OPatch documentation list.
These instructions are for all Oracle Database installations.
Database PSU 12.1.0.1.160719 is packaged as a non-composite patch and hence installing it will rollback all prior overlay patches applied. This will increase the downtime necessary to perform the installation. Before you install PSU 12.1.0.1.160719, perform the following actions to check the environment and to detect and resolve any one-off patch conflicts.
From October 2014 onwards, the Oracle JavaVM Component 12.1.0.1.x Database PSU patch is also available as a separate patch. This patch is not Oracle RAC Rolling Installable. For customers wanting to install both patches together during a single downtime window, follow the various Patching Options listed in the My Oracle Support Document 1929745.1 - Oracle Recommended Patches -- "Oracle JavaVM Component Database PSU" (OJVM PSU) Patches.
If you are installing the PSU to an environment that has a Grid Infrastructure home, note the following:
Grid Infrastructure PSU 12.1.0.1.160719 Patch 23273935 should be applied to the Grid Infrastructure home and Database home using the readme instructions provided with the patch for Linux.x86-64, Solaris SPARC, and Solaris x86-64 platforms.
Grid Infrastructure PSU 12.1.0.1.160719 Patch 23273958 should be applied to the Grid Infrastructure home and Database home using the readme instructions provided with the patch for IBM AIX, Linux on IBM System z, and HP-UX Itanium platforms.
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, in which case you can set your PATH definition as follows:
export PATH=$PATH:/usr/ccs/bin
For an introduction to the PSU one-off patch concepts, see "Patch Set Updates Patch Conflict Resolution" in My Oracle Support Document 854428.1 Patch Set Updates for Oracle Products.
The fastest and easiest way to determine whether you have one-off patches in the Oracle home that conflict with the PSU, and to get the necessary conflict resolution patches, is to use the Patch Recommendations and Patch Plans features on the Patches & Updates tab in My Oracle Support. These features work in conjunction with the My Oracle Support Configuration Manager. Recorded training sessions on these features can be found in Document 603505.1.
However, if you are not using My Oracle Support Patch Plans, the My Oracle Support Conflict Checker tool 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, it will automatically request a resolution, which you can monitor in the Plans and Patch Requests region of the Patches & Updates tab.
For more information, see Knowledge Document 1091294.1, How to use the My Oracle Support Conflict Checker Tool.
Or, use the following steps to manually discover conflicts and resolutions:
Determine whether any currently installed one-off patches conflict with the PSU patch as follows:
unzip p23054354_12101_<platform>.zip cd 23054354 opatch prereq CheckConflictAgainstOHWithDetail -ph ./
The report will indicate the patches that conflict with PSU 23054354 and the patches for which PSU 23054354 is a superset.
Note that Oracle proactively provides PSU 12.1.0.1.160719 one-off patches for common conflicts.
Use My Oracle Support Document 1321267.1 Database Patch conflict resolution to determine, for each conflicting patch, whether a conflict resolution patch is already available, and if you need to request a new conflict resolution patch or if the conflict may be ignored.
When all the one-off patches that you have requested are available at My Oracle Support, proceed with Section 3.2, "Patch Installation Instructions".
Follow these steps:
If you are using a Data Guard Physical Standby database, you must install this patch on both the primary database and the physical standby database, as described by My Oracle Support Document 278641.1.
If this is a RAC environment, install the PSU patch using the OPatch rolling (no downtime) installation method as the PSU patch is rolling RAC installable. Refer to My Oracle Support Document 244241.1 Rolling Patch - OPatch Support for RAC.
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.
Set your current directory to the directory where the patch is located and then run the OPatch utility by entering the following commands:
unzip p23054354_12101_<platform>.zip
cd 23054354
opatch apply
If there are errors, refer to Section 5, "Known Issues".
After installing the patch, perform the following actions:
Apply conflict resolution patches as explained in Section 3.3.1.
Load modified SQL files into the database, as explained in Section 3.3.2.
Upgrade Oracle Recovery Manager catalog, as explained in Section 3.3.3.
Apply the patch conflict resolution one-off patches that were determined to be needed when you performed the steps in Section 3.1.4, "One-off Patch Conflict Detection and Resolution".
The following steps load modified SQL files into the database. For a RAC environment, perform these steps on only one node.
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).
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 |
|
1 |
|
|
2 |
|
2 |
|
|
3 |
|
3 |
|
|
4 |
|
4 |
|
|
5 |
|
5 |
|
|
6 |
|
6 |
|
|
7 |
|
Footnote 1 It is recommended the Post Install step be run on all pluggable databases; however, the following command (SQL> alter pluggable database PDB_NAME open ) 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).
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.
Check the following log files in $ORACLE_HOME/sqlpatch/23054354/ for errors:
23054354_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 5, "Known Issues".
If you are using the Oracle Recovery Manager, the catalog needs to be upgraded. Enter the following command to upgrade it:
$ rman catalog username/password@alias RMAN> UPGRADE CATALOG;
You must execute the steps in Section 3.3.2, "Loading Modified SQL Files into the Database" for any new or upgraded database.
These instructions apply if you need to deinstall the patch.
Section 4.1, "Patch Deinstallation Instructions for a Multitenant Environment"
Section 4.2, "Patch Deinstallation Instructions for a Non-RAC Environment"
Section 4.3, "Patch Post-Deinstallation Instructions for a Non-RAC Environment"
Section 4.4, "Patch Deinstallation Instructions for Oracle RAC Environment"
Section 4.5, "Patch Post-Deinstallation Instructions for Oracle RAC Environment"
The following known issues can be encountered when datapatch is invoked to complete the deinstallation of the PSU:
Bug 17421502
Bug 17490498
Bug 18126350
Because the fixes for these 3 issues conflict, merge patches have been created for the following versions:
For 12.1.0.1, use MLR bug 18524486.
For 12.1.0.1.1PSU, use MLR bug 18524636.
For 12.1.0.1.2PSU, use MLR bug 18524488.
For details, see My Oracle Support Document: 1609718.1 Datapatch Known Issues.
To avoid these issues, the following steps should be taken:
Shut down the instance.
Download the patch for the MLR Bug from My Oracle Support.
Run the OPatch utility specifying these arguments:
opatch rollback -id 23054354 opatch apply -id <MLR patch corresponding to the 12.1 version>
If there are errors, refer to Section 5, "Known Issues".
Start the instance.
Run the datapatch utility to complete the patch deinstallation.
Follow these steps:
Shut down all instances and listeners associated with the Oracle home that you are updating. For more information, see Oracle Database Administrator's Guide.
Run the OPatch utility specifying the rollback argument as follows.
opatch rollback -id 23054354
If there are errors, refer to Section 5, "Known Issues".
After deinstalling the patch, perform the following actions:
Datapatch is run to complete the post-deinstall 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).
Follow these steps:
For each separate database running on the same shared Oracle home being patched, run the datapatch utility as described in Table 3. If this is Oracle RAC, run datapatch on only one instance.
Table 3 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 |
|
1 |
|
|
2 |
|
2 |
|
|
3 |
|
3 |
|
|
4 |
|
4 |
|
|
5 |
|
5 |
|
|
6 |
|
6 |
|
|
7 |
|
Footnote 1 It is recommended the Post Install step be run on all pluggable databases; however, the following command (SQL> alter pluggable database PDB_NAME open ) 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).
The datapatch utility will then run the necessary rollback scripts. 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 ROLLBACK 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.
If the OJVM PSU was applied for a previous PSU patch, you may see invalid Java classes after execution of the catbundle.sql script in the previous step. If this is the case, run utlrp.sql to re-validate these Java classes.
cd $ORACLE_HOME/rdbms/admin sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> @utlrp.sql
Check the following log files in $ORACLE_HOME/sqlpatch/23054354/ for errors:
23054354_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 found in $ORACLE_BASE/cfgtoollogs/catbundle and is named catbundle_PSU_<database SID>_ROLLBACK_<TIMESTAMP>.log where TIMESTAMP is of the form YYYYMMMDD_HH_MM_SS. If there are errors, refer to Section 5, "Known Issues".
If you are using the Oracle Recovery Manager, the catalog needs to be upgraded. Enter the following command to upgrade it:
$ rman catalog username/password@alias RMAN> UPGRADE CATALOG; RMAN> UPGRADE CATALOG;
Patch deinstallation instructions for Oracle RAC includes these environments:
Follow these steps for each node in the cluster, one node at a time.
Shut down the instance on the node.
Run the OPatch utility specifying the rollback argument as follows.
opatch rollback -id 23054354
If there are errors, refer to Section 5, "Known Issues".
Start the instance on the node as follows:
srvctl start instance
Follow the instructions listed in Section Section 4.3, "Patch Post-Deinstallation Instructions for a Non-RAC Environment" only on the node for which the steps in Section 3.3.2, "Loading Modified SQL Files into the Database" were executed during the patch application.
All other instances can be started and accessed as usual while you are executing the deinstallation steps.
After rolling back PSU 12.1.0.1.160719, apply the one off patch for Bug 17421502, before doing the datapatch rollback. The fix for Bug 17421502 should always be in place when you do the datapatch rollback.
For information about OPatch issues, see My Oracle Support Document 293369.1 OPatch documentation list.
For issues documented after the release of this PSU, see My Oracle Support Document 2136771.1 Oracle Database Patch Set Update 12.1.0.1.160719 Known Issues.
Other known issues are as follows.
The following ignorable errors may be encountered while running the datapatch/catbundle.sql script or its rollback script:
ORA-29809: cannot drop an operator with dependent objects ORA-29931: specified association does not exist ORA-29830: operator does not exist ORA-00942: table or view does not exist ORA-00955: name is already used by an existing object ORA-01430: column being added already exists in table ORA-01432: public synonym to be dropped does not exist ORA-01434: private synonym to be dropped does not exist ORA-01435: user does not exist ORA-01917: user or role 'XDB' does not exist ORA-01920: user name '<user-name>' conflicts with another user or role name ORA-01921: role name '<role name>' conflicts with another user or role name ORA-01952: system privileges not granted to 'WKSYS' ORA-02303: cannot drop or replace a type with type or table dependents ORA-02443: Cannot drop constraint - nonexistent constraint ORA-04043: object <object-name> does not exist ORA-29832: cannot drop or replace an indextype with dependent indexes ORA-29844: duplicate operator name specified ORA-14452: attempt to create, alter or drop an index on temporary table already in use ORA-06512: at line <line number>. If this error follow any of above errors, then can be safely ignored. ORA-01927: cannot REVOKE privileges you did not grant ORA-02289: sequence does not exist
On HP-UX Itanium systems, the following ignorable warnings may be encountered during the relinking of the client_sharedlib:
OUI-67215: OPatch found the word "error" in the stderr of the make command. Please look at this stderr. You can re-run this make command. Stderr output: ld: Invalid dynamic relocation needed for read-only section, in input file /scratch/installs/DB/64bit/DB/12101/server/lib/libpls12.a[pfrd.o], for symbol .text at offset b00 ... ld: Invalid non-PIC relocation for symbol ".rodata" in file "/scratch/installs/DB/64bit/DB/12101/server/lib/libpls12.a[plzsql.o]" (section index 5, offset 0x92). 39651 errors. ... ld: Invalid non-PIC relocation for symbol ".rodata" in file "/scratch/installs/DB/64bit/DB/12101/server/lib/libpls12.a[plzsql.o]" (section index 5, offset 0x92). 39651 errors. OUI-67008:OPatch Session completed with warnings.
In the event of a rollback of this PSU, you may experience an INVALID object:
PRIVATE_JDBC SYS PACKAGE BODY
These 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
datapatch may be incorrectly pointing to the wrong apply or rollback logs when multiple patches are being installed or rolled back. Manually review the catbundle APPLY, GENERATE, or ROLLBACK logs for errors.
datapatch is performing duplicate executions of catbundle during APPLY and ROLLBACK operations. This will be seen by looking at the registry$history and dba_registry_sqlpatch views. This can be ignored.
The following documents are references for this patch.
Document 1585822.1 Database 12c Post Patch SQL Automation
Document 293369.1 OPatch documentation list
Document 360870.1 Impact of Java Security Vulnerabilities on Oracle Products
Document 1321267.1 Database Patch conflict resolution
Document 23054354.8 Database 12.1.0.1.160719 Patch Set Update (PSU)
Document 1591141.1 12.1.0.1 Patch Set Updates - List of Fixes in each PSU
Document 1561792.2 Patching Assistant: Oracle Database/Client - Select PSU/SPU (aka CPU)
This patch includes the following bug fixes.
See My Oracle Support Document 1591141.1 that documents all the non-security bugs fixed in each 12.1.0.1 Patch Set Update (PSU).
PSU 12.1.0.1.160719 contains the following new fixes:
Generic
21291274 - Fix for bug 21291274
Oracle Security
21241829 - Fix for bug 21241829 22296366 - Fix for bug 22296366 22507210 - Fix for bug 22507210 22507234 - Fix for bug 22507234
Oracle Utilities
22380919 - Fix for bug 22380919
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/us/corporate/accessibility/support/index.html if you are hearing impaired.
Patch 23054354 - Database Patch Set Update 12.1.0.1.160719 (Includes CPUJul2016) 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.