Thursday, May 23, 2013

Oracle: Opatch Sample

Patch 16056266 - 11.2.0.3.6 Patch Set Update

Released: April 16, 2013
This document is accurate at the time of release. For any changes and additional information regarding PSU 11.2.0.3.6, see these related documents that are available at My Oracle Support (http://support.oracle.com/):
  • Document 1525152.1 Patch Set Update and Critical Patch Update April 2013 Availability Document
  • Document 854428.1 Patch Set Updates for Oracle Products
  • Document 1523829.1 Oracle Database Patch Set Update 11.2.0.3.6 Known Issues
This document includes the following sections:

1 Patch Information

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.6 includes the fixes listed in Section 7, "Bugs Fixed by This Patch".
To install the PSU 11.2.0.3.6 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 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.6
Client-Only Installations
 PSU 11.2.0.3.4 to address CVE-2012-3151
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.)

2 Prerequisites

This section includes the following section:

2.1 OPatch Utility

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 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.

3 Installation

These instructions are for all Oracle Database installations.

3.1 Patch Pre-Installation Instructions

Before you install PSU 11.2.0.3.6, perform the following actions to check the environment and to detect and resolve any one-off patch conflicts.

3.1.1 Environments with Grid Infrastructure

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.6 Patch 16083653 should be applied to the Grid Infrastructure home and Database home using the readme instructions provided with the patch.

3.1.2 Environment Checks

  1. 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

3.1.3 One-off Patch Conflict Detection and Resolution

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:
  1. Determine whether any currently installed one-off patches conflict with the PSU patch as follows:
    unzip p16056266_11203_<platform>.zip
cd 16056266
opatch prereq CheckConflictAgainstOHWithDetail -ph ./
  2. The report will indicate the patches that conflict with PSU 16056266 and the patches for which PSU 16056266 is a superset.
    Note that Oracle proactively provides PSU 11.2.0.3.6 one-off patches for common conflicts.
  3. 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.
  4. When all the one-off patches that you have requested are available at My Oracle Support, proceed with Section 3.2, "Patch Installation Instructions".

3.2 Patch Installation Instructions

Follow these steps:
  1. 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.
  2. 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.
  3. 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.
  4. Set your current directory to the directory where the patch is located and then run the OPatch utility by entering the following commands:
    unzip p16056266_11203_<platform>.zip
cd 16056266
opatch apply
  5. If there are errors, refer to Section 5, "Known Issues".

3.3 Patch Post-Installation Instructions

After installing the patch, perform the following actions:
  1. Apply conflict resolution patches as explained in Section 3.3.1.
  2. Load modified SQL files into the database, as explained in Section 3.3.2.
  3. Upgrade Oracle Recovery Manager catalog, as explained in Section 3.3.3.

3.3.1 Applying Conflict Resolution Patches

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".

3.3.2 Loading Modified SQL Files into the Database

The following steps load modified SQL files into the database. For a RAC environment, perform these steps on only one node.
  1. 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> STARTUP
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.
  2. 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".

3.3.3 Upgrade Oracle Recovery Manager Catalog

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;

3.4 Patch Post-Installation Instructions for Databases Created or Upgraded after Installation of PSU 11.2.0.3.6 in the Oracle Home

There are no actions required for databases that have been upgraded or created after installation of PSU 11.2.0.3.6.

4 Deinstallation

These instructions apply if you need to deinstall the patch.

4.1 Patch Deinstallation Instructions for a Non-RAC Environment

Follow these steps:
  1. 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.
  2. Shut down all instances and listeners associated with the Oracle home that you are updating. For more information, see Oracle Database Administrator's Guide.
  3. Run the OPatch utility specifying the rollback argument as follows.
    opatch rollback -id 16056266
  4. If there are errors, refer to Section 5, "Known Issues".

4.2 Patch Post-Deinstallation Instructions for a Non-RAC Environment

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".
  1. Start all database instances running from the Oracle home. (For more information, see Oracle Database Administrator's Guide.)
  2. 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.
  3. 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".

4.3 Patch Deinstallation Instructions for a RAC Environment

Follow these steps for each node in the cluster, one node at a time:

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".
  1. Shut down the instance on the node.
  2. Run the OPatch utility specifying the rollback argument as follows.
    opatch rollback -id 16056266
    If there are errors, refer to Section 5, "Known Issues".
  3. Start the instance on the node as follows:
    srvctl start instance

4.4 Patch Post-Deinstallation Instructions for a RAC Environment

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.

5 Known Issues

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 1523829.1 Oracle Database Patch Set Update 11.2.0.3.6 Known Issues.
Other known issues are as follows.
Issue 1   
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
Issue 2   
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.

6 References

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 468959.1 Enterprise Manager Grid Control Known Issues
Document 16056266.8 Database 11.2.0.3.6 Patch Set Update (PSU)
Document 1449750.1 11.2.0.3 Patch Set Updates - List of Fixes in each PSU

7 Bugs Fixed by This Patch

This patch includes the following bug fixes.

7.1 CPU Molecules

CPU molecules in PSU 11.2.0.3.6:
PSU 11.2.0.3.6 contains all molecules previously released in PSU 11.2.0.3.5 and the following new PSU 11.2.0.3.6 molecules:

 16314466 - DB-11.2.0.3-MOLECULE-033-CPUAPR2013

16314467 - DB-11.2.0.3-MOLECULE-034-CPUAPR2013

16314468 - DB-11.2.0.3-MOLECULE-035-CPUAPR2013

16314469 - DB-11.2.0.3-MOLECULE-036-CPUAPR2013

16314470 - DB-11.2.0.3-MOLECULE-037-CPUAPR2013

7.2 Bug Fixes

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.6 contains the following new fixes:
Automatic Storage Management

 16231699 - ADDING A NEW DISK ON ODA APPLIANCE HITS ORA-00600 [KFGPSET3] ASSERT

16299830 - CREATE DISKGROUP RECO/REDO ONLY DISCOVER 2 FAILGROUPS

13098318 - CTRL-C OR A SESSION KILL DURING DML INVOLVING TEMP BLOCKS LEADS TO ORA-600[6856]
Buffer Cache Management

 13098318 - CTRL-C OR A SESSION KILL DURING DML INVOLVING TEMP BLOCKS LEADS TO ORA-600[6856]
Enterprise Manager Database Control

 14273397 - Fix for bug 14273397

14459552 - Fix for bug 14459552
Generic

 8547978 - DROP USER GIVES ORA-00600[KQD-OBJERROR$] AFTER ONLINE REDEFINITION OF TABLE

10242202 - ORA-22992 WHEN CREATING MATERIALIZED VIEW WITH REMOTE LOB COLUMN

13496884 - MERGE STMT CONTAINING BIND VARIABLES SOMETIMES FAILS DUE TO ORA-600 [QCSFBDNP:1]

13582702 - ORA-600 [KKMMCTBF:BAD INTCOLN] MAY BE SEEN WHILE EXECUTING DELETE

13584130 - ORA-7445 COMPILING LIBRARY UNIT WITH _LOAD_WITHOUT_COMPILE IN NON-BASE EDITION

13616375 - SQL TUNING FOR SELECT QUERY WITH FUNC-INDEX MAY FAIL DUE TO ORA-600 QKAFFSINDEX5

13786142 - DROP TRIGGER IN EDITIONING ENVIRONMENT COULD FAIL WITH ORA-4045/ORA-4098

13810393 - HANGING DUE TO 'LIBRARY CACHE: MUTEX X' DURING SHARED CURSOR STRESS TEST

13812031 - POSSIBLE WRONG RESULTS FROM QUERIES ON PARTITIONED TABLES

13860201 - INTERMITTENT COREDUMP IN KKSPBD0() DUE TO OBSOLETE CURSOR REFERENCED FROM PLSQL

13911821 - INSTANCE TERMINATION DUE A CRASH HIT BY PMON IN SHARED CURSORS CODE

14110275 - PARSE OF QUERY WITH TABLE THAT HAD UNDERGONE ADD COLUMN MAY RAISE INTERNAL ERROR

14226599 - 'LATCH: ROW CACHE OBJECTS' CONTENTION FOR DC_ROLLBACK_SEGS : ADD HASH BUCKETS

14644185 - DISABLE DEADLOCK DETECTION FOR CURSOR BUILD LOCKS

16175381 - PROCESS HUNG SPINNING IN KKSCSSEARCHCHILDLIST() -> KKSHGETNEXTCHILD()

16344871 - MISMATCH IN CURSOR SHAREABILITY (KKS LAYER) WITH VPD/RLS POLICY

14841812 - Fix for bug 14841812
High Availability

 9706792 - ORA-600 [KCRPDV_NOENT] IN CRASH RECOVERY WITH PARALLELISM

11715084 - ACTIVE DUPLICATE SHOULD WORK WHEN CONNECTED TO STANDBY AS SOURCE DB

12983611 - RARELY ASYNC PROCESS CAN READ THE LOG ENTRY WHILE LGWR IS MODIFYING IT

13632809 - RMAN BZ2 COMPRESSION BACKUP HANGS

13680405 - PGA CONSUMPTION KEEP GROWING BY DIA0

14088346 - LMS DIED BECAUSE OF ORA-600 [KJBRWRDONE:SC3]
Oracle Security

 13596521 - Fix for bug 13596521
Oracle Space Management

 13910420 - ORA-8103 DURING UPDATE OF BASICFILE CLOB IN ASSM SEGMENT USING SPACE SEARCH CACH

13913630 - COMPRESSION OLTP: INSERT ... SELECT DOESN'T COMPRESS SOME ROWS

13958038 - EXCESS SPACE USAGE DURING UPDATE

14176879 - EXTENSIVE GROWTH OF SECUREFILES SEGMENTS UNDERGOING UPDATES

14207163 - FAILED TO CREATE EHCC TBS ON ZFS POOL STORAGE

14472647 - WRONG RESULTS ON IOT SECONDARY INDEX

14589750 - TRUNCATE TABLE HANG IN RAC AFTER APPLICATION OF PATCH OF 14144283
Oracle Spatial

 13561951 - Fix for bug 13561951
Oracle Virtual Operating System Services

 13914613 - DATABASE CRASHED DUE TO ORA-240 AND ORA-15064
SQL*Net

 14841558 - Fix for bug 14841558
Workspace Manager

 16368108 - RUNNING OWMV1120.PLB IN PSU 112036 GIVING ORA-00955

14220725 - Fix for bug 14220725

8 Documentation Accessibility

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 16056266 - 11.2.0.3.6 Patch Set Update Release 11.2.0.3.6 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.
Posted by at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)