Patch 24732082 - Database Patch Set Update 12.1.0.2.170117 (Includes CPUJan2017)
Released: January 17, 2017
This document is accurate at the time of release. For any changes and additional information regarding PSU 12.1.0.2.170117, see these related documents that are available at My Oracle Support (http://support.oracle.com/):
Document 2203916.1 Patch Set Update and Critical Patch Update January 2017 Availability Document
Document 854428.1 Patch Set Updates for Oracle Products
Document 2203888.1 Oracle Database Patch Set Update 12.1.0.2.170117 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.2.170117 includes the fixes listed in Section 7, "Bugs Fixed by This Patch".
To install the PSU 12.1.0.2.170117 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 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.
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.170117 |
|
Client-Only Installations |
PSU 12.1.0.2.161018 |
|
Instant Client Installations |
PSU 12.1.0.2.161018 (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.
Before you install PSU 12.1.0.2.170117, 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.170117 Patch 24917825 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 p24732082_12102_<platform>.zip cd 24732082 opatch prereq CheckConflictAgainstOHWithDetail -ph ./
The report will indicate the patches that conflict with PSU 24732082 and the patches for which PSU 24732082 is a superset.
Note that Oracle proactively provides PSU 12.1.0.2.170117 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 p24732082_12102_<platform>.zip
cd 24732082
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.
The MD5 hash is no longer considered sufficiently secure, see Section 3.3.4.
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_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/24732082/<unique patch ID> for errors:
24732082_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.
This patch now includes the OJVM Mitigation patch (Patch:19721304). If an OJVM PSU is installed or planned to be installed, no further actions are necessary. Otherwise, the workaround of using the OJVM Mitigation patch can be activated. As SYSDBA do the following from the admin directory:
SQL > @dbmsjdev.sql SQL > exec dbms_java_dev.disable
For more information on the OJVM mitigation patch, see Document 1929745.1 Oracle Recommended Patches -- "Oracle JavaVM Component Database PSU" (OJVM PSU) Patches.
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;
It has been determined that MD5 hash is no longer considered sufficiently secure. After this patch is applied, user creation is changed so that the MD5 hash is no longer generated by default. This only applies to users created after this patch is applied; existing users will not be changed. Review the following note to determine if you need to take further actions.
The MD5 hash is no longer considered sufficiently secure, see My Oracle Support Document 2194116.1 for more information.
You must execute the steps in Section 3.3.2, "Loading Modified SQL Files into the Database" for any new database. There are no actions required for databases that have been upgraded.
For more information, see My Oracle Support, 12.1:DBCA(Database Creation) does not execute ”datapatch (Doc ID 2084676.1).
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 24732082
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_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/24732082/<unique patch ID> for errors:
24732082_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.
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 24732082
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 2203888.1 Oracle Database Patch Set Update 12.1.0.2.170117 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. ... ld: Invalid non-PIC relocation for symbol ".rodata" in file "/scratch/installs/DB/64bit/DB/12101/server/lib/libpls12_pic.a[pfrdis.o]" (section index 11, offset 0x19a2). . . . OUI-67008:OPatch Session completed with warnings.
On Solaris systems, the following ignorable warnings may be encountered during relinking of target dlopenlib:
+ make -f $ORACLE_HOMEsqlplus/lib/ins_sqlplus.mk dlopenlib _FULL_LIBNAME=$ORACLE_HOMEsqlplus/lib/libsqlplus.so _LIBNAME=libsqlplus _LIBDIR=$ORACLE_HOMElib/ _LIBNAME_LIBS='$(libsqlplusLIBS)' _LIBNAME_EXTRALIBS='$(libsqlplusEXTRALIBS)' ld: warning: symbol '_init' not found, but .init section exists - possible link-edit without using the compiler driver ld: warning: symbol '_fini' not found, but .fini section exists - possible link-edit without using the compiler driver
For more information, see My Oracle Support Document 2193336.1 Applying Oct2016 PSU or DBBP Version 12.1.0.2.161018 'LD: WARNING: SYMBOL '_INIT' NOT FOUND'.
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 24732082.8 Database 12.1.0.2.170117 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.170117 contains the following new fixes:
Advanced Queuing
20181030 - ORA-7445 [KGGHSTINE_WFP()+114] 20401975 - MESSAGE FLOOD IN ALERT LOG KPONPST: KWQAMARK- WATERMARK FOR AQ NOTIFICATIONS 20936731 - ALTER SYSTEM ENABLE/DISABLE RESTRICTED SESSION BREAKS NOTIFICATIONS
Automatic Storage Management
19818513 - ASM ARB0 HIT ORA-700[KFFRELOCATE...]/ORA-600[KFDVAVOPINITAPE_NXTN 22458049 - ADD KFNRCL TRACE IN KFNRCL_GC 22695831 - REBALANCE IN ACFS ENABLED DISKGROUP FOR RESILVERING IS SUPER SLOW TO FOREVER
Generic
18254023 - INCONSISTENT QUERY RESULTS FOLLOWING DBMS_FLASHBACK_ARCHIVE.ENABLE_AT_VALID_TIM 18510194 - INSTANCE CRASHES - ORA-7445 [KTCNQSGAFREEQUERYINTERNAL], [KTCNQQMAPFREERECOVER] 18840932 - QUERY AGAINST COMPOSITE INTERVAL-PARTITIONED TABLE COULD LEAD TO INTERNAL ERROR 19469538 - LOADING OF DATA IN ECOL$ TABLE IS NON-OPTIMAL FOR QUERIES 19475971 - ORA-600 [17285] RUNNING DIFFERENT APPLICATION PACKAGES 20031873 - WRONG RESULTS ON PARALLEL QUERY USING TEMPORARY TABLE 20803014 - CREATE PARTITION TABLE FAILS WITH ORA-02149 IN 12C BUT SUCCEEDS IN 11G 20879709 - CONCURRENCY WITH DBMS_QOPATCH APIS WITH FIXED TABLE IMPLEMENTATION 21060755 - ORA-07445 [QCSISCOLINFRO()+620] ENCOUNTERED AFTER FIX FOR 19333670 21072646 - IN PDB, SMON_SCN_TIME ROWS ARE DELETED INCORRECTLY 21106027 - FULL DB IMPORT IS TERMINATING WITH ORA 600 [KQLCHG-PARENT-NOT-PINNED] 21196809 - ORA-04024: SELF-DEADLOCK DETECTED WHILE TRYING TO MUTEX PIN CURSOR 21285458 - ORA-00600 [QKAFFSINDEX5], [], [], [] IN FUSION RUNS DURING PARSE 21294938 - ORA-600 [KKDLGETBASEUSER2:AUTHIDTYPE], [0], [48], [XDB_WEBSERVICES] 21354456 - QUERY OVER DBLINK HANGING WAITING FOR "INACTIVE TRANSACTION BRANCH" 21380789 - PMON HIT SIGSEGV IN KGLLCCL() DURING PROCESS CLEANUP 22077517 - UNIFIED_AUDIT_TRAIL: MEMORY LEAK DUE TO KTLI NOT FREEING LOB LOCATORS 22365117 - SQL QUERY COMBINING TABLE FUNCTION WITH JOIN YIELDS WRONG JOIN RESULTS 22529728 - EXADATA : WRONG RESULTS WITH +APPEND HINT 23220453 - ORA-3137: TTC PROTOCOL INTERNAL ERROR: [12333] 23314180 - QI DOES NOT RELEASE LOCK WITH EVENT 18219841 SET 24523374 - FA:REL12 12C CDB: BOOTSTRAP TIMED OUT AFTER 120 SECONDS 24690216 - CHANGE DEFAULT OF QPINV TO USE GV$ RATHER THAN JOBS 24739928 - T7-2 LOS: ORA 7445 [KGLMUTEXCLEANUPALL] WITH SPARSE DG WORKLOAD
High Availability
20315311 - RMAN-5119: RECOVERY CAN NOT BE DONE TO A CONSISTENT STATE 20882568 - INSTANCE CRASH WITH ORA-00600: INTERNAL ERROR CODE, ARGUMENTS: [KJBMICLO:CL], [0 21059919 - ORA-600 [KJCCQMG:ESM] IN CTWR DURING RECONFIGURATION,11.2.0.4 OR HIGHER 21476308 - SUPERSEDED FIX FOR BUG 18070699-FAILURE IN RMAN DUPLICATE COMMAND WITH ORA-1017 22294260 - ORA-600 [KRR_PROCESS_READ_ERROR_1] DURING STANDBY RTA RECOVERY ON AIX 22809871 - ORA-04031- "LARGE POOL","CTWR DBA BUFFER" - INSTANCE CRASH/RESTARTED
Oracle Multitenant
21575362 - CDB: HIT ORA 7445 [PTG_ND] DURING APP SYNC
Oracle Security
18974476 - UNEXPECTED RESULTS WITH MERGE STATEMENT AND VPD POLICY 20562898 - CONN / AS SYSDBA TAKES MORE THAN A MINUTE ON A NOT STARTED INSTANCE 21133343 - *.AUD FILE IS GENERATED THOUGH UNIFIED AUDITING=TRUE AND AUDIT_TRAIL=NONE 23197103 - Fix for bug 23197103
Oracle Space Management
21542577 - ORA-00600: INTERNAL ERROR CODE, ARGUMENTS: [KTSSTRM_SEGMENT-A *21896069 - EXADATA: ORA-08103: OBJECT NO LONGER EXISTS *22022760 - HIGH CPU UTILIZATION BY SMON PROCESS IS CONTINUING IN ADG *22496904 - IMCP:CREATE INDEX FAILING WITH ORA-01950:NO PRIVILEGES ON TABLESPACE'SYSTEM'
Oracle Universal Installer
24413809 - [FATAL] [INS-32167] ERROR REPORTED WHILE RUNNING CONFIG.SH
Oracle Utilities
20591183 - PREUPGRD.SQL: CHECK TO ADJUST JOB_QUEUE_PROCESSES SHOULD BE REMOVED IF IT'S >0 24812585 - TRACKING BUG TO INCLUDE ORACHK 12.2.0.1.1 IN JANUARY 2017 PSU 24825843 - PLACEHOLDER FOR TFA COLLECTOR VERSION 12.1.2.8.3 INCLUSION IN JAN 2017 PSU
Oracle Virtual Operating System Services
20677396 - ORA-600 [526] WHILE GATHERING FIXED STATISTICS 21172913 - ORA-00600 [17113]
PL/SQL
18307021 - COMPILATION OF CODE CRASHES WHEN POINTING TO DATABASE 12.1
Patch Automation
22165897 - INCORRECT BEHAVIOR WITH DATAPATCH -ROLLBACK 22359063 - ZDT: DETERMINE PATCH METADATA FROM XML DESCRIPTOR 23025340 - DATAPATCH CHANGES TO SUPPORT SWITCHING TRAINS 23170620 - STORE CONTENTS OF PATCH DIRECTORY INTO DATABASE 23324000 - SWITCH_DATAPATCH: POTENTIAL TO HAVE PARTIALLY INSTALLED FIXES 23501901 - DATAPATCH ROLLBACK DBPSU ON 1ST NODE WHEN ROLLBACK DBBP 23533524 - 1210719DBBP_LINUX: DATAPATCH FAIL ON 2ND NODE SINCE BOOTSTRAP TIME OUT 24285405 - DATAPATCH REPORTS ERRORS IF ECHO IS ON FOR PROMPT IGNORABLE ERRORS LINE 24308635 - 12102160719DBBP:DATAPATCH ROLLBACK FAILED WITH PRECHECK FAILED 24397438 - SWITCH_DATAPATCH:DATAPATCH FAILED WITH ORA-06512 DURING DERTERMING STATE 24437510 - DATAPATCH FAILED WITH "THE DATABASE MUST BE IN UPGRADE MODE" 24693382 - MISSING NODES OF BUNDLE PATCHES DISPLAYED INCORRECTLY 24808595 - PDB PLUG IN VIOLATION ERROR IS SEEN ON PLUGGING IN REL 12 FA STARTER PDB 25056052 - DATAPATCH REPORTS ERROR FROM COMMENTS OF SQL FILE 25161298 - 12102170117DBBP_LINUX:RETRY AFTER TIMEOUT DURING BOOTSTRAP 25264559 - ALIAS DBPSU TO PSU FOR BUNDLE SERIES
Server Manageability
16777441 - WRH$_SQL_BIND_METADATA IS NOT PURGED BY AUTO PURGE / DEEP PURGE. 23089357 - APPSST12102:SHUTDOWN FAILS WITH ORA-449 "BACKGRND PROCESS ''MMNL' UNEXPECTEDLY
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 24732082 - Database Patch Set Update 12.1.0.2.170117 (Includes CPUJan2017) 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 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.