Combo of OJVM Component 11.2.0.3.1 DB PSU + DB PSU 11.2.0.3.12 (Oct2014)
Released: October 14, 2014
This document is accurate at the time of release. For any
changes and additional information regarding PSU 11.2.0.3.12,
see these related documents that are available at My Oracle
Support (http://support.oracle.com/):
Document 1912224.1 Patch Set Update and Critical Patch Update October 2014 Availability Document
Document 854428.1 Patch Set Updates for Oracle Products
Document 1911751.1 Oracle Database Patch Set Update 11.2.0.3.12 Known Issues
Document 1933271.1 Oracle JavaVM Component 11.2.0.3.1 Database PSU 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 11.2.0.3.12 includes the fixes listed in Section 7, "Bugs Fixed by This Patch".
To install the PSU 11.2.0.3.12 patch, the Oracle home must have the 11.2.0.3.0 Database installed. Subsequent PSU patches can be installed on Oracle Database 11.2.0.3.0 or any PSU with a lower 5th numeral version than the one being installed.
This patch is not 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 11.2.0.3.12 Oracle JavaVM Component 11.2.0.3.1 Database PSU (Oct2014). |
|
Client-Only Installations |
PSU 11.2.0.3.7 to address CVE-2013-3751. Oracle JavaVM Component 11.2.0.3.1 Database PSU for CVE-2014-6544 & CVE-2014-4289 (JDBC). |
|
Instant Client Installations |
PSU 11.2.0.3.7 to address CVE-2013-3751. Oracle JavaVM Component 11.2.0.3.1 Database PSU for CVE-2014-6544 & CVE-2014-4289 (JDBC). (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 11.2.0.3.0 or later to apply this patch. Oracle recommends that you use the latest released OPatch version for 11.2, which is available for download from My Oracle Support patch 6880880 by selecting the 11.2.0.0.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 11.2.0.3.12, perform the following actions to check the environment and to detect and resolve any one-off patch conflicts.
Section 3.1.1, "Applying Database PSU Along Side the "Oracle JavaVM Component Database PSU" Patch"
Section 3.1.4, "One-off Patch Conflict Detection and Resolution"
From October 2014 onwards, the "Oracle JavaVM Component 112031 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 112031 Database PSU" Patches.
If you are installing the PSU to an environment that has a Grid Infrastructure home, note the following:
Grid Infrastructure PSU 11.2.0.3.12 Patch 19440385 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 p19791427_11203_<platform>.zip cd 19791427/19121548 opatch prereq CheckConflictAgainstOHWithDetail -ph ./
The report will indicate the patches that conflict with PSU 19121548 and the patches for which PSU 19121548 is a superset.
Note that Oracle proactively provides PSU 11.2.0.3.12 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".
Conflicting patches should be rolled back before applying
the patch, otherwise opatch apply will
report conflicts again.
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 p19791427_11203_<platform>.zip
cd19791427/19121548
opatch apply
cd ../19282015
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.
For each database instance running on the Oracle
home being patched, connect to the database using
SQL*Plus. Connect as SYSDBA and run postinstall.sql
script as follows:
cd $ORACLE_HOME/sqlpatch/19282015 sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> STARTUP SQL> @postinstall.sql SQL> QUIT
For each database instance running on the Oracle
home being patched, connect to the database using
SQL*Plus. Connect as SYSDBA and run the catbundle.sql
script as follows:
cd $ORACLE_HOME/rdbms/admin sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> @catbundle.sql psu apply SQL> QUIT
The catbundle.sql execution is
reflected in the dba_registry_history view by a row
associated with bundle series PSU.
For information about the catbundle.sql
script, see My Oracle Support Document 605795.1
Introduction to Oracle Database
catbundle.sql.
Check the following log files 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 11.2.0.3.12.
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:
Verify that an $ORACLE_HOME/rdbms/admin/catbundle_PSU_<database SID>_ROLLBACK.sql
file exists for each database associated with this
ORACLE_HOME. If this is not the case, you must execute
the steps in Section 3.3.2,
"Loading Modified SQL Files into the Database"
against the database before deinstalling the PSU.
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.
optch rollback -id 19282015 opatch rollback -id 19121548
If there are errors, refer to Section 5, "Known Issues".
Follow these steps:
|
Note: A known issue exists if 11.2.0.3.1 is deinstalled after deinstalling 11.2.0.3.2. See Section 5, "Known Issues". |
Start all database instances running from the Oracle home. (For more information, see Oracle Database Administrator's Guide.)
Install the SQL portion of the patch by running the following command. For an Oracle RAC environment, reload the packages on one of the nodes.
cd $ORACLE_HOME/sqlpatch/19282015 sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> @postdeinstall.sql
For each database instance running out of the ORACLE_HOME,
connect to the database using SQL*Plus as SYSDBA
and run the rollback script as follows:
cd $ORACLE_HOME/rdbms/admin
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> STARTUP
SQL> @catbundle_PSU_<database SID>_ROLLBACK.sql
SQL> QUIT
In a RAC environment, the name of the rollback script will have the format catbundle_PSU_<database SID PREFIX>_ROLLBACK.sql.
Check the log file for any errors. The log file is
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".
|
Note: A known issue exists if 11.2.0.3.1 is deinstalled after deinstalling 11.2.0.3.2. See Section 5, "Known Issues". |
Shut down the instance on the all nodes.
Run the OPatch utility specifying the rollback
argument as follows.
optch rollback -id 19282015 opatch rollback -id 19121548
If there are errors, refer to Section 5, "Known Issues".
Start the instance on the node as follows:
srvctl start instance –d <db-unique-name> -n <nodename>
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 1911751.1 Oracle Database Patch Set Update 11.2.0.3.12 Known Issues and Document 1933271.1 Oracle JavaVM Component 11.2.0.3.1 Database PSU Known Issues.
Other known issues are as follows.
The following ignorable errors may be encountered while
running the 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
If 11.2.0.3.1 is deinstalled after deinstalling
11.2.0.3.2, the deinstallation process inserts a row in
the registry$history with the wrong
version.
For example you might see the following:
20-MAR-12 11.37.18.860659 AM 2 ROLLBACK 11.2.0.3 PSU 11.2.0.3.2 20-MAR-12 11.42.27.015400 AM 2 ROLLBACK 11.2.0.3 PSU 11.2.0.3.2
The last row showing ROLLBACK 11.2.0.3 PSU
11.2.0.3.2 should be referencing 11.2.0.3.1.
As this is only a historical entry into registry$hisory,
this has no impact and can be ignored.
This will be addressed in a future PSU release.
Warnings may be returned during the re-link phase of 19121548. These warnings may be ignored.
warning: overriding commands for target `nmosudo' warning: ignoring old commands for target `nmosudo'
See the following document for additional information.
Document 1562458.1 Relinking the DB Control 11.2.0.3 Agent Displays a Warning Message "overriding commands for target 'nmosudo'"
On HP-UX systems, the following ignorable warnings may
be encountered during the relinking of the oracle
binary:
WARNING:OUI-67215: OPatch found the word "failed" in the stderr of the make command.Please look at this stderr. You can re-run this make command. cc: warning 487: Possibly incorrect message catalog. total_lntt_bytes is 0, assuming size of .debug_lntt Failed to mmap lntt temp file.
On AIX systems, the following ignorable warnings may be
encountered during the relinking of the oracle
binary:
WARNING:OUI-67215: OPatch found the word "failed" in the stderr of the make command.Please look at this stderr. You can re-run this make command. ld: 0711-224 WARNING: Duplicate symbol: <symbol> ld: 0711-345 WARNING: Duplicate symbol: <symbol> ld: 0711-773 WARNING: Duplicate symbol: <symbol> ld: 0711-783 WARNING: Duplicate symbol: <symbol> ld: 0711-301 WARNING: Duplicate symbol: <symbol> ld: 0711-415 WARNING: Duplicate symbol: <symbol> ld: 0711-319 WARNING: Duplicate symbol: <symbol>
If you are downgrading an Oracle database to Oracle Database 10g release 2 (10.2) or earlier, an "ORA-31134: Cannot delete a configuration that is referenced by other resources" exception will be raised if the existing network access control lists are dropped, but the transaction is not committed before the downgrade. You must commit the transaction before performing the downgrade.
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 19121548.8 Database 11.2.0.3.12 Patch Set Update (PSU)
Document 1449750.1 11.2.0.3 Patch Set Updates - List of Fixes in each PSU
Document 1561792.2 Patching Assistant: Oracle Database/Client - Select PSU/SPU (aka CPU)
Document 1911751.1 Oracle Database Patch Set Update 11.2.0.3.12 Known Issues
Document 1933271.1 Oracle JavaVM Component 11.2.0.3.1 Database PSU Known Issues
This patch includes the following bug fixes.
CPU molecules in PSU 11.2.0.3.12:
PSU 11.2.0.3.12 contains all molecules previously released in PSU 11.2.0.3.11 and the following new PSU 11.2.0.3.12 molecules:
| 19433745 - DB-11.2.0.3-MOLECULE-061-CPUOCT2014 | |
| 19433746 - DB-11.2.0.3-MOLECULE-062-CPUOCT2014 | |
| 19433747 - DB-11.2.0.3-MOLECULE-063-CPUOCT2014 | |
| 19537916 - DB-11.2.0.3-MOLECULE-064-CPUOCT2014 | |
| 19710542 - DB-11.2.0.3-MOLECULE-065-CPUOCT2014 |
See My Oracle Support Document 1449750.1 that documents all the non-security bugs fixed in each 11.2.0.3 Patch Set Update (PSU).
PSU 11.2.0.3.12 contains the following new fixes:
Automatic Storage Management
12387467 - INSTANCE CRASH BY ORA-600 [KFFMXPGET]
Buffer Cache Management
19259446 - ORA-600 [KCBO_SWITCH_CQ_1] MAY BE RAISED DURING FORCE UNDO CR GENERATION
Enterprise Manager
18673304 - Fix for bug 18673304 18673325 - Fix for bug 18673325 18673342 - Fix for bug 18673342 19211724 - Fix for bug 19211724
Generic
5144934 - WRONG OEREOF VALUE RETURNED WHEN ERROR OCCURS IN A BATCH 9163477 - ERROR ORA-39726 WHILE DROPPING COLUMN ON COMPRESSED PARTITIONED TABLE 9812682 - INTERNAL ERROR WHEN EXECUTING DML AGAINST TABLE JUST ALTERED TO ADD NEW COLUMN 11732473 - FLASHBACK QUERY FAILS WITH ORA-8181 12320556 - HIGH VERSION COUNTS OCCUR DUE TO AUTH_CHECK_MISMATCH, INSUFF_PRIVS_REM=Y 12411746 - INCONSISTENT BEHAVIOR OF SESSION TRYING TO PARSE EXECUTING PL/SQL BLOCK 12591399 - PARTITION PRUNING FOR JOINS B/W LOCAL PARTITIONED TABLES AND REMOTE TABLES FAILS 12596444 - CURSOR NOT SHARED WHEN CURSOR_SHARING=FORCE AND SQL WITH CASE EXPRESSION 14799269 - INFO IN V$SQL/V$SQLAREA ARE INCORRECT ONCE _CURSOR_OBSOLETE_THRESHOLD IS REACHED 16505333 - CREATE TABLE ERRORED OUT WITH ORA-38802: EDITION DOES NOT EXIST 16710753 - SGA LEAK (ORA-4031) WHILE DROPPING EDITION ORA$BASE 17050888 - PERFORMING DDL ON A TABLE OR VIEW LEAVES BEHIND TRIGGERS THAT WERE DEFINED ON IT 19458377 - CHECKS TO ENSURE COMPATIBILITY OF BUNDLES WITH JOX CHANGES 19554106 - CONFLICT RESOLVING FIX FOR BUNDLES FOR JOX CHANGES
High Availability
10182005 - COMPRESSED BACKUPS WITH VERY SMALL AMOUNT OF DATA CAN FAIL TO RESTORE 10256843 - HANG MANAGER MAY TRIGGER UNNECESSARY SYSTEMSTATE DUMPS ON ASM INSTANCE 12588237 - POSSIBLE RMAN-3002 ORA-1 AFTER DG SWITCHOVER 14182835 - INCORRECT LOCK REQUEST CAN LEAD TO ORA-600 [KJBRCHKPKEYWAIT:TIMEOUT] 19517437 - ORA-600 [KJBMMCHKINTEG:FROM], [34], [34], [2]
JavaVM
19638161 - OJVM111071:POSTDEINSTALL.SQL FAILED WITH ORA-29537 19289642 - Fix for bug 19289642
Oracle Multimedia
18262334 - PROCESSCOPY TO JPEG IMAGE FAILED FOR INDEX COLOR IMAGE
Oracle Security
16524926 - APEX: ORA-1031 WITH ORACLE MULTIMEDIA AND REALM PROTECTED DB SCHEMA
Oracle Space Management
13871316 - SPACE BACKGROUND SLAVE WNNN PROCESSES ARE PERIODICALLY CPU BOUND (90 TO 100%) 15826962 - INCREASED IN 'RELIABLE MESSAGE' WAITS ASSOCIATED TO KSR RBR MESSAGING
Oracle Transaction Management
12595606 - ORA-7445 [K2SIBG()+1237] PROMOTING A TRANSACTION FROM LOCAL TO GLOBAL
Oracle Virtual Operating System Services
13647945 - DNFS BATCH SIZE NEEDS TO BE MANAGED TO AVOID OVERWHELMING THE SERVER
PL/SQL
18641419 - Fix for bug 18641419
Patch Automation
19727057 - HANDLE JVMPSU.SQL IN CATBUNDLE
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.
Combo of OJVM Component 11.2.0.3.1 DB PSU + DB PSU 11.2.0.3.12 (Oct2014) for UNIX
Copyright © 2006, 2014, 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.