Patch 20299023 - Database Patch Set Update 12.1.0.2.3 (Includes CPUApr2015)
Released: April 14, 2015
This document is accurate at the time of release. For any changes and additional information regarding PSU 12.1.0.2.3, see these related documents that are available at My Oracle Support (http://support.oracle.com/):
Document 1967243.1 Patch Set Update and Critical Patch Update April 2015 Availability Document
Document 854428.1 Patch Set Updates for Oracle Products
Document 1967570.1 Oracle Database Patch Set Update 12.1.0.2.3 Known Issues
This document includes the following sections:
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.2.3 includes the fixes listed in Section 7, "Bugs Fixed by This Patch".
To install the PSU 12.1.0.2.3 patch, the Oracle home must have the 12.1.0.2.0 Database installed. Subsequent PSU patches can be installed on Oracle Database 12.1.0.2.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 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.
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.2.3 |
|
Client-Only Installations |
None |
|
Instant Client Installations |
None (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.4 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.
Before you install PSU 12.1.0.2.3, 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.2.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.2.3 Patch 20485724 should be applied to the Grid Infrastructure home and Database home using the readme instructions provided with the patch.
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 p20299023_12102_<platform>.zip cd 20299023 opatch prereq CheckConflictAgainstOHWithDetail -ph ./
The report will indicate the patches that conflict with PSU 20299023 and the patches for which PSU 20299023 is a superset.
Note that Oracle proactively provides PSU 12.1.0.2.3 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 p20299023_12102_<platform>.zip
cd 20299023
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 database instance running on the Oracle home being patched, run the datapatch utility as described in Table 2.
Table 2 Steps to Run the Datapatch Utility for Single Tenant Versus Multitenant (CDB/PDB)
| Steps | Single Tenant (non-CDB/PDB) | Steps | Multitenant (CDB/PDB) |
|---|---|---|---|
|
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 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.
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_sqlpatch view 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_BASE/cfgtoollogs/sqlpatch/20299023/<unique patch ID> for errors:
20299023_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.
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 Non-RAC Environment"
Section 4.2, "Patch Post-Deinstallation Instructions for a Non-RAC Environment"
Section 4.3, "Patch Deinstallation Instructions for Oracle RAC Environment"
Section 4.4, "Patch Post-Deinstallation Instructions for Oracle RAC Environment"
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 20299023
If there are errors, refer to Section 5, "Known Issues".
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 database instance running on the 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 Single Tenant Versus Multitenant (CDB/PDB)
| Steps | Single Tenant (non-CDB/PDB) | Steps | Multitenant (CDB/PDB) |
|---|---|---|---|
|
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 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.
The datapatch utility will then run the necessary rollback scripts. An entry will be added to the dba_registry_sqlpatch view 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.
Check the following log files in $ORACLE_BASE/cfgtoollogs/sqlpatch/20299023/<unique patch ID> for errors:
19303936_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.
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 20299023
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.2, "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.
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 1967570.1 Oracle Database Patch Set Update 12.1.0.2.3 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
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.
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 20299023.8 Database 12.1.0.2.3 Patch Set Update (PSU)
Document 1591141.1 12.1.0.2 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 1924126.1 that documents all the non-security bugs fixed in each 12.1.0.2 Patch Set Update (PSU).
PSU 12.1.0.2.3 contains the following new fixes:
Advance Queuing
19393542 - TIMESTAMP MISMATCHES ON RULE SET & EVALUATION CONTEXT
Automatic Storage Management
17274537 - ASM DISK GROUP FORCE DISMOUNTED DUE TO SLOW I/OS 19012119 - ORA-15196 WITH 5TB DISK SIZE IN 12.1 19035573 - AFD.CONF SHOULD BE UPDATED AFTER SETTING AFD_DISKSTRING EXPLICITLY 19238590 - ORA-600[KFDATBUPDATE_11_00] DURING DISKGROUP RESIZE OPERATION 19865345 - ODA: KFISODA DOES NOT IDENTIFY ODA ENVIRONMENT 20347562 - PARTNERSHIP INFORMATION PROVIDED BY OAKLIB OVERWRITTEN BY ASM
Buffer Cache Management
19619732 - MANY BLOCK DUMP INCORRECT SAY TABLESPACE IS ENCRYPTED
Generic
18306996 - INCORRECT SORT ORDER IN 11.2.0.4 EVEN WITH ORDER BY 18417036 - INSERT /*+APPEND*/ PRODUCE WRONG RESULTS AFTER UPGRADE FROM 11.2.0.1 TO 11.2.0.4 18856999 - WRONG RESULTS (WRONG CURSOR) WITH SCHEMA TABLE MASKING PUBLIC SYNONYM 18909599 - MOVE DATABASE FROM SHARE NFS TO SHARE NFS REPORT SQLPATCH FAILED 19018447 - DB PROC HIT ORA-07445 KSXPMSGCNCL() & ORA-00600 [15810] ERRORS 19023822 - DATA GETS TRUNCATED WHILE FILE SIZE OF THE FILE BEING TRANSFERRED IS > 4G 19183343 - WRONG RESULT RETURNED BY STATEMENT WHEN USING IN LIST. 19272708 - UNABLE TO UPGRADE PDBS IF STANDARD IS CHANGED 19291380 - DBUA FAILS WITH ORA-38804 WHEN THERE IS NO ORA$BASE EDITION IN SOURCE DATABASE 19487147 - CREATE EDITION ERRORS OUT WITH ORA-38807 19524384 - ORA-704, ORA-604, ORA-2240 AND DATABASE DOESN'T OPEN AFTER UPGRADE TO 11.2.0.4 19536415 - DB UPGRADE FAILS WITH ORA-600 [KKAEGSO: PUBLIC] 19606174 - ORA-2030 WHEN COMPILING PL/SQL CODE THAT SELECTS FROM REMOTE FIXED VIEW/TABLE 19637186 - RAC OPTION MISMATCH PRODUCES ERROR VIOLATION DURING PDB PLUG IN 19670108 - WITH CLAUSE QUERY WITH BINDS RUNS INTO ORA-600 [QCSFPBND] 19684504 - ORA-32036 EXECUTING WITH STATEMENT AFTER UPGRADE TO 12.1.0.2 19687159 - ORA-4030: OUT OF PROCESS MEMORY USING AGGREGATION 19730508 - ORA-600 [KWQDLPROCHSTENTRY:LTBAGI] 19896336 - DELETE AND UPDATE TRIGGERS NOT FIRING IN SOME DML AGAINST EDITIONED VIEWS 20235511 - PLACEHOLDER FOR TFA COLLECTOR VERSION 12.1.2.1.2 19915271 - Fix for bug 19915271
High Availability
19335438 - BROKER CONFIG WITH STANDBYS=NONE PDB RETURNS ORA-16843 19385656 - PDB PLUGIN GETS ORA-1274 ON STANDBY WHEN PRIMARY AND STANDBY SHARE SAME ASM 20425790 - LOGMINER PATCHES SHOULD TRANSPARENTLY FUNCTION IN A NON-PARITIONING ENABLED DB
Oracle Diagnostics Infrastructure
19512341 - "ADRCI PURGE" DELETES CURRENT DAEMON TRACES
Oracle Multitenant
18681056 - ORA-600[KGLBRK-BAD-LOCK] WAS INTERMITTENTLY SIGNALED IN CDB ENVIRONMENT. 19597583 - "EXTERNAL TABLE READS" DURING PDB CREATION 19841800 - RECOVER PDB WITH PRE-PLUGIN BACKUP FAILS
Oracle Security
16619249 - VPD : ORA-7445 IN [KZRTEVW] AND KZFTEVW
Oracle Security Service
19081128 - BOGUS CHARS RETURNED FROM NZDUUI6_GET_NAME COMMON_NAME ATTRIBUTE
Oracle Space Management
18202441 - LOGMINER SHOWS INCORRECT VALUE IN WHERE CLAUSE 18607546 - ORA-600 [KDBLKCHECKERROR], [43], [1971507], [6266] WITH CHAINED ROWS 18940497 - ORA-600 [KDBLKCHECKERROR] DOING UPDATE ON EHCC TABLE 19627012 - ORA-7445 [KD9IR2TCOMPUTETREESERCS()+160] DURING IMPDP
Oracle Streams
19644859 - STARTING OF IR FAILED WITH ORA-00904: "UTL_RAW"."CAST_TO_VARCHAR2 19658708 - APPLY IS GOING DOWN WHEN 2ND INSTANCE IS SHUTDOWN.
Oracle Transaction Management
19649152 - ORA-600 [KTURRUR_0] RUNNING OPM LOT COST PROCESSOR IN FDPSTP
Oracle Utilities
19065677 - ORA-604 AND ORA-904 AFTER UPGRADE FROM 11.2.0.2 19791377 - FLUSHING THE SHARED POOL TAKES A LONG TIME IN CDB UPGRADE FROM 12101 TO 12102 19805359 - DB 11.2 PRIVILEGES DIFFERENCE BETWEEN FRESH INSTALL AND UPGRADE FROM 10.2 19873610 - ORA-1658 DURING 12.1.0.2 UPGRADE FROM 11.1.0.7 19928926 - ORA-942 ERROR DURING 11203 TO 12.2 UPGRADE ON ASM FILE SYSTEM
Patch Automation
19315691 - CHANGE XMLTYPE DATATYPE TO CLOB FOR BUNDLE_DATA COLUMN IN REGISTRY$PATCH 19547370 - LOG OUTPUT OF DATAPATCH 19978542 - DOWNGRADE FROM 12.2 TO 12.1.0.2 FAILS WITH PRVTSQLPATCH COMPILATION WARNING. 20348653 - HIT ORA-01418:SPECIFIED INDEX DOES NOT EXISWHEN ROLLBACK GIPSU 20440930 - SQLPATCH/DATAPATCH HANGS ON JAPANESE LOCALES
XML Database
19358317 - Fix for bug 19358317
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 20299023 - Database Patch Set Update 12.1.0.2.3 (Includes CPUApr2015) for UNIX
Copyright © 2006, 2015, 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.