Patch 8576156 - 10.2.0.4.1 Patch Set Update
Released: July 14, 2009
This document is accurate at the time of release. For any changes and additional information regarding PSU 10.2.0.4.1, see these related documents that are available at My Oracle Support (http://www.myoraclesupport.com/):
Note 854428.1 Introduction to Database Patch Set Updates
Note 854473.1 Oracle Database Patch Set Update 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 10.2.0.4.1 includes the following previously released bundle patches:
Generic Recommended Bundle #4 (Patch 8362683)
RAC Recommended Bundle #3 (Patch 8344348)
Data Guard Broker Recommended Bundle #1 (Patch 7936793)
Data Guard Physical/Recovery Recommended Bundle #1 (Patch 7936993)
Data Guard Logical Recommended Bundle #1 (Patch 7937113)
To install the PSU 10.2.0.4.1 patch, the Oracle home must have the 10.2.0.4.0 Database patch set installed. Subsequent PSU patches can be installed on Oracle Database 10.2.0.4.0 or any PSU with a lower 5th numeral version than the one being installed. For example, PSU 10.2.0.4.3 can be installed on 10.2.0.4.0, 10.2.0.4.1, and 10.2.0.4.2.
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 10.2.0.4.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 Database Concepts.) |
|
ASM (Automatic Storage Management) homes |
PSU 10.2.0.4.1 |
|
CRS (Cluster Ready Services) homes |
None |
This section includes the following sections:
The PSU is made available on the following platforms:
HP-UX Itanium
HP-UX PA-RISC (64-bit)
IBM AIX on POWER Systems (64-bit)
Linux x86
Linux x86-64
Sun Solaris SPARC (64-bit)
You can request the PSU for other platforms. Refer to My Oracle Support patch 8576156 for other available platforms and to the "On Request Patch Set Updates" section of My Oracle Support Note 854428.1 Introduction to Database Patch Set Updates.
For Windows platforms, the 10.2.0.4 bundle announced with CPUJul2009 includes the content of PSU 10.2.0.4.1.
Components patched by this Patch Set Update:
Advanced Networking Option
Enterprise Manager for RDBMS
Oracle Data Mining
Oracle Database - Enterprise Edition
Oracle Database Vault
Oracle Net Services
You must use the OPatch 10.2 version 10.2.0.4.7 or later. Oracle recommends that you use the latest released OPatch 10.2, which is available for download from My Oracle Support patch 6880880 by selecting the 10.2.0.0.0 release.
For information about OPatch documentation, including any known issues, see My Oracle Support Note 293369.1 OPatch documentation list.
These instructions are for both non-RAC environments and RAC environments.
Before you install PSU 10.2.0.4.1, perform the following actions to check the environment and to detect and resolve any one-off patch conflicts.
Ensure that your Oracle Database installation is the same base release for which you are applying this patch. In other words, only apply the PSU 10.2.0.4.1 patch to Oracle Database Release 10.2.0.4.0.
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
Determine whether any currently installed one-off patches conflict with the PSU patch as follows:
unzip p8576156_10204_<platform>.zip opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir ./8576156
The report will indicate the patches that conflict with PSU 8576156 and the patches for which PSU 8576156 is a superset. Refer to "Patch Set Updates Patch Conflict Resolution" in My Oracle Support Note 854428.1 Introduction to Database Patch Set Updates.
Note that Oracle proactively provides 10.2.0.4.1 one-off patches for common conflicts.
When all the 10.2.0.4.1 one-off patches that you have requested are available at My Oracle Support, proceed with Section 2.3.2, "Patch Installation Instructions".
Follow these steps:
Review Section 3, "Known Issues" before proceeding with this installation.
If you are patching an ASM instance, shut down all Oracle Database instances that use this ASM instance. (To see which Oracle Database instances are connected to this ASM instance, query the V$ASM_CLIENT view.)
Do one of the following, depending on whether this is a RAC environment:
If this is a RAC environment, choose one of the patch installation methods provided by OPatch (rolling, all node, or minimum downtime), and shutdown instances and listeners as appropriate for the installation method selected.
This PSU patch is rolling RAC installable. Refer to My Oracle Support Note 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 p8576156_10204_<platform>.zip
cd 8576156
opatch apply
If any currently installed one-off patches conflict with the PSU patch, apply the patch conflict resolution one-off patches that were determined to be needed when you performed the steps in Section 2.3.1.2, "One-off Patch Conflict Detection and Resolution".
If there are errors, refer to Section 3, "Known Issues".
If you use the Job Scheduling system, run psu_root.sh as root to complete the installation of molecule 7155248. To run psu_root.sh, go to the directory where you downloaded the patch (if you are not already in that directory) and enter the following command:
sh psu_root.sh
If you are unable to run psu_root.sh during the PSU patch installation because of the additional access rights required, it can be scheduled to run at a later time, and the database does not need to be shut down.
If you do not run psu_root.sh, which changes the permissions on the binary extjob, executable jobs can fail with the following error:
ORA-27369: job of type EXECUTABLE failed with exit code: ...
Note that this step has no impact on the implementation of the PSU security fixes; it only affects the successful execution of the Job Scheduling system. That is, if you do not run psu_root.sh when you should, or if you run psu_root.sh but fail to run it as root, the PSU security fixes are still installed; however, the Job Scheduling system will fail.
Do not perform the operations in this section on ASM instances. However, if you shut down ASM as part of applying the PSU, you must start ASM instances before you can perform any of the actions in this section on any database instances.
After installing the patch, perform the following actions:
Load modified .sql files into the database, as explained in Section 2.3.3.1.
Recompile views in the database, if necessary, as explained in Section 2.3.3.2.
The following steps load modified .sql files into the database. For a RAC environment, perform these steps on only one node.
(Note that if there is a database in the Oracle home that you are patching, this will involve starting all database instances running from this Oracle home.)
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
For information about the catbundle.sql script, see My Oracle Support Note 605795.1 Introduction to Oracle Database catbundle.sql.
Check the following log files in $ORACLE_HOME/cfgtoollogs/catbundle 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 3, "Known Issues".
You may skip this section if you have recompiled views for this database during the installation of a previous PSU or CPU.
The time required to recompile the views and related objects depends on the total number of objects and on your system configuration. In one internal Oracle test with approximately 2000 views and 4000 objects, the total execution time for view_recompile_jan2008cpu.sql and utlrp.sql was about 30 minutes.
|
Note: Depending on these considerations and your downtime schedule, you can choose to schedule the recompilation of views independent of the rest of the PSU installation. If you do this, your system will continue to work; however, the PSU installation will not be complete until the view recompilation is completed. |
If you want to check whether view recompilation has already been performed for the database, execute the following statement.
SELECT * FROM registry$history where ID = '6452863';
If the view recompilation has been performed, this statement returns one or more rows. If the view recompilation has not been performed, this statement returns no rows.
The following steps recompile the views in the database. For a RAC environment, perform these steps on only one node.
Run the pre-check script (so named because it was initially released in CPUJan2008), which reports the maximum number of views and objects that may be recompiled:
cd $ORACLE_HOME/cpu/view_recompile sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> @recompile_precheck_jan2008cpu.sql SQL> QUIT
The purpose of this step is to help you determine whether view recompilation should be done at the same time as the PSU install, or scheduled later.
If the database is not in a RAC environment, perform this step and skip the next step. (If the database is in a RAC environment, go to the next step.)
Run the view recompilation script. Note that this script is run with the database in upgrade mode, which restricts connections as SYSDBA.
cd $ORACLE_HOME/cpu/view_recompile sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> SHUTDOWN IMMEDIATE SQL> STARTUP UPGRADE SQL> @view_recompile_jan2008cpu.sql SQL> SHUTDOWN; SQL> STARTUP; SQL> QUIT
If the database is in a RAC environment, run the view recompilation script as follows. Note that this script is run with the database in upgrade mode, which restricts connections as SYSDBA. Stop all instances except the one where the view recompilation is being executed.
cd $ORACLE_HOME/cpu/view_recompile
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> STARTUP NOMOUNT
SQL> ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=spfile;
SQL> SHUTDOWN
SQL> STARTUP UPGRADE
SQL> @view_recompile_jan2008cpu.sql
SQL> SHUTDOWN;
SQL> STARTUP NOMOUNT;
Set the CLUSTER_DATABASE initialization parameter to TRUE:
SQL> ALTER SYSTEM SET CLUSTER_DATABASE=TRUE SCOPE=spfile;
Restart the database:
SQL> QUIT
cd $CRS_HOME/bin
srvctl start database -d <database-name>
Check the log file for any errors. The log file is in the current directory and is named: vcomp_<sid>_<timestamp>.log
If any invalid objects were reported, run the utlrp.sql script as follows:
cd $ORACLE_HOME/rdbms/admin sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> @utlrp.sql
Then, manually recompile any invalid objects. For example:
SQL> alter package schemaname.packagename compile;
These instructions are for both non-RAC environments and RAC environments when a database is created or upgraded after the installation of PSU 10.2.0.4.1.
You must execute the steps in Section 2.3.3.1, "Loading Modified .sql Files into the Database"" and Section 2.3.3.2, "Recompiling Views in the Database" for any new database only if it was created by any of the following methods:
Using DBCA (Database Configuration Assistant) to select a sample database (General, Data Warehouse, Transaction Processing)
Using a script that was created by DBCA that creates a database from a sample database
Cloning a database that was created by either of the two preceding methods, and if Section 2.3.3.1, "Loading Modified .sql Files into the Database" and Section 2.3.3.2, "Recompiling Views in the Database" were not executed after PSU 10.2.0.4.1 was applied
Upgraded databases require that you perform the steps in Section 2.3.3.2, "Recompiling Views in the Database" if these steps have not previously been performed; otherwise, no post-installation steps need to be performed.
These instructions are for both Non-RAC environments and RAC environments.
Section 2.4.1, "Patch Deinstallation Instructions for a Non-RAC Environment"
Section 2.4.2, "Post Deinstallation Instructions for a Non-RAC Environment"
Section 2.4.3, "Patch Deinstallation Instructions for a RAC Environment"
Section 2.4.4, "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 2.3.3.1, "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.
opatch rollback -id 8576156
If there are errors, refer to Section 3, "Known Issues".
Follow these steps:
Start all database instances running from the Oracle home that you had patched. (For more information, see Oracle Database Administrator's Guide.)
For each database instance running out of the ORACLE_HOME that was patched, 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_HOME/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 3, "Known Issues".
If the number of invalid objects after the rollback is different from the number of invalid objects before the rollback, you probably want to compile the invalid objects, which you can do as follows:
cd $ORACLE_HOME/rdbms/admin sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> @utlrp.sql
Follow these steps for each node in the cluster, one node at a time:
Shut down the instance on the node. (Shut down all RDBMS instances before any ASM instances.)
Run the OPatch utility specifying the rollback argument as follows.
opatch rollback -id 8576156
If there are errors, refer to Section 3, "Known Issues".
Start the instance on the node. Depending on the type of home, enter the following commands or command.
For ASM homes:
srvctl start listener srvctl start asm srvctl start instance
For RDBMS (non-ASM) homes:
srvctl start instance
Follow the instructions listed in Section Section 2.4.2, "Post Deinstallation Instructions for a Non-RAC Environment" only on the node for which the steps in Section 2.3.3.1, "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 Note 293369.1 OPatch documentation list.
For issues documented after the release of this PSU, see My Oracle Support Note 854473.1 Oracle Database Patch Set Update 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-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.
The view recompilation pre-check script returns different results during subsequent runs (such as after the first time you ran it).
The results (the maximum number of views and objects that may be recompiled) may be more or less than reported in the previous running of the script. This is expected behavior, and is not a problem.
If the view recompilation script has already been run, a message is displayed indicating that the script has already been applied.
This is not a problem, because as the instructions note, you do not need to run the script if it has already been run.
The following documents are references for this patch.
Note 293369.1 OPatch documentation list
Note 360870.1 Impact of Java Security Vulnerabilities on Oracle Products
Note 468959.1 Enterprise Manager Grid Control Known Issues
This patch includes the following bug fixes.
CPU molecules in PSU 10.2.0.4.1:
PSU 10.2.0.4.1 contains all molecules previously released in CPUApr2009 and the following new CPUJul2009 molecules:
8568395 - DB-10.2.0.4-MOLECULE-021-CPUJUL2009
8568397 - DB-10.2.0.4-MOLECULE-022-CPUJUL2009
8568398 - DB-10.2.0.4-MOLECULE-023-CPUJUL2009
8568402 - DB-10.2.0.4-MOLECULE-024-CPUJUL2009
8568404 - DB-10.2.0.4-MOLECULE-025-CPUJUL2009
8568405 - DB-10.2.0.4-MOLECULE-026-CPUJUL2009
PSU 10.2.0.4.1 contains all fixes previously released in Generic Recommended Bundle #4 and the following new fixes:
4695511 - ORA-600 [KXFQUPP_BAD_CVL] WHEN CREATING BITMAP INDEX ON HUGE TABLE
5386204 - ORA-600 [KDDUMMY_BLKCHK] ERRORS WITH CODE 18038
6645719 - ORA 7445 [KGCCGMTF()+656] DURING RMAN WITH COMPRESS OPTION
6800507 - PROBLEM OF BUG;6749433 WAS NOT RESOLVED, EVEN APPLYING TEST FIX OF BUG;6474769
6858062 - KSWSAS SERVICE ENTRY IS NEVER FREED RESULTING IN MEMORY USE FOR DELETED SERVICES
7039896 - REFPART:LNX:PMON FAILED TO ACQUIRE LATCH, SEE PMON DUMP
7190270 - ORA-600 [KTSIRCINFO_NUM1] HAPPENED WHEN CTAS/DROP TABLE
7330909 - TB PERFORMANCE; KSWSISS() SHOULD ELIMINATE ONE QUERY FROM SERVICE$
7477934 - READ ONLY OR ACTIVE PHYSICAL STANDBY DATABASES ONLY START LAST SERVICE SPECIFIED
7661251 - SR11.2RCL - TRC - ORA-00445; BACKGROUND PROCESS 'W006' DID NOT START AFTER 600 S
7835247 - TRACING IN KSWSSCS() CAN CAUSE A SIGSEGV
8247855 - AFTER ERROR IN K2G?_DTP_START_SVC, HANG ON AS ENQUEUE OCCURS
8342923 - SIGSEGV SIGNALED WHEN ATTEMPTING TO START A NON-EXISTENT SERVICE
8344399 - MERGE OF SEVERAL SERVICES BUG FIXES FOR 10.2.0.4 (II) TO STABILIZE THE CODE BASE
8373286 - MERGE OF SERVICE LAYER FIXES FOR 10.2.0.4
Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.
Accessibility of Code Examples in Documentation
Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.
Accessibility of Links to External Web Sites in Documentation
This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.
TTY Access to Oracle Support Services
To reach AT&T Customer Assistants, dial 711 or 1.800.855.2880. An AT&T Customer Assistant will relay information between the customer and Oracle Support Services at 1.800.223.1711. Complete instructions for using the AT&T relay services are available at http://www.consumer.att.com/relay/tty/standard2.html. After the AT&T Customer Assistant contacts Oracle Support Services, an Oracle Support Services engineer will handle technical issues and provide customer support according to the Oracle service request process.
Patch 8576156 - 10.2.0.4.1 Patch Set Update Release 10.2.0.4.1 for UNIX
Copyright © 2006, 2009, 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 software or related documentation 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 USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software 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 which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
This software 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.