Patch 17027533 - 12.1.0.1.1 Patch Set Update
Released: October 15, 2013
This document is accurate at the time of release. For any changes and additional information regarding PSU 12.1.0.1.1, see these related documents that are available at My Oracle Support (http://support.oracle.com/):
Document 1571391.1 Patch Set Update and Critical Patch Update October 2013 Availability Document
Document 854428.1 Patch Set Updates for Oracle Products
Document 1571651.1 Oracle Database Patch Set Update 12.1.0.1.1 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.1.1 includes the fixes listed in Section 7, "Bugs Fixed by This Patch".
To install the PSU 12.1.0.1.1 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 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.1 |
|
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.0 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.1.1, perform the following actions to check the environment and to detect and resolve any one-off patch conflicts.
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.1 Patch 17272829 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, follow these steps:
Determine whether any currently installed one-off patches conflict with the PSU patch as follows:
unzip p17027533_12101_<platform>.zip cd 17027533 opatch prereq CheckConflictAgainstOHWithDetail -ph ./
The report will indicate the patches that conflict with PSU 17027533 and the patches for which PSU 17027533 is a superset.
Note that Oracle proactively provides PSU 12.1.0.1.1 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 p17027533_12101_<platform>.zip
cd 17027533
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.3, "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.
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.
Check the following log files in $ORACLE_HOME/sqlpatch/17027533/ for errors:
17027533_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;
There are no actions required for databases that have been upgraded or created after installation of PSU 12.1.0.1.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 a RAC Environment"
Section 4.4, "Patch Post-Deinstallation Instructions for a 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 17027533
If there are errors, refer to Section 5, "Known Issues".
Follow these steps:
For each database instance running on the Oracle home being patched, run the datapatch utility as described in Table 3.
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 rollback.
Check the following log files in $ORACLE_HOME/sqlpatch/17027533/ for errors:
17027533_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 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".
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 17027533
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 1571651.1 Oracle Database Patch Set Update 12.1.0.1.1 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
The following documents are references for this patch.
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 17027533.8 Database 12.1.0.1.1 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.1 contains the following new fixes:
Automatic Storage Management
| 15996344 - ORA-600 [KFFBADDBLK04] WHILE ADDING DATAFILE IN DATABASE AND ASM INSTANCE | |
| 16007562 - LNX64-12.1-HUB,+ASM INST HIT ORA-600 [KFFMAPLOCKCKPT10] IN CKPT | |
| 16178562 - PROXY INSTANCE DOESN'T TIMEOUT WHEN NO ASM INSTANCES ARE AVAILABLE | |
| 16195633 - LNX64-12.1-ADVM-FCF: MKFS HUNG FOR MORE THAN 2 DAYS | |
| 16227068 - LNX64-12.1-ASM-SCF:CANNOT CREATE DISKGROUP IF WE SET COMPATIBLE.ADVM 12.1.0.1.0 | |
| 16849982 - ARS0 CANNOT RELOCATE ASM SPFILE | |
| 17034172 - LX64_MAIN_CDB: ORA-7445 [KFFMTRANSLATE()+10836] DUE TO RANDOM SGA CORRUPTION | |
| 17273253 - 12C_ASM_X64:X: RESYNC CHECK-POINTING NEEDS TO BE DISABLED FOR 12.1.0.1 DBPSU 1 |
Buffer Cache Management
| 16465149 - MSGQ: HITS ORA-600 [KCBCHG1_16] | |
| 16964279 - AROLTP-C: LMS* TIMEOUT AFTER WAITING FOR EVENT 'LATCH: CACHE BUFFER CHAIN" |
Generic
| 14197853 - SYS.SNAP_XCMT$ NOT BEING CLEARED AFTER REFRESH FOR NESTED MVIEWS | |
| 16070351 - CDB: ORA-7445 [CTCDRV()+42824] [SIGSEGV] [ADDR:0X18] [PC:0X173C0F8] | |
| 16186165 - ORA-7445 [LXPTMUTF8()+17] DURING SQL EXECUTION TEST WORKLOAD | |
| 17330580 - INHERIT PRIVILEGES GRANTS NOT USABLE BY EDITIONED CODE |
High Availability
| 15986012 - MSGQ: LMS1 HITS ORA-600 [KJBMPRLST:!RCFG] | |
| 16286774 - CDB: OGG: IEV2 ABENDS WITH ORA-01405: FETCHED COLUMN VALUE IS NULL. | |
| 16313881 - CDB: OGG: IEV2 ABENDS WITH OGG-02077 AND ORA-600 [KRVUATLD] ON NEW PDB ADDITION | |
| 16392068 - MSGQ: LMS0 HITS ORA-600 [KJBMPOCR:DSB] | |
| 16448848 - LGSB: WIDETAB: ORA-600[17147] & ORA-600[600] & SQL APPLY STOPPED W/ SUPPL ALL | |
| 16465158 - MSGQ: INSTANCE CRASHED WITH ORA-600 [KJBMPOCR:DSB1] | |
| 16495802 - LGSB: WIDETAB:ORA-16211 & SQL APPLY STOPPED | |
| 16503473 - AROLTP-D: LMS1 CRASHED WITH ORA-600 [KJBREFBAS:!RES] | |
| 16524071 - INTRODUCE A TIME-OUT FOR DRM SLAVES WHEN ITERATING THROUGH LOCKS OF A PKEY | |
| 16524968 - CDB: ORA-600 [KCCOCX_02], [0X52C3B8068], [], | |
| 16543323 - OLTP_FA : ORA-29770: GLOBAL ENQUEUE PROCESS LMS - INSTANCE TERMINATED BY LMHB | |
| 16589507 - HM: KJZNSESS_STEADY NOT CLEARED CAUSES PREMATURE HUNG SESSION DETECTION | |
| 16634384 - LOGMINER BUILDER ASSERTS KRVUATLA20 AFTER UNREGISTERING PDB | |
| 16668226 - 12G_SLES_X64: ORA-00600 [723] & [15709] DURING STRESS TESTS | |
| 16674666 - AROLTP-D: LMS CRASHED WITH ORA-600 [KCLRECBST_9] | |
| 16694728 - MSGQ: LSM1 HITS ORA-600 [KJBLPGORM:!ANTILOCK] | |
| 16733884 - AROLTP-D: INSTANCE CRASHED WITH ORA-600 [KJBMPRLST:!RCFG] | |
| 16784143 - CDB (NON-RAC): ORA-600 [KCVFDB_PDB_SET_CLEAN_SCN: CLEANCKPT], [3], [0], [610153 | |
| 16856570 - AROLTP-D: LMS HITS ORA-600 [KJBRCVT:!S] DURING CDB TEST | |
| 16864359 - PHSB: CDB TOO MANY ORA-01110 DURING NEW PRIMARY DB OPEN AFTER FAILOVER | |
| 16991789 - ETL_PDML: ORA-600 [KJBLDRMRPST:INVSHAD] AND INSTANCE CRASH BY RMV0 PROCESS | |
| 17346196 - OLTP_FA + REDACT :ORA-29770: GLOBAL ENQUEUE PROCESS LMS -LMHB- INSTANCE CRASH |
Oracle Multitenant
| 16427054 - SR12.1.0.2PX_HYBRID_LOAD - TRC - KPDBIDTONAME | |
| 16443657 - CDB: OCITRANSCOMMIT() IS ABLE TO COMMIT FROM WRONG CONTAINER | |
| 16457621 - W2K8_12.1_CDB: ORA-600 [KKAEGEN_GET_EDITION_NAME_3] TERMINATE INSTANCE | |
| 16459685 - CDB (NON RAC) : ORA-44310 AND ORA-07445:[KSPGIP()+106] [SIGSEGV] | |
| 16483559 - CDB:COMMON USER NOT SYNCED ON PDB OPEN WITH FORCE OPTION | |
| 16485876 - FIRE LOGON TRIGGER DOING DDL IN OTHER CONTAINER GIVES ORA-600 [KTSSCNI1], | |
| 16603924 - XSTRM CDB W/ UPG'D PDBS, CREATE_OUTBOUND => ORA-600 [KKAEGEN_GET_EDITION_NAME_1] | |
| 16660558 - CDB: ORA-7445 [KSFD_IO] & [KSLWS_DMP_SESS_WAITSTACK] IN CREATE PDB UNDO CALLBACK | |
| 16663303 - SR12.1UPD-PLUGIN:DBMS_EDITIONS_UTILITIES FAILS WITH ORA-38817: INSUFFICIENT PRIV | |
| 16663465 - SR12.1UPD-PLUGIN -TRC -ORA-600KKDLGETBASEUSER2:AUTHIDTYPE/ORA-04024 SELF-DEADLOC | |
| 16675710 - CDB: ORA-7445 [KSUSDIINPROGRESS()+47] [SIGSEGV] [ADDR:0X18] [PC:0XB35190F] | |
| 16689109 - INVALID OBJECTS OCCUR WHEN UPGRADING IN A CDB | |
| 16697600 - CDB: "ALTER PDB ALL OPEN INSTANCES = ALL" ERRORS IF ALL OPEN ALREADY | |
| 16698577 - FA + REDACT: ORA-10387 AND ORA-600 [KGLRELEASEHANDLEREFERENCE1] | |
| 16705020 - LNX64-12.1-CDB: HIT ORA-7445 [KSP_PDB_SPFILE_INSERT] WHEN CREATING PDB | |
| 16707927 - PKT : ORA-600 [2130] - TRC - KCCUGG | |
| 16712618 - CDB:ORPHANED USER CAN BE UNLOCKED | |
| 16715647 - CDB-ADG:RESTRICTED OPEN FORCE FOR MULTIPLE PDBS DOES NOT WORK | |
| 16730813 - CDB:ORA-65144 WHEN DISABLING RESTRICTED SESSION IN ROOT | |
| 16772060 - TT12.1SQLFUZZ2: DBMS_PDB.SYNC_PDB THROWS ORA-600 [KGHSTACK_UNDERFLOW_INTERNAL_1] | |
| 16784167 - CDB(NON-RAC):ORA-00600: INTERNAL ERROR CODE, ARGUMENTS: [2801], [], [], [], [], | |
| 16784901 - TT12.1SQLFUZZ2: DESC ON RECREATED SUPPLIED OBJ THROWS ORA-7445 [KQLPRFD()+121] | |
| 16795944 - TT12.1SQLFUZZ2: PDB OPEN CRASHES AFTER LICENSE_MAX_USERS SET TO LESS THAN CURREN | |
| 16825779 - COMMON PROFILE RESOURCE LIMIT FOR PASSWORD VERIFY FUNCTION DISPLAYS FROM ROOT | |
| 16836849 - PHSB: CDB ORA-00600:[KTCALLOCXCB] DURING DB OPEN | |
| 16859937 - CDB: LOCAL USER CONVERTED TO COMMON | |
| 16902138 - RAC: ORA-7445 [RPIDRV] AFTER DROPPING A PDB | |
| 16921340 - CDB EXIT: NON-CDB TO PDB PLUGIN HANGS | |
| 16935643 - GOT ORA-600 [KQLUDP2] , [0X16EB753A8], [4] WHILE UPGRADING A PDB | |
| 16946613 - TT12.1SQLFUZZ2: CMN USER WHICH WAS LOCAL PRIOR TO SYNC NOT SYNCED ON PDB OPEN | |
| 16946990 - UNABLE TO INSTALL APEX IN LOCAL PDB 12C DATABASE.RAISES ORA-65050 | |
| 16993424 - CDB: ORA-600 [KKAEGEN_GET_EDITION_NAME_3], [3] | |
| 16994576 - CDB(NON-RAC): ORA-600 [KQLBBOTADD:3] | |
| 17000176 - HANG INSIDE CATCDB_INT.SQL CALLED USING CATCON.PL | |
| 16911800 - Fix for bug 16911800 | |
| 16919176 - Fix for bug 16919176 |
Oracle Security
| 16362358 - Fix for bug 16362358 |
Oracle Security Service
| 16212405 - Fix for bug 16212405 |
Oracle Space Management
| 16191248 - ILM : JOBS EXECUTION RATE IS SLOW AND HENCE PROGRESS IS DECREASING |
Oracle Storage Server Service Layer
| 16173738 - LNX64-12.1-HUB,DB INST HIT ORA-27603/ORA-27626 ISSUE | |
| 16788832 - ORA-27609: SMART I/O FAILED DUE TO A NETWORK ERROR TO THE CELL AFTER SHUTDOWN | |
| 16837842 - ORA-4030, ORA-7445 [KCFIS_DUMP_APP_STATE()+1868] AND ORA-600 [KCFIS_DECR_OVERHEA | |
| 16838328 - WRONG WAIT DB FILE SEQUENTIAL READ WHEN SMART SCAN DOWNGRADED TO BLOCK IO | |
| 16845022 - DISCREPANCY BETWEEN "READ" AND "READ TOTAL" STATS | |
| 16850996 - SERIAL FLASHCACHE SCAN PERFORMANCE DEGRADED | |
| 16863422 - ORA-600 [KXDAM_NOTIFY_CELL:IOCTLFAILED] DURING RPM UPGRADE | |
| 16864864 - FIX KCFIS SUCH THAT IT DOESNT SLOW DOWN FILE INITIALIZATION | |
| 16910734 - ORA-600 [KCFIS_CREATE_FLCUNKEEP_PAYLOAD:INVALID REQTYPE0] IN LRGSAOBJRBRM | |
| 16928832 - KCFIS RECONNECT DIAGNOSTICS NOT FULLY FUNCTIONAL WITH MULTIDB CHANGES | |
| 16930325 - 12C_RAC_X64:X: ORA-600 [KCFIS_TRANSLATE0] IN RDBMS FG AND P01Y |
Oracle Streams
| 16170787 - OGG : IR ABEND FOR EHCC ENABLED TABLES W/ FK-PK REFERENTIAL INTEGRITY CASES | |
| 16320173 - EXPLICIT TABLE/SCHEMA IN INLCUSION RULE SHOULD OVERRIDE WILDCARD EXCLUSION RULE | |
| 16523150 - ENABLING MIN SUPPLEMENTAL LOGGING AT THE DATABASE LEVEL CRASHES OGG REPLICAT IN | |
| 16590848 - ADD TRANDATA TABLENAME FAILS WITH ORA-1031 | |
| 16617325 - APPLY ABENDS WITH ORA-02292: INTEGRITY CONSTRAINT ERROR | |
| 16621274 - INBOUND SERVER PARAMETER ALLOW_DUPLICATE_ROWS NOT WORKING AS EXPECTED | |
| 16674842 - OCI ERROR FLUSHING XSTREAM INBOUND SERVER APPLY HANG | |
| 16679874 - STREAMS APPLY THROUGHPUT SIGNIFICANTLY AFFECTED BY DEPENDENCY WAITS | |
| 16787973 - OGG INTEGRATED REPLICAT ABENDS WITH OCI ERROR ORA-01403: NO DATA FOUND, SQL | |
| 16816103 - XIN ABORTS WITH ORA-4031 DUE TO MEMORY LEAK ON OCIXSTREAMINCOMMIT | |
| 16842274 - LATCH HIERARCHY VIOLATION IN KRVXB.C | |
| 16910001 - ORCL2ORCL:IR SOME UPDATES ARE IGNORED WHEN THE CLOB LENGHT IS VERY BIG | |
| 16964686 - LW CAPTURE GENERATES UNNECCESSARY REDO ON THE DATABASE |
Oracle Transaction Management
| 14355775 - OLTP_FA : ORA-7445 [KTRVLEAFROWSZ] [SIGSEGV] | |
| 14536110 - CDB_RAC : FDA + ILM: ORA-600 [KTFAPUT: WRONG PDB] - INSTANCE TERMINATED BY LMD0 | |
| 16372203 - Fix for bug 16372203 |
Oracle Virtual Operating System Services
| 16978185 - ORA-600 [KGHLATCH_REG4] ON A LARGE SYSTEM WITH >512 CPUS |
Patch Automation
| 17005047 - DATAPATCH SHOULD CALL CATBUNDLE FOR 12.1.* PSU |
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 17027533 - 12.1.0.1.1 Patch Set Update Release 12.1.0.1.1 for UNIX
Copyright © 2006, 2013, 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.