Patch 13343447 - 11.2.0.2.5 GI Patch Set Update (Includes Database PSU 11.2.0.2.5)
Released: January 17, 2012
This document is accurate at the time of release. For any changes and additional information regarding GI PSU 11.2.0.2.5, see these related documents that are available at My Oracle Support (http://support.oracle.com/):
Note 854428.1 Patch Set Updates for Oracle Products
Note 1272288.1 11.2.0.2.X Grid Infrastructure Bundle/PSU Known Issues
This document includes the following sections:
GI Patch Set Update (PSU) patches are cumulative. That is, the content of all previous PSUs (if any) is included in the latest GI PSU 11.2.0.2.5 patch.
Table 1 describes installation types and security content. For each installation type, it indicates the most recent PSUs, which includes 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 PSUs is listed, then apply that or any later PSUs patch to be current with security fixes.
Table 1 Installation Types and Security Content
| Installation Type | Latest PSU with Security Fixes |
|---|---|
|
Server homes |
11.2.0.2.5 GI PSU |
|
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.) |
This section includes the following sections:
You must satisfy the conditions in the following sections before applying the patch:
You must use the OPatch utility version 11.2.0.1.5 or later to apply this patch. Oracle recommends that you use the latest released OPatch for 11.2 releases, which is available for download from My Oracle Support patch 6880880 by selecting ARU link for the 11.2.0.0.0 release. It is recommended that you download the Opatch utility and the GI PSU 11.2.0.2.5 patch in a shared location to be able to access them from any node in the cluster for the patch application on each node.
|
Note: When patching the GI Home, a shared location on ACFS only needs to be unmounted on the node where the GI Home is being patched.The new opatch utility should be updated in all the Oracle RAC or Oracle RAC One Node database homes and the GI home that are being patched. To update Opatch, use the following instructions. |
Download the OPatch utility to a temporary directory.
For each Oracle RAC or Oracle RAC One Node database home and the GI home that are being patched, run the following commands as the home owner to extract the OPatch utility.
unzip <OPATCH-ZIP> -d <ORACLE_HOME> <ORACLE_HOME>/OPatch/opatch version
The version output of the previous command should be 11.2.0.1.5 or later.
For information about OPatch documentation, including any known issues, see My Oracle Support Note 293369.1 OPatch documentation list.
The OPatch utility will prompt for your OCM (Oracle Configuration Manager) response file when it is run. You should enter a complete path of OCM response file if you already have created this in your environment.
If you do not have the OCM response file (ocm.rsp) and you wish to use one during the patch application, then you should run the following command to create it.
As the Grid home owner execute:
<ORACLE_HOME>/OPatch/ocm/bin/emocmrsp
You can also invoke opatch auto with the -ocmrf <OCM response file path> option to run opatch auto in silent mode.
Before beginning patch application, check the consistency of inventory information for GI home and each database home to be patched. Run the following command as respective Oracle home owner to check the consistency.
<ORACLE_HOME>/OPatch/opatch lsinventory -detail -oh <ORACLE_HOME>
If this command succeeds, it lists the Oracle components that are installed in the home. The command will fail if the Oracle Inventory is not set up properly. If this happens, contact Oracle Support Services for assistance.
If you have not already done so, download OPatch 11.2.0.1.5 or later, as explained in Section 2.1.1, "OPatch Utility Information".
The patch application requires explicit user actions to run 'opatch auto' command on each node of Oracle clusterware. So, it is recommended that you download and unzip the GI PSU 11.2.0.2.5 patch in a shared location to be able to access it from any node in the cluster and then as the Grid home owner execute the unzip command. In the absence of a shared location, the patch should be copied to each node and unzipped on each node. It is not necessary to have the patch in same location on each node.
|
Note: Do not unzip the GI PSU 11.2.0.2.5 patch in the top level/tmp directory. |
The unzipped patch location should be empty and have read permission for ORA_INSTALL group in order to patch Oracle homes owned by different owners. The ORA_INSTALL group is the primary group of the user who owns the GI home or the group owner of the Oracle central inventory.
(In this readme, the downloaded patch location directory is referred as <UNZIPPED_PATCH_LOCATION>.)
cd <UNZIPPED_PATCH_LOCATION>
Unzip the GI PSU 11.2.0.2.5 patch as grid home owner in a shared location. As the Grid home owner execute:
unzip p13343447_112020_<platform>.zip
For example, if <UNZIPPED_PATCH_LOCATION> in your environment is /u01/oracle/patches, enter the following command:
cd /u01/oracle/patches
Unzip the GI PSU 11.2.0.2.5 patch as grid home owner in a shared location. As the Grid home owner execute:
unzip p13343447_112020_<platform>.zip
The PSU patch may include multiple patches and you may notice that there are multiple directories created with distinct bug numbers.
The Opatch utility has automated the patch application for the Oracle Grid Infrastructure (GI) home and the Oracle RAC or Oracle RAC One Node database homes. It operates by querying existing configurations and automating the steps required for patching each Oracle RAC or Oracle RAC One Node database home of same version and the GI home.
The utility must be executed by an operating system (OS) user with root privileges (usually the user root), and it must be executed on each node in the cluster if the GI home or Oracle RAC or Oracle RAC One Node database home is in Non-shared storage. The utility should not be run in parallel on the cluster nodes.
Depending on command line options specified, one invocation of Opatch can patch the GI home, one or more Oracle RAC or Oracle RAC One Node database homes, or both GI and Oracle RAC or Oracle RAC One Node database homes of the same Oracle release version. You can also roll back the patch with the same selectivity.
Add the directory containing the opatch to the $PATH environment variable. For example:
export PATH=$PATH:<GI_HOME>/OPatch
To patch GI home and all Oracle RAC or Oracle RAC One Node database homes of the same version:
opatch auto <UNZIPPED_PATCH_LOCATION>
To patch only the GI home:
opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME>
To patch one or more Oracle RAC or Oracle RAC One Node database homes:
opatch auto <UNZIPPED_PATCH_LOCATION> -oh <ORACLE_HOME>, <ORACLE_HOME2>
To roll back the patch from the GI home and each Oracle RAC or Oracle RAC One Node database home:
opatch auto <UNZIPPED_PATCH_LOCATION> -rollback
To roll back the patch from the GI home:
opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME> -rollback
To roll back the patch from the Oracle RAC or Oracle RAC One Node database home:
opatch auto <UNZIPPED_PATCH_LOCATION> -oh <ORACLE_HOME> -rollback
You should use the -ocmrf option in the opatch auto command to install patches in silent mode.
For more information about opatch auto, see My Oracle Support Note 293369.1 OPatch documentation list.
For detailed patch installation instructions, see Section 2.4, "Patch Installation".
For an introduction to the PSU one-off patch concepts, see "Patch Set Updates Patch Conflict Resolution" in My Oracle Support Note 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 Note 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:
In the unzipped directory as in Section 2.1.5.
opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir ./13343447
The report will indicate the patches that conflict with PSU 13343447 and the patches for which PSU 13343447 is a superset.
Note that Oracle proactively provides GI PSU 11.2.0.2.5 one-off patches for common conflicts.
Use My Oracle Support Note 1061295.1 Patch Set Updates - One-off 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 2.4, "Patch Installation".
This section will guide you through the steps required to apply this GI PSU 11.2.0.2.5 patch to Oracle RAC or Oracle RAC One Node database homes, the Grid home, or all relevant homes on the cluster.
|
Note: When patching the GI Home, a shared location on ACFS only needs to be unmounted on the node where the GI Home is being patched. |
The patch instructions will differ based on the configuration of the Grid infrastructure and the Oracle RAC or Oracle RAC One Node database homes.
The patch installations will also differ based on following aspects of your existing configuration:
GI home is shared or non-shared
The Oracle RAC or Oracle RAC One Node database home is shared or non-shared
The Oracle RAC or Oracle RAC One Node database home software is on ACFS or non-ACFS file systems.
Patch all the Oracle RAC or Oracle RAC One Node database and the GI homes together, or patch each home individually
You must choose the most appropriate case that is suitable based on the existing configurations and your patch intention.
|
Note: You must stop the EM agent processes running from the database home, prior to patching the Oracle RAC or Oracle RAC One Node database or GI Home. Execute the following command on the node to be patched.As the Oracle RAC or Oracle RAC One Node database home owner execute: <ORACLE_HOME>/bin/emctl stop dbconsole |
Case 1: Patching Oracle RAC or Oracle RAC One Node Database Homes and the GI Home Together
Case 2: Patching Oracle RAC or Oracle RAC One Node Database Homes
Case 6: Patching a Software Only Oracle RAC or Oracle RAC One Node Home Installation
Case 1: Patching Oracle RAC or Oracle RAC One Node Database Homes and the GI Home Together
Follow the instructions in this section if you would like to patch all the Oracle RAC or Oracle RAC One Node database homes of release version 11.2.0.2 and the 11.2.0.2 GI home.
Case 1.1: GI Home Is Shared
Follow these instructions in this section if the GI home is shared.
|
Note: Patching a shared GI home requires shutdown of Oracle GI stack on all the remote nodes in the cluster. This also means you need to stop all Oracle RAC or Oracle RAC One Node databases which depend on GI stack, ASM for data files, or an ACFS file system. |
Make sure to stop the Oracle databases running from the Oracle RAC or Oracle RAC One Node database homes.
As Oracle database home owner:
<ORACLE_HOME>/bin/srvctl stop database –d <db-unique-name>
ORACLE_HOME: Complete path of the Oracle database home.
Make sure the ACFS file systems are unmounted on all the nodes. Use instructions in Section 2.8 for unmounting ACFS file systems.
As root user, execute the following on all the remote nodes to stop the CRS stack:
<GI_HOME>/bin/crsctl stop crs
Patch the GI home.
On local node, as root user, execute the following command:
opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME>
On the remote node, as root user, run:
<GI_HOME>/crs/install/rootcrs.pl -patch
This step must be done after the first node is patched (Step 4), but before the stack is started on the remote nodes (Step 6).
opatch auto does not need to be run again because the GI home is already updated.
Start the Oracle GI stack on all the remote nodes.
As root user execute:
<GI_HOME>/bin/crsctl start crs
Mount ACFS file systems. See Section 2.9.
For each Oracle RAC or Oracle RAC One Node database home, execute the following command on each node if the database home software is not shared.
For each database home execute the following as root user:
opatch auto <UNZIPPED_PATCH_LOCATION> -oh <ORACLE_HOME>
ORACLE_HOME: Complete path of Oracle database home.
|
Note: The previous command should be executed only once on any one node if the database home is shared. |
Restart the Oracle databases that you have previously stopped in step 1.
As the database home owner execute:
<ORACLE_HOME>/bin/srvctl start database –d <db-unique-name>
Case 1.2: GI Home Is Not Shared
Case 1.2.1: ACFS File System Is Not Configured and Database Homes Are Not Shared
Follow these instructions in this section if the GI home is not shared and none of the Oracle database homes is shared.
As root user execute the following command on each node of the cluster:
opatch auto <UNZIPPED_PATCH_LOCATION>
Case 1.2.2A: Patching the GI Home and Database Home Together, the GI Home Is Not Shared, the Database Home Is Shared on ACFS
From the Oracle database home, make sure to stop the Oracle RAC or Oracle RAC One Node databases running on all nodes.
As the database home owner execute:
<ORACLE_HOME>/bin/srvctl stop database –d <db-unique-name>
On the 1st node, unmount the ACFS file systems. Use instructions in Section 2.8 for unmounting ACFS file systems.
On the 1st node, apply the patch to the GI Home using the opatch auto command.
As root user, execute the following command:
opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME>
On the 1st node, remount ACFS file systems. See Section 2.9 for instructions.
On the 1st node, apply the patch to the Database home using the opatch auto command. This operation will patch the Database home across the cluster given that it is a shared ACFS home.
As root user, execute the following command:
opatch auto <UNZIPPED_PATCH_LOCATION> -oh <ORACLE_HOME>
On the 1st node only, restart the Oracle database which you have previously stopped in Step 1.
As the database home owner execute:
<ORACLE_HOME>/bin/srvctl start database –d <db-unique-name> -n <nodename>
On the 2nd (next) node, unmount the ACFS file systems. Use instructions in Section 2.8 for unmounting ACFS file systems.
On the 2nd node, apply the patch to GI Home using the opatch auto command.
As root user, execute the following command:
opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME>
On the 2nd node, running the opatch auto command in Step 8 will restart the stack.
On the 2nd node, remount ACFS file systems. See Section 2.9 for instructions.
On the 2nd node only, restart the Oracle database which you have previously stopped in Step 1.
As the database home owner execute:
<ORACLE_HOME>/bin/srvctl start database –d <db-unique-name> -n <nodename>
Repeat Steps 7 through 10 for all remaining nodes of the cluster.
Case 1.2.2B: Patching the GI Home and the Database Home Together, the GI Home Is Not Shared, the Database Home Is Not Shared
For each node, perform the following steps:
On the local node, unmount the ACFS file systems. Use instructions in Section 2.8 for unmounting ACFS file systems.
On the local node, apply the patch to the GI home and to the Database home.
As root user, execute the following command:
opatch auto <UNZIPPED_PATCH_LOCATION>
This operation will patch both the CRS home and the Database home.
The opatch auto command will restart the stack on the local node and restarts the Database on the local node.
Repeat Steps 1 through 3 for all remaining nodes of the cluster.
Case 2: Patching Oracle RAC or Oracle RAC One Node Database Homes
You should use the following instructions if you prefer to patch Oracle RAC or Oracle RAC One Node databases alone with this GI PSU 11.2.0.2.5 patch.
Case 2.1: Non-Shared Oracle RAC or Oracle RAC One Node Database Homes
Execute the following command on each node of the cluster.
As root user execute:
opatch auto <UNZIPPED_PATCH_LOCATION> -oh <Comma separated Oracle home paths>
The opatch auto command stops the database instance on each node during the Oracle RAC or Oracle RAC One Node database patching. So there is no need to perform an explicit stop on database instances.
Case 2.2: Shared Oracle RAC or Oracle RAC One Node Database Homes
Make sure to stop the databases running from the Oracle RAC or Oracle RAC One Node database homes that you would like to patch. Execute the following command to stop each database.
As Oracle database home owner execute:
<ORACLE_HOME>/bin/srvctl stop database -d <db_unique_name>
As root user execute only on the local node.
opatch auto <UNZIPPED_PATCH_LOCATION> -oh <Comma separated Oracle home paths>
Restart the Oracle databases that were previously stopped in Step 1. Execute the following command for each database.
As Oracle database home owner execute:
<ORACLE_HOME>/bin/srvctl start database -d <db_unique_name>
Case 3: Patching GI Home Alone
You should use the following instructions if you prefer to patch Oracle GI (Grid Infrastructure) home alone with this GI PSU 11.2.0.2.5 patch.
Case 3.1: Shared GI Home
Follow these instructions in this section if the GI home is shared.
|
Note: Patching a shared GI home requires shutdown of Oracle GI stack on all the remote nodes in the cluster. This also means you need to stop all Oracle RAC or Oracle RAC One Node databases that depend on the GI stack, ASM for data file, or ACFS file system for database software. |
Make sure to stop the Oracle databases running from the Oracle RAC or Oracle RAC One Node database homes.
As Oracle database home owner:
<ORACLE_HOME>/bin/srvctl stop database –d <db-unique-name>
Make sure the ACFS file systems are unmounted on all the nodes. Use instructions in Section 2.8 for unmounting ACFS file systems.
As root user, execute the following on all the remote nodes to stop the CRS stack:
<GI_HOME>/bin/crsctl stop crs
Execute the following command on the local node
As root user execute:
opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME>
On the remote node, as root user, run:
<GI_HOME>/crs/install/rootcrs.pl -patch
This step must be done after the first node is patched (Step 4), but before the stack is started on the remote nodes (Step 6).
opatch auto does not need to be run again because the GI home is already updated.
Start the Oracle GI stack on all the remote nodes.
As root user execute:
<GI_HOME>/bin/crsctl start crs
Mount ACFS file systems. See Section 2.9.
Restart the Oracle databases that you have previously stopped in Step 1.
As the database home owner execute:
<ORACLE_HOME>/bin/srvctl start database –d <db-unique-name>
Case 3.2: Non-Shared GI Home
If the GI home is not shared then use the following instructions to patch the home.
Case 3.2.1: ACFS File System Is Not Configured
Follow these instructions in this section if the GI home is not shared and none of the Oracle database homes use ACFS file system for its software files.
Execute the following on each node of the cluster.
As root user execute:
opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME>
Case 3.2.2: ACFS File System Is Configured
Repeat Steps 1 through 5 for each node in the cluster:
From the Oracle database home, stop the Oracle RAC or Oracle RAC One Node database running on that node.
As the database home owner execute:
<ORACLE_HOME>/bin/srvctl stop instance –d <db-unique-name> -n <node_name>
Unmount all ACFS file systems on this node using instructions in Section 2.8.
Apply the patch to the GI home on that node using the opatch auto command.
Execute the following command on that node in the cluster.
As root user execute:
opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME>
Remount ACFS file systems on that node. See Section 2.9 for instructions.
Restart the Oracle database on that node that you have previously stopped in Step 1.
As the database home owner execute:
<ORACLE_HOME>/bin/srvctl start database –d <db-unique-name>
Case 4: Patching Oracle Restart Home
You must keep the Oracle Restart stack up and running when you are patching. Use the following instructions to patch the ACFS software in an Oracle Restart home, which is not the case in all installations. This is regardless of whether or not opatch auto is being used to patch the GI home.
For each node, perform the following steps to patch Oracle Restart home:
On the local node, unmount the ACFS file systems. Use instructions in Section 2.8 for unmounting ACFS file systems.
Stop the has stack:
crsctl stop has
Run <GridHome>/bin/acfsroot install.
As root user execute:
opatch auto <UNZIPPED_PATCH_LOCATION> -oh <ORACLE_HOME>
Case 5: Patching a Software Only GI Home Installation
Apply the CRS patch using.
As the GI home owner execute:
<GI_HOME>/OPatch/opatch napply -oh <GI_HOME> -local <UNZIPPED_PATCH_LOCATION>/13343447
As the GI home owner execute:
<GI_HOME>/OPatch/opatch napply -oh <GI_HOME> -local <UNZIPPED_PATCH_LOCATION>/13343424
Case 6: Patching a Software Only Oracle RAC or Oracle RAC One Node Home Installation
Run the pre script for DB component of the patch.
As the database home owner execute:
<UNZIPPED_PATCH_LOCATION>/13343447/custom/server/13343447/custom/scripts/prepatch.sh -dbhome <ORACLE_HOME>
Apply the DB patch.
As the database home owner execute:
<ORACLE_HOME>/OPatch/opatch napply -oh <ORACLE_HOME> -local <UNZIPPED_PATCH_LOCATION>/13343447/custom/server/13343447 <ORACLE_HOME>/OPatch/opatch napply -oh <ORACLE_HOME> -local <UNZIPPED_PATCH_LOCATION>/13343424
Run the post script for DB component of the patch.
As the database home owner execute:
<UNZIPPED_PATCH_LOCATION>/13343447/custom/server/13343447/custom/scripts/postpatch.sh -dbhome <ORACLE_HOME>
After installing the patch, perform the following actions:
Apply conflict resolution patches as explained in Section 2.5.1.
Load modified SQL files into the database, as explained in Section 2.5.2.
Upgrade Oracle Recovery Manager catalog, as explained in Section 2.5.3.
Apply the patch conflict resolution one-off patches that were determined to be needed when you performed the steps in Section 2.3, "One-off Patch Conflict Detection and Resolution".
The following steps load modified SQL files into the database. For an Oracle RAC or Oracle RAC One Node 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 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 Note 605795.1 Introduction to Oracle Database catbundle.sql.
Check the following log files in $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 3, "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;
These instructions are for a database that is created or upgraded after the installation of GI PSU 11.2.0.2.5.
You must execute the steps in Section 2.5.2, "Loading Modified SQL Files into 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
There are no actions required for databases that have been upgraded.
You can use the following steps to roll back GI and GI PSU 11.2.0.2.5 patches. Choose the instructions that apply to your needs.
|
Note: You must stop the EM agent processes running from the database home, prior to rolling back the patch from Oracle RAC or Oracle RAC One Node database or GI Home. Execute the following command on the node to be patched.As the Oracle RAC or Oracle RAC One Node database home owner execute: <ORACLE_HOME>/bin/emctl stop dbconsole |
Case 1: Rolling Back the Oracle RAC or Oracle RAC One Node Database Homes and GI Homes Together
Case 2: Rolling Back from the Oracle RAC or Oracle RAC One Node Database Homes
Case 5: Rolling Back the Patch from a Software Only GI Home Installation
Case 1: Rolling Back the Oracle RAC or Oracle RAC One Node Database Homes and GI Homes Together
Follow the instructions in this section if you would like to rollback the patch from all the Oracle RAC or Oracle RAC One Node database homes of release version 11.2.0.2 and the 11.2.0.2 GI home.
Case 1.1 GI Home Is Shared
Follow these instructions in this section if the GI home is shared.
|
Note: An operation on a shared GI home requires shutdown of the Oracle GI stack on all the remote nodes in the cluster. This also means you need to stop all Oracle RAC or Oracle RAC One Node databases that depend on the GI stack, ASM for data file, or ACFS file system. |
Make sure to stop the Oracle databases running from the Oracle RAC or Oracle RAC One Node database homes.
As Oracle database home owner:
<ORACLE_HOME>/bin/srvctl stop database -d <db-unique-name>
ORACLE_HOME: Complete path of the Oracle database home.
Make sure the ACFS file systems are unmounted on all the nodes. Use instructions in Section 2.8 for un-mounting ACFS file systems.
As root user, execute the following on all the remote nodes to stop the CRS stack:
<GI_HOME>/bin/crsctl stop crs
Rollback the patch from the GI home.
On local node, as root user, execute the following command:
opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME> -rollback
On the remote node, as root user, run:
<GI_HOME>/crs/install/rootcrs.pl -patch
This step must be done after the first node is patched (Step 4), but before the stack is started on the remote nodes (Step 6).
opatch auto does not need to be run again because the GI home is already updated.
Start the Oracle GI stack on all the remote nodes.
As root user execute:
<GI_HOME>/bin/crsctl start crs
Mount ACFS file systems. See Section 2.9.
For each Oracle RAC or Oracle RAC One Node database home, execute the following command on each node if the database home software is not shared.
For each database home, execute the following as root user:
opatch auto <UNZIPPED_PATCH_LOCATION> -oh <ORACLE_HOME> -rollback
ORACLE_HOME: Complete path of Oracle database home.
|
Note: The previous command should be executed only once on any one node if the database home is shared. |
Restart the Oracle databases that you have previously stopped in Step 1.
As the database home owner execute:
<ORACLE_HOME>/bin/srvctl start database -d <db-unique-name>
Case 1.2: GI Home Is Not Shared
Case 1.2.1: ACFS File System Is Not Configured and Database Homes Are Not Shared
Follow these instructions in this section if the GI home is not shared and none of the Oracle database homes is shared.
As root user, execute the following command on each node of the cluster.
opatch auto <UNZIPPED_PATCH_LOCATION> -rollback
Case 1.2.2A: Rolling Back the GI Home and Database Home Together, the GI Home Is Not Shared, the Database Home Is Shared on ACFS
From the Oracle database home, make sure to stop the Oracle RAC or Oracle RAC One Node databases running on all nodes.
As the database home owner execute:
<ORACLE_HOME>/bin/srvctl stop database –d <db-unique-name>
On the 1st node, unmount the ACFS file systems. Use instructions in Section 2.8 for unmounting ACFS file systems.
On the 1st node, roll back the patch to the GI Home using the opatch auto command.
As root user, execute the following command:
opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME> -rollback
On the 1st node, remount ACFS file systems. See Section 2.9 for instructions.
On the 1st node, roll back the patch to the Database home using the opatch auto command. This operation will patch the Database home across the cluster given that it is a shared ACFS home.
As root user, execute the following command:
opatch auto <UNZIPPED_PATCH_LOCATION> -oh <ORACLE_HOME> -rollback
On the 1st node only, restart the Oracle database which you have previously stopped in Step 1.
As the database home owner execute:
<ORACLE_HOME>/bin/srvctl start database –d <db-unique-name> -n <nodename>
On the 2nd (next) node, unmount the ACFS file systems. Use instructions in Section 2.8 for unmounting ACFS file systems.
On the 2nd node, roll back the patch to GI Home using the opatch auto command.
As root user, execute the following command:
opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME> -rollback
On the 2nd node, running the opatch auto command in Step 8 will restart the stack.
On the 2nd node, remount ACFS file systems. See Section 2.9 for instructions.
On the 2nd node only, restart the Oracle database which you have previously stopped in Step 1.
As the database home owner execute:
<ORACLE_HOME>/bin/srvctl start database –d <db-unique-name> -n <nodename>
Repeat Steps 7 through 10 for all remaining nodes of the cluster.
Case 1.2.2B: Rolling Back the GI Home and the Database Home Together, the GI Home Is Not Shared, the Database Home Is Not Shared
For each node, perform the following steps:
On the local node, unmount the ACFS file systems. Use instructions in Section 2.8 for unmounting ACFS file systems.
On the local node, roll back the patch to the GI home and to the Database home.
As root user, execute the following command:
opatch auto <UNZIPPED_PATCH_LOCATION> -rollback
This operation will patch both the CRS home and the Database home.
The opatch auto command will restart the stack on the local node and restarts the Database on the local node.
Repeat Steps 1 through 3 for all remaining nodes of the cluster.
Case 2: Rolling Back from the Oracle RAC or Oracle RAC One Node Database Homes
You should use the following instructions if you prefer to rollback the patch from Oracle RAC or Oracle RAC One Node databases homes alone.
Case 2.1: Non-Shared Oracle RAC or Oracle RAC One Node Database Homes
Execute the following command on each node of the cluster.
As root user execute:
opatch auto <UNZIPPED_PATCH_LOCATION> -oh <Comma separated Oracle home paths> -rollback
Case 2.2: Shared Oracle RAC or Oracle RAC One Node Database Homes
Make sure to stop the databases running from the Oracle RAC or Oracle RAC One Node database homes from which you would like to rollback the patch. Execute the following command to stop each database.
As Oracle database home owner execute:
<ORACLE_HOME>/bin/srvctl stop database -d <db_unique_name>
As root user execute only on the local node.
opatch auto <UNZIPPED_PATCH_LOCATION> -oh <Comma separated Oracle home paths> -rollback
Restart the Oracle databases that were previously stopped in Step 1. Execute the following command for each database.
As Oracle database home owner execute:
<ORACLE_HOME>/bin/srvctl start database -d <db_unique_name>
Case 3: Rolling Back from the GI Home Alone
You should use the following instructions if you prefer to rollback patch from the Oracle GI (Grid Infrastructure) home alone.
Case 3.1 Shared GI Home
Follow these instructions in this section if the GI home is shared.
|
Note: An operation in a shared GI home requires shutdown of Oracle GI stack on all the remote nodes in the cluster. This also means you need to stop all Oracle RAC or Oracle RAC One Node databases that depend on the GI stack, ASM for data file, or ACFS file system for database software. |
Make sure to stop the Oracle databases running from the Oracle RAC or Oracle RAC One Node database homes.
As Oracle database home owner:
<ORACLE_HOME>/bin/srvctl stop database -d <db-unique-name>
Make sure the ACFS file systems are unmounted on all the nodes. Use instructions in Section 2.8 for unmounting ACFS file systems.
As root user, execute the following on all the remote nodes to stop the CRS stack:
<GI_HOME>/bin/crsctl stop crs
Execute the following command on the local node.
As root user execute:
opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME> -rollback
On the remote node, as root user, run:
<GI_HOME>/crs/install/rootcrs.pl -patch
This step must be done after the first node is patched (Step 4), but before the stack is started on the remote nodes (Step 6).
opatch auto does not need to be run again because the GI home is already updated.
Start the Oracle GI stack on all the remote nodes.
As root user execute:
<GI_HOME>/bin/crsctl start crs
Mount ACFS file systems. See Section 2.9.
Restart the Oracle databases that you have previously stopped in Step 1.
As the database home owner execute:
<ORACLE_HOME>/bin/srvctl start database -d <db-unique-name>
Case 3.2: Non-Shared GI Home
If the GI home is not shared, then use the following instructions to rollback the patch from the GI home.
Case 3.2.1: ACFS File System Is Not Configured
Follow these instructions in this section if the GI home is not shared and none of the Oracle database homes is shared.
Execute the following on each node of the cluster.
As root user execute:
opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME> -rollback
Case 3.2.2: ACFS File System Is Configured
Repeat Steps 1 through 5 for each node in the cluster:
From the Oracle database home, stop the Oracle RAC or Oracle RAC One Node database running on that node.
As the database home owner execute:
<ORACLE_HOME>/bin/srvctl stop instance -d <db-unique-name> -n <node_name>
Make sure the ACFS file systems are unmounted on that node. Use instructions in Section 2.8 for unmounting ACFS file systems.
Roll back the patch to the GI home on that node using the opatch auto command.
Execute the following command on each node in the cluster.
As root user execute:
opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME> -rollback
Remount ACFS file systems on that node. See Section 2.9 for instructions.
Restart the Oracle database on that node that you have previously stopped in Step 1.
As the database home owner execute:
<ORACLE_HOME>/bin/srvctl start instance -d <db-unique-name> -n <node_name>
Case 4: Rolling Back the Patch from Oracle Restart Home
You must keep the Oracle Restart stack up and running when you are rolling back the patch from the Oracle Restart home. Use the following instructions to roll back the patch from the Oracle Restart home.
As root user execute:
opatch auto <UNZIPPED_PATCH_LOCATION> -oh <ORACLE_HOME> -rollback
Case 5: Rolling Back the Patch from a Software Only GI Home Installation
Roll back the CRS patch.
As the GI home owner execute:
<GI_HOME>/OPatch/opatch rollback -local -id 13343447 -oh <GI_HOME> <GI_HOME>/OPatch/opatch rollback -local -id 13343424 -oh <GI_HOME>
Case 6: Rolling Back the Patch from a Software Only Oracle RAC or Oracle RAC One Node Home Installation
Run the pre script for DB component of the patch.
As the database home owner execute:
<UNZIPPED_PATCH_LOCATION>/13343447/custom/server/13343447/custom/scripts/prepatch.sh -dbhome <ORACLE_HOME>
Roll back the DB patch from the database home.
As the database home owner execute:
<ORACLE_HOME>/OPatch/opatch rollback -local -id 13343447 -oh <ORACLE_HOME> <ORACLE_HOME>/OPatch/opatch rollback -local -id 13343424 -oh <ORACLE_HOME>
Run the post script for DB component of the patch.
As the database home owner execute:
<UNZIPPED_PATCH_LOCATION>/13343447/custom/server/13343447/custom/scripts/postpatch.sh -dbhome <ORACLE_HOME
ACFS file systems can be used by Oracle RAC or Oracle RAC One Node for hosting software files for the database. It can also be used as a general purpose file system for non-database files.The ACFS file system is managed and administered by the Oracle GRID Infrastructure. So ACFS file systems will be impacted when shutting down the GI stack for patching GI homes.
Shut down the processes using the software files on ACFS and then unmount the ACFS file system.
|
Note: Make sure to stop the non-Oracle processes that use ACFS file systems. |
If the ACFS file system is used by Oracle database software, then perform Steps 1 and 2.
Execute the following command to find the names of the CRS managed ACFS file system resource.
As root user execute:
crsctl stat res -w "TYPE = ora.acfs.type"
Execute the following command to stop the CRS managed ACFS file system resource with the resource name found from Step 1.
As root user execute:
crsctl stop res <acfs file system resource name> -n <nodename>
If the ACFS file system is not used for Oracle Database software and is registered in the ACFS registry, perform the following steps.
Execute the following command to find all ACFS file system mount points.
As the root user execute:
/sbin/acfsutil registry
Unmount ACFS file systems found in Step 1.
As the root user execute:
/bin/umount <mount-point>
|
Note: On Solaris operating system use:/sbin/umount.
On AIX operating system, use: |
Verify that the ACFS file systems are unmounted. Execute the following command to verify.
As the root user execute:
/sbin/acfsutil info fs
The previous command should return the following message if there is no ACFS file systems mounted.
"acfsutil info fs: ACFS-03036: no mounted ACFS file systems"
If the ACFS file system is used by Oracle database software, then perform Steps 1 and 2.
Execute the following command to find the names of the CRS managed ACFS file system resource.
As root user execute:
crsctl stat res -w "TYPE = ora.acfs.type"
Execute the following command to start and mount the CRS managed ACFS file system resource with the resource name found from Step 1.
As root user execute:
crsctl start res <acfs file system resource name> -n <nodename>
If the ACFS file system is not used for Oracle Database software and is registered in the ACFS registry, these file systems should get automatically mounted when the CRS stack comes up. Perform Steps 1 and 2 if it is not already mounted.
Execute the following command to find all ACFS file system mount points.
As the root user execute:
/sbin/acfsutil registry
Mount ACFS file systems found in Step 1.
As the root user execute:
/bin/mount <mount-point>
|
Note: On Solaris operating system use:/sbin/mount.
On AIX operating system, use: |
Follow these steps only on the node for which the steps in Section 2.5.2, "Loading Modified SQL Files into the Database" were executed during the patch application.:
Start all database instances running from the Oracle home. (For more information, see Oracle Database Administrator's Guide.)
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 PREFIX>_ROLLBACK.sql
SQL> QUIT
In an Oracle RAC or Oracle RAC One Node 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 3, "Known Issues".
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 PSUs, see My Oracle Support Note 1272288.1 11.2.0.2.X Grid Infrastructure Bundle/PSU Known Issues.
Other known issues are as follows.
Known Issues for Opatch Auto
Bug 10339274 - 'OPATCH AUTO' FAILED TO APPLY 11202 PATCH ON EXADATA RAC CLUSTER WITH 11201 RAC
Bug 10339251 - MIN OPATCH ISSUE FOR DB HOME SETUP IN EXADATA RAC CLUSTER USING 'OPATCH AUTO'
These two issues are observed in an environment where lower version database homes coexist with 11202 clusterware and database homes and opatch auto is used to apply the 11202 GIBundle.
Workaround:
Apply the 11202 GIBundle to the 11202 GI Home and Oracle RAC or Oracle RAC One Node database home as follows:
opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME> opatch auto <UNZIPPED_PATCH_LOCATION> -oh <11202 ORACLE_HOME>,<11202 ORACLE_HOME>
Bug 10226210 (11,11.2.0.2GIBTWO) 11202_GI_OPATCH_AUTO: OPATCH TAKES MORE STORAGE SPACE AFTER ROLLBACK SUCCEED
Workaround:
Execute the following command as Oracle home owner after a successful rollback to recover the storage used by the backup operation:
opatch util cleanup -silent
Bug 11799240 - 11202_GIBTWO:STEP 3 FAILED,CAN'T ACCESS THE NEXT OUI PAGE DURING SETTING UP GI
After applying GI PSU 11.2.0.2.5, the Grid Infrastructure Configuration Wizard fails with error INS-42017 when choosing the nodes of the cluster.
Workaround:
Apply the one off patch for the bug 10055663.
Bug 11856928 - 11202_GIBTWO_HPI:PATCH SUC CRS START FAIL FOR PERM DENY TO MKDIR $EXTERNAL_ORACL
This issue is seen only on the HPI platform when the opatch auto command is invoked from a directory that does not have write permission to the root user.
Workaround:
Execute the opatch auto from a directory that has write permission to the root user.
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
Bug 12619571 - 11202_GIBTHREE: PATCH FAILED IN MULTI-BYTES LANG ENV ISSUE SHOULD BE DOCUMENTED
This issue is seen when trying to run opatch auto to apply the GI PSU patch in the Japanese environment. The cause of the problem is that opatch auto currently only supports the English language environment.
Workaround:
Always keep the environment as the English language environment when running opatch auto to apply the GI PSU.
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
Steps for Applying the Patch
|
Note: You must stop the EM agent processes running from the database home, prior to patching the Oracle RAC or Oracle RAC One Node database or GI Home. Execute the following command on the node to be patched.As the Oracle RAC or Oracle RAC One Node database home owner execute: <ORACLE_HOME>/bin/emctl stop dbconsole |
Execute the following on each node of the cluster in non-shared CRS and DB home environment to apply the patch.
Stop the CRS managed resources running from DB homes.
If this is a GI Home environment, as the database home owner execute:
<ORACLE_HOME>/bin/srvctl stop home -o <ORACLE_HOME> -s <status file location> -n <node name>
If this is an Oracle Restart Home environment, as the database home owner execute:
<ORACLE_HOME>/bin/srvctl stop home -o <ORACLE_HOME> -s <status file location>
|
Note: You need to make sure that the Oracle ACFS file systems are unmounted (see Section 2.8) and all other Oracle processes are shutdown before you proceed. |
Run the pre root script.
If this is a GI Home, as the root user execute:
<GI_HOME>/crs/install/rootcrs.pl -unlock
If this is an Oracle Restart Home, as the root user execute:
<GI_HOME>/crs/install/roothas.pl -unlock
Apply the CRS patch using.
As the GI home owner execute:
<GI_HOME>/OPatch/opatch napply -oh <GI_HOME> -local <UNZIPPED_PATCH_LOCATION>/13343447
As the GI home owner execute:
<GI_HOME>/OPatch/opatch napply -oh <GI_HOME> -local <UNZIPPED_PATCH_LOCATION>/13343424
Run the pre script for DB component of the patch.
As the database home owner execute:
<UNZIPPED_PATCH_LOCATION>/13343447/custom/server/13343447/custom/scripts/prepatch.sh -dbhome <ORACLE_HOME>
Apply the DB patch.
As the database home owner execute:
<ORACLE_HOME>/OPatch/opatch napply -oh <ORACLE_HOME> -local <UNZIPPED_PATCH_LOCATION>/13343447/custom/server/13343447 <ORACLE_HOME>/OPatch/opatch napply -oh <ORACLE_HOME> -local <UNZIPPED_PATCH_LOCATION>/13343424
Run the post script for DB component of the patch.
As the database home owner execute:
<UNZIPPED_PATCH_LOCATION>/13343447/custom/server/13343447/custom/scripts/postpatch.sh -dbhome <ORACLE_HOME>
Run the post script.
As the root user execute:
<GI_HOME>/rdbms/install/rootadd_rdbms.sh
If this is a GI Home, as the root user execute:
<GI_HOME>/crs/install/rootcrs.pl -patch
If this is an Oracle Restart Home, as the root user execute:
<GI_HOME>/crs/install/roothas.pl -patch
Start the CRS managed resources that were earlier running from DB homes.
If this is a GI Home environment, as the database home owner execute:
<ORACLE_HOME>/bin/srvctl start home -o <ORACLE_HOME> -s <status file location> -n <node name>
If this is an Oracle Restart Home environment, as the database home owner execute:
<ORACLE_HOME>/bin/srvctl start home -o <ORACLE_HOME> -s <status file location>
Steps for Rolling Back the Patch
Execute the following on each node of the cluster in non-shared CRS and DB home environment to rollback the patch.
Stop the CRS managed resources running from DB homes.
If this is a GI Home environment, as the database home owner execute:
<ORACLE_HOME>/bin/srvctl stop home -o <ORACLE_HOME> -s <status file location> -n <node name>
If this is an Oracle Restart Home environment, as the database home owner execute:
<ORACLE_HOME>/bin/srvctl stop home -o <ORACLE_HOME> -s <status file location>
|
Note: You need to make sure that the Oracle ACFS file systems are unmounted (see Section 2.8) and all other Oracle processes are shut down before you proceed. |
Run the pre root script.
If this is a GI Home, as the root user execute:
<GI_HOME>/crs/install/rootcrs.pl -unlock
If this is an Oracle Restart Home, as the root user execute:
<GI_HOME>/crs/install/roothas.pl -unlock
Roll back the CRS patch.
As the GI home owner execute:
<GI_HOME>/OPatch/opatch rollback -local -id 13343447 -oh <GI_HOME> <GI_HOME>/OPatch/opatch rollback -local -id 13343424 -oh <GI_HOME>
Run the pre script for DB component of the patch.
As the database home owner execute:
<UNZIPPED_PATCH_LOCATION>/13343447/custom/server/13343447/custom/scripts/prepatch.sh -dbhome <ORACLE_HOME>
Roll back the DB patch from the database home.
As the database home owner execute:
<ORACLE_HOME>/OPatch/opatch rollback -local -id 13343447 -oh <ORACLE_HOME> <ORACLE_HOME>/OPatch/opatch rollback -local -id 13343424 -oh <ORACLE_HOME>
Run the post script for DB component of the patch.
As the database home owner execute:
<UNZIPPED_PATCH_LOCATION>/13343447/custom/server/13343447/custom/scripts/postpatch.sh -dbhome <ORACLE_HOME>
Run the post script.
As the root user execute:
<GI_HOME>/rdbms/install/rootadd_rdbms.sh
If this is a GI Home, as the root user execute:
<GI_HOME>/crs/install/rootcrs.pl -patch
If this is an Oracle Restart Home, as the root user execute:
<GI_HOME>/crs/install/roothas.pl -patch
Start the CRS managed resources that were earlier running from DB homes.
If this is a GI Home environment, as the database home owner execute:
<ORACLE_HOME>/bin/srvctl start home -o <ORACLE_HOME> -s <status file location> -n <node name>
If this is an Oracle Restart Home environment, as the database home owner execute:
<ORACLE_HOME>/bin/srvctl start home -o <ORACLE_HOME> -s <status file location>
This patch includes the following bug fixes:
CPU molecules in GI PSU 11.2.0.2.5:
GI PSU 11.2.0.2.5 contains the following new CPU 11.2.0.5 molecules:
13386082 - DB-11.2.0.2-MOLECULE-017-CPUJAN2012
13468884 - DB-11.2.0.2-MOLECULE-018-CPUJAN2012
GI PSU 11.2.0.2.5 contains all fixes released previous to GI PSU 11.2.0.2.5 (see Section 6.3, Section 6.4, and Section 6.5 for a list of these bug fixes) and the following new fixes:
Automatic Storage Management
9970255 - TB_ASM_NT64: CRASH WHEN DISMOUNTING ONE IN-USE AND ONE NON-EXISTING DISKGROUP
10021022 - NODES REBOOT WHEN MOUNTING ASM DG CONTAINING VOTE AND OCR
11061775 - 11203_ASM_X64:ORA-7445[KFDGLOBALOPEN()+740] IN DB INSTANCE RECOVERY
11841309 - OMITTING REBALANCE POWER CAN CAUSE KFGBTIMEOUT_2 IF POWER LIMIT IS 0
12397410 - SOL-SP64-11203-ACFS:PARALLEL RESIZE ACFS FAILED AND DB CRASH AND RESTART
12655433 - 11202_BP_ASM:X:ASM INST HANGING IN MOUTING ALL DGS AFTER THREE CELLS REBOOTED
12685431 - X2-2 ORA-600 [KFCRELEASE - INVALID BUFFER HANDLE], [KFDUS.C] RBAL TERMINATES ASM
12797765 - SOL_SP64: AFTER ALL DISKS FAILURE, DG CAN'T BE DISMOUNTED ON T2000-3
12945137 - VOTING FILE SIZE NEEDS TO BE SMALLER VALUE FOR 11.2.0.2.0 COMPATIBLE DISKGROUPS
12950644 - RBAL HIT ORA-07445:[KFDGLOBALOPEN()+738], ASM INST ABORT
Buffer Cache Management
10040035 - AROLTP-D: INSTANCE DIED WITH ORA-00600 [KCLPDC_21]
11800959 - AROLTP-D: TAKING SYSTEM STATE DUMP TAKES A LONG TIME SEEMS LOOPING IN KCL*
11866952 - DBWR PROCESSES USE HIGH CPU WITH TIMES() SYSTEM CALL IN STANDBY.
12569482 - LNX64-RAC:DB LMS PROC HIT ORA-00600[KJBLDRMRPST:!MASTER] AND INST CRASH
Generic
9285259 - MERGE IGNORES CHECK CONSTRAINT
9375300 - UNABLE TO SHARE CURSORS FOR REASON 'PQ_SLAVE_MISMATCH'
9436324 - ISSUES WITH INSERT-VALUES OCI_BATCH_ERRORS EXECUTION MODE
9578670 - ORA-4031 WHILE DROP PARTITIONS, SOLUTION FROM DOC ID: 419551.1 DIDN'T HELP
9727147 - APPS-R12:SQL-PROFILE :ORA-7445 [QKSVCPROCESSVIRTUALCOLUMN()+429] W/OFE=11.1.0.7
9847634 - HIGH VERSION COUNT DUE TO AUTH_CHECK_MISMATCH AND TRANSLATION_MISMATCH
10158493 - COMPLEX QUERY PROVIDES INCORRECT BLANK ROW
10165083 - PROCEDURE TRIES TO WRITE TO A WRONG SCHEMA (CHILD CURSORS MISMATCH) IN 10.2.0.5
10284838 - CACHE LINE CONTENTION WHILE WAITING FOR MUTEXES
10302581 - START_REDEF_TABLE CREATE INDEX IN SYSTEM TABLESPACE
10363186 - ORA-19563 WHILE USING DBMS_FILE_TRANSFER FROM SOLARIS TO LINUX (EXPDP DMP FILES)
10417216 - CORE DUMP WHEN USING A MIX OF NATIVE AND INTERPRETED PLSQL UNITS
10417716 - MUTEX X WAITS SINCE UPGRADE TO 11.2.0.2
10630870 - TRIGGER ASSIGNING A VALUE TO :NEW FAILS WITH ORA-1407 ON 11.1 AND 11.2
11076894 - ALTER INDEX [NO]PARALLEL REQUIRES UNNECCESSARY X-LOCK
11788856 - INSERT HANG 11.2.0.1 SPINNING ON QKSHTSTMTINF0
11858315 - ORA-600 [17147] ORA-600 [KGHALO4] WITH PATCH 10277915 APPLIED
12345717 - MERGE FAILS WITH ORA-600 [13013]
12400751 - UPDATE STATEMENTS DOES NOT WORK.
12531263 - ORA-4020 DEADLOCK DETECTED WHILE TRYING TO LOCK OBJECT $BUILD$.4D05F39B829BBE95
12543639 - QUERY RETURNS DIFFERENT RESULTS IN 10G AND 11G
12589039 - ORA-600 [17147] DATABASE CRASH
12830339 - FREQUENT INSTANCE CRASHES AFTER 11.2.0.2 UPGRADE
High Availability
9943960 - "TTX ID1: %X ID2: %X RET: %D WAITOPT: %D"MESSAGE IN TRACE FILE
10200390 - ORA-600[KJBCLOSE_REMASTER:!DRM]
10284570 - CRASH RECOVERY FAILS DUE TO ORA-15081, DISK GROUP IS MOUNTED BUT WAS RESYNC-ING
10314582 - GSIAP: RDBMS IPC REPLY WAITS WHEN PARSING SELECT FROM DUAL
10388660 - DUPLICATE DATABASE FAILS WHEN LOG_ARCHIVE_DEST IS SET TO AN ASM DISK GROUP
10635701 - BACKUP OF FRA CONSUMES 15GB OF PGA AND FAIL WITH ORA-4030
11689702 - ORA-600 [3020] DURING RECOVERY AFTER DATAFILE RESIZE (TO SMALLER SIZE)
11690639 - VERY MANY AND LONG LATCH: GES RESOURCE HASH LIST WAIT EVENT
11694127 - RMAN DUPLICATE NOT HONORING TIME FOR "UNTIL TIME"
11785390 - KJBM.C HAS MULTIPLE EXITS FROM SETJMP ERROR HANDLING BLOCKS
11815753 - ORA-7445 [KCRF_VAL_LOG_BSZ()+417] AFTER SETTING 4K REDO GROUP USING OVERRIDE
11890804 - LMHB TERMINATE INSTANCE WHEN LMON WAIT CHANGE FROM CF READ AFTER 60 SEC
12370722 - CATUPGRD.SQL HANGS WITH ARCH ERROR ORA-600 [KRR_HIGHEST_SCN_TIM_8]
12408350 - ORA-600 [KJBRASR:PKEY], [31023744], [0],
12423475 - BRR SHOULD NOT BE GENERATED FOR CACHE FUSION WITH S LOCK PING
12917230 - QUERY WITH TEMP TABLE TRANSFORMATION RUNS 5X SLOWER WAITING FOR REMASTERING
Oracle Portable ClusterWare
9686152 - TWO OF THREE RAC INSTANCES DID NOT RESTART AFTER REINSTATEMENT
9935308 - TB-GNS: GNSD SPINS CPU (~50%) AFTER FAILOVERED TO ANOTHER NODE
10057719 - LNX64-11202-RAC1:DB INSTANCE KEEPS RESTART AFTER DIRTY RESET OMOTION SOURCE NODE
10165314 - CHM/CRF/IPDOS REPOSITORY EXCEEDS 1GB AFTER ADD/REMOVE NODE OR FRESH INSTALL
10365625 - 11202_GI_BUND_CRF: OSYSMOND MEMORY LEAK AT THE SPEED OF 10MB/HOUR
11705438 - CRSCTL DELETE NODE RECEIVES CRS-4662 AND CRS-4000
11744343 - LNX64-11203-RACG: ONE DB INST GETS CLEANED DURING PARALLEL STACK START
11882456 - OL11-11203: ORA.CRF START FAILED DURING ROOT.SH
12593451 - VIP FAILOVER TAKES OVER 30 SECONDS DUE TO CMVIEWCL TIMEOUT
12718811 - 11202_GIBTHREE_HPI:EXECTASK COREDUMP PERIODICALLY ON NODE RUNNING ORA.CVU
12720728 - GIPCHALOWERPROCESSNODE: NO VALID INTERFACES FOUND TO NODE
12722095 - 11202_GIB3: "CANNOT PARSE HOSTS FROM OUTPUT" IN DIAGCOLLECTION.PL
12728585 - CRSCTL STOP CRS HANGS
12950415 - LNX64-11203-CRF:OSYSMOD DUMP CORE WHEN SYSTEM HAS GREATER THAN 255 MOUNT POINTS
13332363 - BUG 9795321 HAS REAPPEARED IN 11.2.0.3
13334158 - REBOOT OF ONE OF THE SWITCH EVICTS INSTANCES
13355549 - OPATCH APPLY FAILS FOR GIPSU 11.2.0.2.4
Oracle Secure Files
11723722 - ORA-3106 READNG SECUREFILES BY OCI SQLTYPE SQLT_LBI AND SQLT_CHR
Oracle Security
9842573 - MVIEW REFRESH GET ORA-3113 WITH AUDIT
Oracle Space Management
9707965 - UNNECESSARY DECOMPRESSION OF OLTP COMPRESSED ROWS
10427260 - ORA-00600 [KTCDSO-1], [], [], [] WHEN PURGE RECYCLE BIN
11842991 - DBFS TEST WITH CONCURRENT FILE CREATION HANG/SPIN WHEN ALLOCATING SPACE
12417369 - GSIAP-CORRUPT BLOCK FOUND FOR CZ.CZ_LOCALIZED_TEXTS
Oracle Transaction Management
10269503 - ALTER PACKAGE COMPILE IN NATIVE COMPILATION RAISES ORA-600
Oracle Universal Storage Management
12545774 - SOL-X64-SC-ACFS:LS HANG ON REMOTE NODE WHEN CREATE LOTS OF FILES ON LOCAL NODE
12932852 - AIX VNOPS, ETC USE ENOTSUP WHERE ENOSYS IS APPROPRIATE
13019958 - ACFS FILESYSTEM MOUNTS BECOME OFFLINE FREQUENTLY
13045518 - GBM SCANNING CAUSING PERFORMANCE PROBLEMS
13146653 - ACFS FILE SYSTEM FIXER DROPS CORE AND EXITS
13255295 - ACFS FILE SYSTEMS MAY GO OFFLINE ON AIX
Oracle Virtual Operating System Services
9382956 - VKRM TRACE FILES GENERATED WHEN RESOURCE MANAGER PLAN IS CLEARED
9672816 - DBRM SIGNALED ORA-7445[KSLDCLT_CLN()+297]
9829397 - ASYNC DESCRIPTOR RESIZE
GI PSU 11.2.0.2.4 contains all fixes released previous to GI PSU 11.2.0.2.4 (see Section 6.4 and Section 6.5 for a list of these bug fixes) and the following new fixes:
Automatic Storage Management
8685446 - ALLOWS NON-DEGENERATE EXADATA DISKGROUP WITH MISSING DISK(S) TO BE MOUNTED
9683047 - STALL ON AM ENQUEUE AFTER CELL FAILURE
9771278 - REQUIRED_MIRROR_FREE_MB IS WRONG VALUE IN LARGE DISKGROUP
9966609 - 11.2.0.2 : AIX : HIT ORA-600 [KFDCOPY_3] IN ASM INSTANCE DURING REBALANCE
10051315 - SEEING MAY TRACES WITH "WARNING: IO FAILED"
10055063 - WARNING: IO FAILED WHEN DOING SYNCHRONIZATION READ
10097711 - V$ASM_DISK.HASH_VALUE IS SHOWN AS 0 IN 11G R2 RDBMS INSTANCE EXADATA V2
10200404 - DROPPING DISK THAT GOES OFFLINE NOT EXPELLED WHEN EMPTY
10239480 - TB:X:REBOOT 1 CELL NODE AND KILL ASM LMS, DB INSTS ABORT DUE TO ORA-15081.
10264696 - DBMV2:A DISK FAILED TO ONLINE DUE TO RACE CONDITION IN LOOP TEST
10285022 - TB_ASM_SOL_SP64:ORA-7445[KFBTTRAVUNSIGNED()+200] IN INSTANCE RECOVERY
10285394 - DBMV2: ORA-700[KFNRELEASEASM1] SIGNALED BY CKPT AFTER EXHAUSTED FRA
10384285 - DBMV2:DATA CORRUPTION DURING GRIDDISK ACTIVE/INACTIVE LOOP TEST
10422126 - FAILED TO READ MORROR SIDE 1
11057263 - 11203_ASM_X64:ORA-7445 [KFK_IODONE_COMMON()+1061] IN OFFLING DISK
11666137 - DISMOUNTED DISKS ARE STILL HELD BY BACKGROUND PROCESSES FOR LONG TIME
11733179 - ASMB PROCESS HIT ORA-00600[KFFMUNLOCK_6],TERMINATE DB INSTANCE.
11785938 - ASM 11.2.0.2 IS NOT RELEASING FILE DESCRIPTORS AFTER DROP DISKGROUP
11889177 - ASM ADD DISK FAIL WITH ORA-600 [KFDOFFLINEPRIV05] AND FORCE DG DISMOUNT
12366627 - DATA FILE CORRUPTION AFTER RESIZING TABLESPACE OVER 4 BILLION BLOCKS
12546006 - RETRYING AN I/O MAY CAUSE A SPIN IF THE FILE IS CLOSED OR GROUP IS DISMOUNTED
12635537 - 11202_BP_ASM:X:ALL ASM INSTANCE HANGING AFTER INACTIVE/ACTIVE ALL GRIDDISKS
12639177 - LNX64-112-CMT: COMET ASM DISK NUMBER SHOULD BE THE SAME AS SLOT#, NEED FOR STM
Buffer Cache Management
10237773 - 11202-NT_2K8_X64:ORA-00600, ARGUMENTS: [KCBZ_CHECK_OBJD_TYP], [0], [0], [1], [],
10396041 - HASH LATCH SHOULD BE GOTTEN SHARED INSTEAD OF EXCLUSIVE
Generic
9564886 - ORA-600 [KGL-HASH-COLLISION] DURING TRIGGER EXECUTION
9746210 - APPS-R12:SQL-PROFILE :ORA-7445 [QSMMIXCOMPUTECLUSTERINGFACTOR] W/OFE=11.1.0.7
9795214 - DATABASE INSTANCE CRASHED DUE ORA-00600 [17074], ORA-822MMAN
9873405 - ORA-600 DURING FAST REFRESH AFTER 11.2.0.1.0 TO 11.2.0.2.0 UPDATE.
10399808 - DATA CORRUPTION THROUGH DBMS_LOB.WRITEAPPEND AND KOLE_T2U [34]
11893621 - DBMS_LOB.SUBSTR CAN TRUNCATE DATA OVER 8191 BYTES LONG IN MULTIBYTE CHARACTERSET
12340939 - ORA-07445 CORE DUMP [KGLIC0()+712] AND DATABASE HUNG
12670165 - LIBRARY CACHE MUTEX CONTENTION : KGLGET
High Availability
10035737 - A CORRUPT BLOCK WAS DETECTED DURING SHUTDOWN
10094823 - BLOCK CHANGE TRACKING ON PHYSICAL STANDBY CAN CAUSE DATA LOSS
10137324 - UNCONDITIONAL TRACE INFO LGWR - MAKING UPINBLS REQUEST TO LNS
10278773 - S941 RDBMS/SRC/SERVER/DRS/RFCFG.C VIOLATES OCCS 1.3.1.1, 7.2.1
10312847 - LOTS OF "DOING BLOCK RECOVERY FOR FILE X BLOCK Y" MESSAGES SEEN IN ALERT.LOG
10419984 - ACTIVE DATA GUARD STANDBY GIVES ORA-600 [KCBR_APPLY_CHANGE_11]
11670161 - EXCESSIVE KJFMHBUPDATETIME TRACING.
11827088 - LNX64-RAC: LMS WAITS FOR LATCH 'GC ELEMENT', LMHB TERMINATED INST.
11853815 - PHYSICAL STANDBY DB UNABLE TO FETCH ARCHIVE GAP LOG SEQUENCE
11894889 - SR11.2.0.3MEMORY_AND_DSS - TRC - KCRFW_ZERO_REWRITE_CORRUPT
12371955 - BACKUP TASK TRIGGERS JUMP IN SCN GROWTH RATE, LEADING TO ORA-600 [2252] ERRORS
12639234 - LOGICAL CORRUPTION FOUND AFTER OFFLINED FILE RECOVERY WAS PERFORMED
Oracle Diagnostics Infrastructure
9819805 - ORAUS.MSB BEING OPENED REPEATEDLY, UNTIL MAX FILES LIMIT IS HIT AND PROCESS FAIL
Oracle Portable ClusterWare
9458055 - CONNECTIONS FAIL WITH ORA-12537
9795321 - MTU SIZE FOR VIP UNDER 11GR2 GRID INFRASTRUCTURE
10161846 - BC: CHM/OS: DATA COLLECTION STOPPED ON ONE CLUSTER NODE
10229297 - LNX64-11202-CRF: OSYSMOND.BIN CONSUMES ABOUT 7.5% CPU IN KERNEL 2.6.32
10370797 - START OF 'ORA.CLUSTER_INTERCONNECT.HAIP' FAILED DURING UPGRADE TO 11.2.0.2
10420872 - 11.2.0.2 GRID INFRASTRUCTURE ROOT.SH FAILS
10428946 - SUSE10-LNX64-11203:OHASD.SLES NOT FOUND WHEN RAN ROOT.SH
11692271 - 11203-NT:PARALLEL STOP CRS STACK ON ALL NODES AND ASM STOP FAILED ON LAST NODE
11768055 - ONE NODE CSS JOIN CLUSTER,ALL OTHER NODES CSS ABORT FROM GM PEER LSNR
11768599 - LNX64-11203:THE ATTRIBUTES OF $CRS_HOME/CV/LOG/CVUTRACE.LOG.0 FILE ISN'T CORRECT
11777648 - LNX64-RAC: GMON IN +ASM1, 2, 4 HANG IN 'CSS GROUP REGISTRATION' AFTER REBOOT
11818524 - AT CLUSTER REBOOT, CEDING RECONFIG HAS WRONG RULES, CAUSING A STARTUP HANG
11820787 - 11202_GIBTWO_LINUX:CRSCTL START RES WITH ERROR "CRS-5010: UPDATE OF CONF FAILED"
11834289 - OHASD FAILED TO START TIMELY
11871469 - ORAAGENT CHECK TASK IS TIMING OUT WHICH IS FORCING THE AGENT TO ABORT AND EXIT
11925641 - SERVICES DON'T GET REGISTERED IN SUSE IN SIHA CONFIGURATION
12345151 - LNX64-11203: GIPCD COREDUMP AT GIPCDMONITORTHREAD.C:126
12359585 - AIX-11203-HA-CSS:ROOT.SH FAIL TO START ORA.CSSD DUE TO FAILURE OF EXADATA FENCE
12366642 - DB CHECK ACTIONS TAKE A LONG TIME IF THE SHARED POOL SIZE ISN'T TUNED
12406573 - GRID INFRASTRUCTURE DOES NOT START AFTER REBOOT
12412303 - LNX64-11203-DIT:PERMS OF $CH/CV/LOG/* WERE WRONG AFTER INSTALL RAC USING 2 USERS
12422324 - LNX64-112-CMT: HIT PRVF-7539 : GROUP "DBA" DOES NOT EXIST ON OUDA NODE
12424479 - LNX64-112-CMT: VIP FAILOVER TOOK 123 SECONDS AFTER PULLED OUT TWO PUBLIC CABLES
12426375 - ASM HANG 'GCS LOCK OPEN S'<='ENQ: FA - ACCESS FILE'
12546712 - HPI_11203_CRS:ORAROOTAGENT CORE DUMP WHEN ADDING PRIV NIC BACK VIA OIFCFG SETIF
12556028 - HPI_11203_CRS:CRSD LEAK MEMROY AT 8M/1.2H ON PE MASTER WITH OCR BUSY WORKLOAD RU
12597463 - LNX64-11201: NODE SHOULD BE EVICTION WHEN CRS HOME HANG FOR SOME TIME
12600343 - ORAAGENT DAEMON CRASH ISSUE
12615394 - GIPC API LEAKING MEMORY IN AIX
12651595 - STOP CRS FAILS DURING DOWNGRADE (11.2.0.3.0 TO 11.2.0.1.0)
12680491 - STOP DEPENDENCY BETWEEN NETWORK AND VIP MUST HAVE INTERMEDIATE MODIFYER
12695202 - AIX-11202GIB3_CRS:CRSD ORAAGENT COREDUMP AT CLSN_AGENT:INSTCONNECTION::BREAKCALL
12700217 - 11202_GIB3: CRSD AGENT CORE DUMP AT CLSN_AGENT::CONNECTIONPOOL::ABORTCONNECTIONS
12743755 - SET FENCING TYPE CAUSES CSSD TO SPIN
12767231 - AIX-11202-GIPC DISABLE SWITCH PORT FOR ONE PRIVATE NIC,HAIP DID NOT FAILOVER
12767563 - LNX64-11203-CRS: CRSD KEEPS CONSUMING HIGH CPU AFTER UPGRADED TO 11.2.0.3
12800501 - INSTANCE RESOURCE CHECK TIMED OUT AND SO RACGIMON STOPPED THE INSTANCE.
12823479 - FIX CMDLINE /PROC READ FOR EACH PID
13079948 - CVU FILES NOT BEING PICKED UP FOR 11.2.0.2.4GIPSU
Oracle Space Management
9414040 - 11GR2 ISSUE WITH TEMP SPACE
10281887 - REUSE CLAUSE IS BEING IGNORED CREATE TABLESPACE AND ADD DATAFILE
Oracle Universal Storage Management
11058691 - LNX64-11203-ACFS:ACFS CAN BE MOUNTED BUT CAN'T BE ACCESSED AFTER LONG RUNNING
11839004 - CRS-2799: FAILED TO SHUT DOWN RESOURCE 'ORA.DRIVERS.ACFS' ON 'SHESBDB1'
12433511 - SOL-X64-SC-ACFS:ACFS RELATED OPERATION HANG ON ALL CLUSTER NODES
12433819 - SOL_SP64: ACCESS ACFS HUNG AFTER ASM INSTANCE CRASH ON OTHER NODES
12591990 - ALLOW CHOWN OF LOST+FOUND ON SOLARIS, WINDOWS, AND AIX
12594736 - LNX64: NODE ASSERT AT OFS_DLM_CHECK_HASHTABLE_DEBUG WHEN UMOUNT ACFS
12614853 - SOL-SP-11203: ORACLEADVM DRIVER FAILED TO ATTACH AND ROOT.SH ABORT
12645334 - SOL-X64-SC-ACFS:HIT ASSERTION FAILURE: FALSE ON ORACLEACFS:PROCESSLOGFILE
12681864 - SOL-X64-SC-ACFS: ASSERTION:!(OFS_TEST_FCBSTATES(PFCB,OFS_FCB_DISK_UPDATE_NEEDED)
12694821 - ACFS HANG ACROSS CLUSTER
12700050 - 11203_ACFS_AIX: ACFS DISMOUNT HANG WHILE DOING DISMOUNT ON ALL NODES
12724761 - ACFS WILL NOT INSTALL ON AIX 7.1
12732899 - ACFS CORRUPTION WHEN A FILESYSTEM IS OVER 16T IN SIZE
12747467 - CHMOD CMD TO LOST+FOUND DIR IN ACFS FAILS - SIMILAR TO BUG 12545060
Oracle Virtual Operating System Services
10031806 - M8K: EFFECTIVE RM MAX CPU CAPPING IS WRONG WITH LARGE NUMBER OF CPUS
10039731 - HIGH WAITS FOR RUNNABLE PROCESS USING PX AND RESMGR
10048701 - DBRM WITH PARALLEL STAMENT QUEUEING OCCURES ORA-600 AND INSTANCE TERMINATED
10113990 - DISABLE RESOURCE MANAGER NUMA SUPPORT
10142909 - DO NOT PUSH SUBPLAN MAX UTILIZATION LIMIT TO EXADATA
10180307 - DBRM DBMS_RESOUCE_MANAGER.CALIBRATE_IO REPORTS VERY HIGH MAX_PMBPS ON EXADATA
10204358 - INCORRECT PQQ STATS FOR NON-REGULATED VT'S (LOG MINER - MS01)
10219583 - DBMV2: DATABASE HUNG AFTER 4 HRS OF ENABLE/DISABLE IORMPLAN
10229886 - 11202_GI_BUNDLE1 ORA-00600: [KSXP_RM_CHECK:RECUR] DURING CRS STACK STOP
10326338 - HIGH RESMGR:CPU QUANTUM WITH APPSQOS_PLAN IN PLACE
10622001 - DATABASE CRASH WITH ORA-7445 [KSFVIDMP]
10623249 - HIGH "LATCH FREE" WAIT EVENT WHEN RESOURCE MANAGER IS USED
11674898 - DBMV2: ORA-600[1433] SIGNALED AND INSTANCE TERMINATION
11695333 - POSSIBLE HANG IN KSKQRECALC
Server Manageability
10159846 - ORA-1 ON SYS.WRH$_TEMPSTATXS_PK WHEN COLLECTING AWR SNAPSHOT
GI PSU 11.2.0.2.3 contains all fixes previously released in GI PSU 11.2.0.2.3 (see Section 6.5 for a list of these bug fixes) and the following new fixes:
|
Note: ACFS is not supported on HP and therefore the bug fixes for ACFS do not apply to the HP GI PSU 5. |
Automatic Storage Management
6892311 - PROVIDE REASON FOR MOUNT FORCE FAILURE WITHOUT REQUIRING PST DUMP
9078442 - ORA-19762 FROM ASMCMD CP COPYING FILE WITH DIFFERENT BYTE ORDER FROM FILESYSTEM
9572787 - LONG WAITS FOR ENQ: AM CONTENTION FOLLOWING CELL CRASH CAUSED CLUSTERWIDE OUTAGE
9953542 - TB_SOL_SP: HIT 7445 [KFKLCLOSE()+20] ERROR WHEN DG OFFLINE
10040921 - HUNG DATABASE WORKLOAD AND BACKGROUNDS AFTER INDUCING WRITE ERRORS ON AVD VOLUME
10155605 - 11201-OCE:DISABLE FC IN ONE NODE, ASM DISKGOUP FORCE DISMOUNTED IN OTHER NODES.
10278372 - TB:X:CONSISTENTLY PRINT "WARNING: ELAPSED TIME DID NOT ADVANCE" IN ASM ALERT LOG
10310299 - TB:X:LOST WRITES DUE TO RESYNC MISSING EXTENTS WHEN DISK GO OFFLINE DURING REBAL
10324294 - DBMV2: DBFS INSTANCE WAITS MUCH FOR "ASM METADATA FILE OPERATION"
10356782 - DBMV2+: ASM INSTANCE CRASH WITH ORA-600 : [KFCGET0_04], [25],
10367188 - TB:X:REBOOT 2 CELL NODES,ASM FOREGROUND PROCESS HIT ORA-600[KFNSMASTERWAIT01]
10621169 - FORCE DISMOUNT IN ASM RECOVERY MAY DROP REDO'S AND CAUSE METADATA CORRUPTIONS
11065646 - ASM MAY PICK INCORRECT PST WHEN MULTIPLE COPIES EXTANT
11664719 - 11203_ASM_X64:ARB0 STUCK IN DG REBALANCE
11695285 - ORA-15081 I/O WRITE ERROR OCCURED AFTER CELL NODE FAILURE TEST
11707302 - FOUND CORRUPTED ASM FILES AFTER CELL NODES FAILURE TESTING.
11707699 - DATABASE CANNOT MOUNT DUE TO ORA-00214: CONTROL FILE INCONSISTENCY
11800170 - ASM IN KSV WAIT AFTER APPLICATION OF 11.2.0.2 GRID PSU
11800854 - BUG TO TRACK LRG 5135625
12620422 - FAILED TO ONLINE DISKS BECAUSE OF A POSSIBLE RACING RESYNC
Buffer Cache Management
11674485 - LOST DISK WRITE INCORRECTLY SIGNALLED IN STANDBY DATABASE WHEN APPLYING REDO
Generic
9748749 - ORA-7445 [KOXSS2GPAGE]
10082277 - EXCESSIVE ALLOCATION IN PCUR OF "KKSCSADDCHILDNO" CAUSES ORA-4031 ERRORS
10126094 - ORA-600 [KGLLOCKOWNERSLISTDELETE] OR [KGLLOCKOWNERSLISTAPPEND-OVF]
10142788 - APPS 11I PL/SQL NCOMP:ORA-04030: OUT OF PROCESS MEMORY
10258337 - UNUSABLE INDEX SEGMENT NOT REMOVED FOR "ALTER TABLE MOVE"
10378005 - EXPDP RAISES ORA-00600[KOLRARFC: INVALID LOB TYPE], EXP IS SUCCESSFUL
10636231 - HIGH VERSION COUNT FOR INSERT STATEMENTS WITH REASON INST_DRTLD_MISMATCH
12431716 - UNEXPECTED CHANGE IN MUTEX WAIT BEHAVIOUR IN 11.2.0.2.2 PSU (HIGHER CPU POSSIBLE
High Availability
9869401 - REDO TRANSPORT COMPRESSION (RTC) MESSAGES APPEARING IN ALERT LOG
10157249 - CATALOG UPGRADE TO 11.2.0.2 FAILS WITH ORA-1
10193846 - RMAN DUPLICATE FAILS WITH ORA-19755 WHEN BCT FILE OF PRIMARY IS NOT ACCESSIBLE
10648873 - SR11.2.0.3TXN_REGRESS - TRC - KCRFW_REDO_WRITE
11664046 - STBH: WRONG SEQUENCE NUMBER GENERATED AFTER DB SWITCHOVER FROM STBY TO PRIMARY
Oracle Portable ClusterWare
8906163 - PE: NETWORK AND VIP RESOURCES FAIL TO START IN SOLARIS CONTAINERS
9593552 - GIPCCONNECT() IS NOT ASYNC 11.2.0.2GIBTWO
9897335 - TB-ASM: UNNECCESSARY OCR OPERATION LOG MESSAGES IN ASM ALERT LOG WITH ASM OCR
9902536 - LNX64-11202-MESSAGE: EXCESSIVE GNS LOGGING IN CRS ALERT FILE WHEN SELFCHECK FAIL
9916145 - LX64: INTERNAL ERROR IN CRSD.LOG, MISROUTED REQUEST, ASSERT IN CLSM2M.CPP
9916435 - ROOTCRS.PL FAILS TO CREATE NODEAPPS DURING ADD NODE OPERATION
9939306 - SERVICES NOT COMING UP AFTER SWITCHOVER USING SRVCTL START DATABASE
10012319 - ORA-600 [KFDVF_CSS], [19], [542] ON STARTUP OF ASM DURING ADDNODE
10019726 - MEMORY LEAK 1.2MB/HR IN CRSD.BIN ON NON-N NODE
10056713 - LNX64-11202-CSS: SPLIT BRAIN WHEN START CRS STACK IN PARALLEL WITH PRIV NIC DOWN
10103954 - INTERMITTENT "CANNOT COMMUNICATE WITH CRSD DAEMON" ERRORS
10104377 - GIPC ENSURE INITIAL MESSAGE IS NOT LOST DURING ESTABLISH PHASE
10115514 - SOL-X64-11202: CLIENT REGISTER IN GLOBAL GROUP MASTER#DISKMON#GROUP#MX NOT EXIT
10190153 - HPI-SG-11202 ORA.CTSSD AND ORA.CRSD GOES OFFLINE AFTER KILL GIPC ON CRS MASTER
10231906 - 11202-OCE-SYMANTEC:DOWN ONE OF PRIVAE LINKS ON NODE 3,OCSSD CRASHED ON NODE 3
10233811 - AFTER PATCHING GRID HOME, UNABLE TO START RESOURCES DBFS AND GOLDEN
10253630 - TB:X:HANG DETECTED,"WAITING FOR INSTANCE RECOVERY OF GROUP 2" FOR 45 MINUTES
10272615 - TB:X:SHUTDOWN SERVICE CELLD ON 2 CELL NODES,CSSD ABORT IN CLSSNMRCFGMGRTHREAD
10280665 - TB:X:STOP CELLD ON 2 CELL NODES,CSSD ABORT IN CLSSNMVVERIFYPENDINGCONFIGVFS
10299006 - AFTER 11.2.0.2 UPGRADE, ORAAGENT.BIN CONNECTS TO DATABASE WITH TOO MANY SESSIONS
10322157 - 11202_GIBONE: PERM OF FILES UNDER $CH/CRS/SBS CHANGED AFTER PATCHED
10324594 - STATIC ENDPOINT IN THE LEASE BLOCKS OVERWRITTEN DURING UPGRADE
10331452 - SOL-11202-UD: 10205->11202 NETWORK RES USR_ORA_IF VALUE MISSED AFTER UPGRADE
10357258 - SOL-11202-UD: 10205->11202 [IPMP] HUNDREDS OF DUP IP AFTER INTRA-NODE FAILOVER
10361177 - LNX64-11203-GNS: MANY GNS SELF CHECK FAILURE ALERT MESSAGES
10385838 - TB:X:CSS CORE DUMP AT GIPCHAINTERNALSEND
10397652 - AIX-11202-GIPC:DISABLE SWITCH PORT FOR ONE PRIVATE NIC,HAIP DID NOT FAILOVER
10398810 - DOUBLE FREE IN SETUPWORK DUE TO TIMING
10419987 - PEER LISTENER IS ACCESSING A GROCK THAT IS ALREADY DELETED
10621175 - TB_RAC_X64:X: CLSSSCEXIT: CSSD SIGNAL 11 IN THREAD GMDEATHCHECK
10622973 - LOSS OF LEGACY FEATURES IN 11.2
10631693 - TB:X:CLSSNMHANDLEVFDISCOVERACK: NO PENDINGCONFIGURATION TO COMPLETE. CSS ABORT
10637483 - TB:X:REBOOT ONE CELL NODE, CSS ABORT AT CLSSNMVDDISCTHREAD
10637741 - HARD STOP DEPENDENCY CAN CAUSE WRONG FAIL-OVER ORDER
10638381 - 11202-OCE-SYMANTEC: HAIP FAIL TO START WHEN PRIVATE IP IS PLUMBED ON VIRTUAL NIC
11069614 - RDBMS INSTANCE CRASH DUE TO SLOW REAP OF GIPC MESSAGES ON CMT SYSTEMS
11071429 - PORT 11GR2 CRS TO EL6
11654726 - SCAN LISTENER STARTUP FAILS IF /VAR/OPT/ORACLE/LISTENER.ORA EXISTS.
11663339 - DBMV2:SHARED PROCESS SPINNING CAUSES DELAY IN PRIMARY MEMBER CLEANUP
11682409 - RE-USING OCI MEMORY ACROSS CONNECTIONS CAUSES A MEMORY CORRUPTION
11698552 - SRVCTL REPORT WRONG STATUS FOR DATABASE INSTANCE.
11741224 - INCORRECT ACTIVE VERSION CHECK WHILE ENABLING THE BATCH FUNCTIONALITY
11744313 - LNX64-11203-RACG: UNEXPECTED CRSD RESTART DURING PARALLEL STACK START
11775080 - ORA-29701/29702 OCCURS WHEN WORKLOAD TEST RUNNING FOR A LONG TIME AND IS RESTART
11781515 - EVMD/CRSD FAIL TO START AFTER REBOOT, EVEN AFTER CRSCTL START CLUSTERWARE
11807012 - LNX64-11203-RACG: DB SERVICE RUNS INTO "UNKNOWN" STATE AFTER STACK START
11812615 - LNX64-11203-DIT: INCONSISTENT PERMISSION BEFORE/AFTER ROOTCRS.PL -UNLOCK/-PATCH
11828633 - DATABASE SERVICE DID NOT FAIL OVER AND COULD NOT BE STARTED AFTER NODE FAILURE
11840629 - KERNEL CRASH DUMP AND REBOOT FAIL INSIDE SOLARIS CONTAINER
11866171 - ENABLE CRASHDUMP WHEN REBOOTING THE MACHINE (LINUX)
11877079 - HUNDREDS OF ORAAGENT.BIN@HOSTNAME SESSSIONS IN 11.2.0.2 DATABASE
11899801 - 11202_GIBTWO_HPI:AFTER KILL ASM PMON, POLICY AND ADMIN DB RUNNING ON SAME SERVER
11904778 - LNX64-OEL6-11202: CRS STACK CAN'T BE START AFTER RESTART
11933693 - 11.1.0.7 DATABASE INSTANCE TERMINATED BY 11.2.0.2 CRS AGENT
11936945 - CVU NOT RECOGNIZING THE OEL6 ON LINUX
12332919 - ORAAGENT KEEPS EXITING
12340501 - SRVCTL SHOWS INSTANCE AS DOWN AFTER RELOCATION
12340700 - EVMD CONF FILES CAN HAVE WRONG PERMISSIONS AFTER INSTALL
12349848 - LNX64-11203: VIPS FELL OFFLINE WHEN BRING DOWN 3/4 PUBLIC NICS ONE BY ONE
12378938 - THE LISTENER STOPS WHEN THE ORA.NET1.NETWORK'S STATE IS CHANGED TO UNKNOWN
12380213 - 11203_110415:ERROR EXCEPTION WHILE INSTALLATION 11202 DB WITH DATAFILES ON 11203
12399977 - TYPO IN SUB PERFORM_START_SERVICE RETURNS ZERO (SUCCESS) EVEN WHEN FAILED
12677816 - SCAN LISTENER FAILD TO STARTUP IF /VAR/OPT/ORACLE/LISTENER.ORA EXIST
Oracle Space Management
8223165 - ORA-00600 [KTSXTFFS2] AFTER DATABASE STARTUP
9443361 - WRONG RESULTS (ROWDATA) FOR SELECT IN SERIAL FROM COMPRESSED TABLE
10061015 - LNX64-11202:HIT MANY ORA-600 ARGUMENTS: [KTFBHGET:CLSVIOL_KCBGCUR_9] DURING DBCA
10132870 - INDEX BLOCK CORRUPTION - ORA-600 [KCBZPBUF_2], [6401] ON RECOVER
10324526 - ORA-600 [KDDUMMY_BLKCHK] [6106] WHEN UPDATE SUBPARTITION OF TABLE IN TTS
Oracle Transaction Management
10053725 - TS11.2.0.3V3 - TRC - K2GUPDATEGLOBALPREPARECOUNT
10233732 - ORA-600 [K2GUGPC: PTCNT >= TCNT] OCCURS IN A DATABASE LINK TRANSACTION
Oracle Universal Storage Management
9867867 - SUSE10-LNX64-11202:NODE REBOOT HANG WHILE ORACLE_HOME LOCATED ON ACFS
9936659 - LNX64-11202-CRS: ORACLE HOME PUT ON ACFS, DB INST FAILS TO RESTART AFTER CRASH
9942881 - TIGHTEN UP KILL SEMANTICS FOR 'CLEAN' ACTION.
10113899 - AIX KSPRINTTOBUFFER TIMESTAMPS NEEDS TIME SINCE BOOT AND WALL_CLOCK TIMES
10266447 - ROOTUPGRADE.SH FAILS: 'FATAL: MODULE ORACLEOKS NOT FOUND' , ACFS-9121, ACFS-9310
11789566 - ACFS RECOVERY PHASE 2
11804097 - GBM LOCK TAKEN WHEN DETERMINING WHETHER THE FILE SYSTEM IS MOUNTED AND ONLINE
11846686 - ACFSROOT FAILS ON ORACLELINUX-RELEASE-5-6.0.1 RUNNUNG A 2.6.18 KERNEL
12318560 - ALLOW IOS TO RESTART WHEN WRITE ERROR MESG RETURNS SUCCESS
12326246 - ASM TO RETURN DIFF VALUES WHEN OFFLINE MESG UNSUCCESSFUL
12378675 - AIX-11203-HA-ACFS: HIT INVALID ASM BLOCK HEADER WHEN CONFIGURE DG USING AIX LVS
12398567 - ACFS FILE SYSTEM NOT ACCESSIBLE
12545060 - CHOWN OR RM CMD TO LOST+FOUND DIR IN ACFS FAILS ON LINUX
Oracle Utilities
9735282 - GETTING ORA-31693, ORA-2354, ORA-1426 WHEN IMPORTING PARTITIONED TABLE
Oracle Virtual Operating System Services
10317487 - RMAN CONTROLFILE BACKUP FAILS WITH ODM ERROR ORA-17500 AND ORA-245
11651810 - STBH: HIGH HARD PARSING DUE TO FILEOPENBLOCK EATING UP SHARED POOL MEMORY
XML Database
10368698 - PERF ISSUE WITH UPDATE RESOURCE_VIEW DURING AND AFTER UPGRADING TO 11.2.0.2
This section describes bugs fixed in the GI PSU 11.2.0.2.2 release.
ACFS
10015603 - KERNEL PANIC IN OKS DRIVER WHEN SHUTDOWING CRS STACK
10178670 - ACFS VOLUMES ARE NOT MOUNTING ONCE RESTARTED THE SERVER
10019796 - FAIL TO GET ENCRYPTION STATUS OF FILES UNTIL DOING ENCR OP FIRST
10029794 - THE DIR CAN'T READ EVEN IF THE DIR IS NOT IN ANY REALM
10056808 - MOUNT ACFS FS FAILED WHEN FS IS FULL
10061534 - DB INSTANCE TERMINATED DUE TO ORA-445 WHEN START INSTANCE ON ALL NODES
10069698 - THE EXISTING FILE COULD CORRUPT IF INPUT INCORRECT PKCS PASSOWRD
10070563 - MULTIPLE WRITES TO THE SAME BLOCK WITH REPLICATION ON CAN GO OUT OF ORDER
10087118 - UNMOUNT PANICS IF ANOTHER USER IS SITTING IN A SNAPSHOT ROOT DIRECTORY
10216878 - REPLI-RELATED RESOURCE FAILED TO FAILOVER WHEN DG DISMOUNTED
10228079 - MOUTING DG ORA-15196 [KFC.C:25316] [ENDIAN_KFBH] AFTER NODE REBOOT
10241696 - FAILED TO MOUNT ACFS FS TO DIRECTORY CREATED ON ANOTHER ACFS FS
10252497 - ADVM/ACFS FAILS TO INSTALL ON SLES10
9861790 - LX64: ADVM DRIVERS HANGING OS DURING ACFS START ATTEMPTS
9906432 - KERNEL PANIC WHILE DISMOUNT ACFS DG FORCE
9975343 - FAIL TO PREPARE SECURITY IF SET ENCRYPTION FIRST ON THE OTHER NODE
10283549 - FIX AIX PANIC AND REMOVE -DAIX_PERF
10283596 - ACFS:KERNEL PANIC DURING USM LABEL PATCHING - ON AIX
10326548 - WRITE-PROTETED ACFS FILES SHOULD NOT BE DELETED BY NON-ROOT USER
ADVM
10045316 - RAC DB INSTALL ON SHARED ACFS HANGS AT LINKING PHASE
10283167 - ASM INSTANCE CANNOT STARTUP DUE TO EXISTENCE OF VMBX PROCESS
10268642 - NODE PANIC FOR BAD TRAP IN "ORACLEADVM" FOR NULL POINTER
10150020 - LINUX HANGS IN ADVM MIRROR RECOVERY, AFTER ASM EVICTIONS
Automatic Storage Management
9788588 - STALENESS REGISTRY MAY GET CLEARED PREMATURELY
10022980 - DISK NOT EXPELLED WHEN COMPACT DISABLED
10040531 - ORA-600 [KFRHTADD01] TRYING TO MOUNT RECO DISKGROUP
10209232 - STBH: DB STUCK WITH A STALE EXTENT MAP AND RESULTS IN DATA CORRUPTIONS
10073683 - ORA-600 [KFCBINITSLOT40] ON ASM ON DBMV2 WITH BP5
9715581 - DBMV2: EXADATA AUTO MANAGEMENT FAILED TO BRING UP DISKS ONLINE
10019218 - ASM DROPPED DISKS BEFORE DISK_REPAIR_TIME EXPIRED
10084145 - DBMV2: ORA-600 [1427] MOUNTING DISKGROUP AFTER ALL CELLS RESTARTED
11067567 - KEPT GENERATING "ELAPSED TIME DID NOT ADVANCE " IN ASM ALERT LOG
10356513 - DISK OFFLINED WITH NON ZERO TIMEOUT EXPELLED IMMEDIATELY
10332589 - TB:X:MOUNT NORMAL REDUNDANCY DG, FAILED WITH ORA-00600:[KFCINITRQ20]
10329146 - MARKING DIFFERENT SR BITS FROM MULTIPLE DBWS CAN CAUSE A LOST WRITE
10299224 - TB:X:PIVOTING AN EXTENT ON AN OFFLINE DISK CAN CAUSE STALE XMAPS IN RDBMS
10245086 - ORA-01210 DURING CREATE TABLESPACE
10230571 - TB:X:REBOOT ONE CELL NODE, RBAL HIT ORA-600[17183]
10228151 - ASM DISKGROUPS NOT GETTING MOUNTED
10227288 - DG FORCIBLY DISMOUNTED AFTER ONE FG LOST DUE TO "COULD NOT READ PST FOR GRP 4"
10222719 - ASM INSTANCE HANGS WITH RBAL PROCESS WAITS ON "NO FREE BUFFER"
10102506 - DISK RESYNC TAKES A LONG TIME EVEN WITH NO STALE EXTENTS
10094201 - DISK OFFLINE IS SLOW
10190642 - ORA-00600: [1433] FOLLOWED BY INSTANCE CRASH WITH ASM ON EXADATA
11067567 - 11202_gibtwo: kept generating "elapsed time did not advance " in asm alert log
Buffer Cache Management
9651350 - ora-00308 and ora-27037 when ora-8103 without event 10736 been set
10110863 - trace files is still generated after applying patch:9651350
10205230 - tb_x64: hit ora-00600: [kclwcrs_6]
10332111 - sql running long in active standby
CRS Group
CLEANUP
9949676 - GNSD.BIN CORE DUMP AFTER KILL ASM PMON ON ALL NODES AT SAME TIME
9975837 - GNS INCORRECTLY PROCESSES IPV6 LOOKUP REQUESTS
10007185 - GNS DUMPS CORE IN CLSKGOPANIC AT CLSKPDVA 717
10028343 - GNS CAN NOT BE RELOCATED AFTER PUBLIC RESTARTED
CRS
9876201 - OHASD AGENT CORE DUMP AT EONSHTTP.C:162
10011084 - 11202 STEP3 MODIFY BINARY AFTER INSTALLATION CANNOT EXCUTE SUCCESSFULLY
10028235 - 'CLSNVIPAGENT.CPP', LINE 1522: ERROR: FORMAL ARGUMENT TYPE OF ...
10045436 - 'ORA.LISTENER.LSNR' FAILED TO BE FENCED OFF DURING CRSD CLEANUP
10062301 - VALUE FOR FIELD 'CLUSTER_NAME' IS MISSING IN CRSCONFIG_PARAMS
10110969 - PORTABILITY ISSUES IN FUNCTION TOLOWER_HOST
10175855 - FAILED TO UGPRADE 11.2.0.1 + ARU 12900951 -> 11.2.0.2
9891341 - CRSD CORE DUMP IN PROATH_MASTER_EXIT_HELPER AT PROATH.C:1834
11655840 - RAC1 DB' STATE_DETAILS IS WRONG AFTER KILL GIPCD
10634513 - OHASD DUMPS CORE WHEN PLUG IN UNPLUGGED PRIVATE NETWORK NIC
10236074 - ASM INSTANCES CRASH SEVERAL TIMES DURING PARALLEL CRS STARTUP
10052529 - DB INST OFFLINE AFTER STOP/START CRS STACK ON ALL NODES IN PARALLEL
10065216 - VIRTUAL MEMORY USAGE OF ORAROOTAGENT IS BIG(1321MB) AND NOT DECREASING
10168006 - ORAAGENT PROCESS MEMORY GROWTH PERIODICALLY.
CSS
9907089 - CSS CORE DUMP DURING EXADATA ROLLING UPGRADE
9926027 - NODE REBOOTED AFTER CRS CLEAN-UP SUCCEEDED 11202 GI + 10205 RAC DB
10014392 - CRSCTL DELETE NODE FAILS WITH CRS-4662 & CRS-4000
10015460 - REMOVAL OF WRONG INCARNATION OF A NODE DUE TO MANUAL SHUTDOWN STATE
10040109 - PMON KILL LEAD TO OS REBOOT
10048027 - ASM UPGRADE FAILS
10052721 - 11201- 11202 NON-ROLLING,CRSCTL.BIN CORE AT CLSSNSQANUM, SIGNAL 11
10083789 - A NODE DOESNT INITIATE A RECONFIG DUE TO INCORRECT RECONFIG STATE
9944978 - FALSE CSS EVICTION AFTER PRIVATE NIC RESUME
9978195 - STOP DB ACTION TIMED OUT AND AGENT EXITS DUE TO FAILURE TO STOP EVENT BRIDGE
10248739 - AFTER APPLY THE PATCH, THE NODE EVICTED DURING START CRS STACK
CVU
9679401 - OUI PREREQ CHECKS FAILED FOR WRONG OWNSHIP OF RESOLV.CONF_`HOST`
9959110 - GNS INTEGRITY PREREQUISITE FAILED WITH PRVF-5213
9979706 - COMP OCR CHECK FAILS TO VERIFY SIZE OF OCR LOCATION
10029900 - CVU PRE NODEADD CHECK VD ERROR
10033106 - ADDNODE.SH SHOULD INDICATE WHAT HAPPENS WHEN ERROR OCCURRING
10075643 - UNABLE TO CONTINUE CONFIG.SH FOR CRS UPGRAD
10083009 - GIPCD FAILS TO RETRIEVE INFORMATION FROM PEERS DUE TO INVALID ENDPOINT
GIPC
9812956 - STATUS OF CRSD AND EVMD GOES INTERMEDIATE FOR EVER WHEN KILL GIPC
9915329 - ORA-600 [603] IN DB AND ORA-603 IN ASM AFTER DOWN INTER-CONNECT NIC
9944948 - START RESOUCE HAIP FAILED WHEN RUN ROOT.SH
9971646 - ORAROOTAGENT CORE DUMPED AT NETWORKHAMAINTHREAD::READROUTEDATA
9974223 - GRID INFRASTRUCTURE NEEDS MULTICAST COMMUNICATION ON 230.0.1.0 ADDRESSES WORKING
10053985 - ERROR IN NETWORK ADDRESS ON SOLARIS 11
10057680 - OHASD ORAROOTAGENT.BIN SPIN CPU AFTER SIMULATE ASM DISK ERROR
10078086 - ROOTUPGRADE.SH FAIL FOR 'CRSCTL STARTUPGRADE' FAIL,10205-> 11202
10260251 - GRID INSTALLATION FAILS TO START HAIP DUE TO CHANGE IN NETWORK INTERFACE NAME
10111010 - CRSD HANGS FOR THE HANAME OF PEER CRSD
11782423 - OHASD.BIN TAKES CPU ABOUT 95% ~ 100%
11077756 - STARTUP FAILURE OF HAIP CAUSES INSTALLATION FAILURE
10375649 - DISABLE HAIP ON PRIMECLUSTER
10284828 - INTERFACE UPDATES GET LOST DURING BOUNCE OF CRSD PROCESS
10284693 - AIX EPIPE FAILURE
10233159 - NEED 20 MINS TO STARTUP CRS WHEN 1/2 GIPC NICS DOWN
10128191 - LRGSRG9 AND LRGSRGE FAILURE
GNS
9864003 - NODE REBOOT DUE TO 'ORA.GNS' FAILED TO BE FENCED OFF DURING CRSD
GPNP
9336825 - GPNPD FLUSH PROFILE PUSH ERROR MESSAGES IN CRS ALERT LOG
10314123 - GPNPD MAY NOT UPDATE PROFILE TO LATEST ON START
10105195 - PROC-32 ACCESSING OCR; CRS DOES NOT COME UP ON NODE
10205290 - DBCA FAILED WITH ERROR ORA-00132
10376847 - [ORA.CRF] [START] ERROR = ERROR 9 ENCOUNTERED WHEN CONNECTING TO MOND
IPD-OS
9812970 - IPD DO NOT MARK TYPE OF DISKS USED FOR VOTING DISK CORRECTLY
10057296 - IPD SPLIT BRAIN AFTER CHANGE BDB LOCATION
10069541 - IPD SPLIT BRAIN AFTER STOPPING ORA.CRF ON MASTER NODE
10071992 - UNREASONABLE VALUES FOR DISK STATISTICS
10072474 - A NODE IS NOT MONITORED AFTER STOP AND START THE ORA.CRF ON IT
10073075 - INVALID DATA RECEIVED FROM THE CLUSTER LOGGER SERVI
10107380 - IPD NOT STARTED DUE TO SCRFOSM_GET_IDS FAILED
OCR
9978765 - ROOTUPGRADE.SH HANG AND CRSD CRASHED ON OTHER NODES,10205-> 11202
10016083 - 'OCRCONFIG -ADD' NEEDS HELPFUL MESSAGE FOR ERROR ORA-15221
OPSM
9918485 - EMCONFIG FAIL WITH NULLPOINTEREXCEPTION AT RACTRANSFERCORE.JAVA
10018215 - RACONE DOES NOT SHUTDOWN INSTANCE DURING RELOCATION
10042143 - ORECORE11 LWSFDSEV CAUSED SEGV IN SRVM NATIVE METHODS
OTHERS
9963327 - CHMOD.PL GETS CALLED INSTEAD OF CHMOD.EXE
10008467 - FAILS DUE TO WRONG VERSION OF PERL USED:
10015210 - OCTSSD LEAK MEMORY 1.7M HR ON PE MASTER DURING 23 HOURS RUNNI
10027079 - CRS_SHUTDOWN_SYNCH EVENT NOT SENT IN SIHA
10028637 - SCLS.C COMPILE ERRORS ON AIX UNDECLARED IDENTIFIERS
10029119 - 11201-11202 CRS UPGRADE OUI ASKS TO RUN ROOTUPGRADE.SH
10036834 - PATCHES NOT FOUND ERROR WHILE UPGRADING GRID FROM 11201 TO 11202
10038791 - HAS SRG SRV GETTING MANY DIFS FOR AIX ON LABEL 100810 AND LATER
10040647 - LNX64-112022-UD; AQ AND RLB DO NOT WORK AFTER UPGRADING FROM 11201
10044622 - EVMD FAILED TO START AFTER KILL OHASD.BIN
10048487 - DIAGCOLLECTION CANNOT RETRIEVE IPD REPORTS
10073372 - DEINSTALL FAILED TO DELETE CRS_HOME ON REMOTE NODE IF OCR VD ON NFS
10089120 - WRONG PROMPT MESSAGE BY DEINSTALL COMMAND WHILE DELETING CRS HOME
10124517 - CRS STACK DOES NOT START AUTOMATICALLY AFTER NODE REBOOT
10157622 - 11.2.0.2 GI BUNDLE 1 HAS-CRS TRACKING BUG
RACG
10036193 - STANDBY NIC DOESN'T WORK IF DOWN PUBLIC NIC
10146768 - NETWORK RESOURCE FAILS TO START WITH IPMP ON SOLARIS 11
USM Miscellaneous
10146744 - ORA.REGISTRY.ACFS BECOME UNKOWN AND ACFS FS DISMOUNT
10283058 - RESOURCES ACFS NEEDS AN OPTION TO DISALLOW THE MOUNTING OF FILE SYSTEMS ON RESOURCE START
10193581 - ROOT.SH CRS-2674: START OF 'ORA.REGISTRY.ACFS' FAIL
10244210 - FAIL TO INSTALL ADVM/ACFS ON SOLARIS CONTAINER
10311856 - APPLY ASSERTION FAILURE:PBOARDENTRY>USRGBOARDRECENTRY_RECORD
Generic
9591812 - incorrect wait events in 11.2 ("cursor: mutex s" instead of "cursor: mutex x")
9905049 - ebr: ora-00600: internal error code, arguments: [kqlhdlod-bad-base-objn]
10052141 - exadata database crash with ora-7445 [_wordcopy_bwd_dest_aligned] and ora-600 [2
10052956 - ora-7445 [kjtdq()+176]
10157402 - lob segment has null data after long to lob conversion in parallel mode
10187168 - obsolete parent cursors if version count exceeds a threshold
10217802 - alter user rename raises ora-4030
10229719 - qrmp:12.2:ora-07445 while performing complete database import on solaris sparc
10264680 - incorrect version_number reported after patch for 10187168 applied
10411618 - add different wait schemes for mutex waits
11069199 - ora-600 [kksobsoletecursor:invalid stub] quering pq when pq is disabled
11818335 - additional changes when wait schemes for mutex waits is disabled
High Availability
10018789 - dbmv2-bigbh:spin in kgllock caused db hung and high library cache lock
10129643 - appsst gsi11g m9000: ksim generic wait event
10170431 - ctwr consuming lots of cpu cycles
Oracle Space Management
6523037 - et11.1dl: ora-600 [kddummy_blkchk] [6110] on update
9724970 - pdml fails with ora-600 [4511]. ora-600 [kdblkcheckerror] by block check
10218814 - dbmv2: ora-00600:[3020] data block corruption on standby
10219576 - ora-600 [ktsl_allocate_disp-fragment]
Oracle Transaction Management
10358019 - invalid results from flashback_transaction_query after applying patch:10322043
Oracle Utilities
10373381 - ora-600 [kkpo_rcinfo_defstg:objnotfound] after rerunning catupgrd.sql
Oracle Virtual Operating System Services
10127360 - dg4msql size increasing to 1.5gb after procedure executed 250 times
Server Manageability
11699057 - ora-00001: unique constraint (sys.wri$_sqlset_plans_tocap_pk) violated
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Access to Oracle Support
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Patch 13343447 - 11.2.0.2.5 GI Patch Set UpdateRelease 11.2.0.2.5 for Grid Infrastructure
Copyright © 2006, 2012, 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 of The Open Group.
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.