Skip Headers

Oracle® Database

Patch 9352164 - 10.2.0.4.4 Patch Set Update

 

Released: April 13, 2010

This document is accurate at the time of release. For any changes and additional information regarding PSU 10.2.0.4.4, see these related documents that are available at My Oracle Support (http://support.oracle.com/):

This document includes the following sections:

1 Patch Information

Patch Set Update (PSU) patches are cumulative. That is, the content of all previous PSUs is included in the latest PSU patch.

PSU 10.2.0.4.4 includes all fixes previously included in PSU 10.2.0.4.3 and those listed in Section 5, "Bugs Fixed by This Patch".

To install the PSU 10.2.0.4.4 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.4 can be installed on 10.2.0.4.0, 10.2.0.4.1, 10.2.0.4.2, and 10.2.0.4.3.

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


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


2 Patch Installation and Deinstallation

This section includes the following sections:

2.1 Platforms for PSU 10.2.0.4.4

For a list of platforms that are supported in this Patch Set Update, see My Oracle Support Note 1060989.1 Critical Patch Update April 2010 Patch Availability Document for Oracle Products.

2.2 OPatch Utility Information

You must use the OPatch 10.2 version 10.2.0.4.7 or later to apply this patch. 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.

2.3 Patch Installation

These instructions are for both non-RAC environments and RAC environments.

2.3.1 Patch Pre-Installation Instructions

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

2.3.1.1 Environment Checks
  1. Ensure that the $PATH definition has the following executables: make, ar, ld, and nm.

    The location of these executables depends on your operating system. On many operating systems, they are located in /usr/ccs/bin, in which case you can set your PATH definition as follows:

    export PATH=$PATH:/usr/ccs/bin
    
2.3.1.2 "spare" Parameters and One-off Patches

If you have any one-off patches installed in the Database home, you must check whether any "spare" parameters (_first_spare_parameter, _second_spare_parameter, and so on) are set in the init.ora file before installing the 10.2.0.4.4 PSU. Failure to do so could result in memory corruption.

  • If no "spare" parameters are set, or the only one set is _first_spare_parameter for bug 7291739, then no other action is required.

  • Otherwise, you must follow additional steps (explained in Section 2.3.2, "Patch Installation Instructions") during the patch installation, including explicit rollback of the conflicting patch that includes "spare" parameter changes.

To check if any "spare" parameters are set, enter the following statements:

sqlplus
SQL> CONNECT / AS SYSDBA
SQL> show parameter spare
2.3.1.3 One-off Patch Conflict Detection and Resolution

For an introduction to the PSU one-off patch concepts, see "Patch Set Updates Patch Conflict Resolution" in My Oracle Support 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:

  1. Determine whether any currently installed one-off patches conflict with the PSU patch as follows:

    unzip p9352164_10204_<platform>.zip
    opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir ./9352164
    
  2. The report will indicate the patches that conflict with PSU 9352164 and the patches for which PSU 9352164 is a superset. Refer to "Patch Set Updates Patch Conflict Resolution" in My Oracle Support Note 854428.1 Patch Set Updates for Oracle Products.

    Note that Oracle proactively provides 10.2.0.4.3 one-off patches for common conflicts.

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

  4. When all the 10.2.0.4.4 one-off patches that you have requested are available at My Oracle Support, proceed with Section 2.3.2, "Patch Installation Instructions".

2.3.2 Patch Installation Instructions

Follow these steps:

  1. If you are using a Data Guard Physical Standby database, you must first install this patch on the primary database before installing the patch on the physical standby database. It is not supported to install this patch on the physical standby database before installing the patch on the primary database. For more information, see My Oracle Support Note 278641.1.

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

  3. If "spare" parameters been set for any bug fixes other than 7291739 (as checked in Section 2.3.1.2, ""spare" Parameters and One-off Patches"), see My Oracle Support Note 1083413.1 Important Information about "spare" Database Parameters for the actions required.

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

  5. Set your current directory to the directory where the patch is located and then run the OPatch utility by entering the following commands:

    unzip p9352164_10204_<platform>.zip
    cd 9352164
    opatch apply
    
  6. If there are errors, refer to Section 3, "Known Issues".

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

2.3.3 Post Installation Instructions

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:

  1. Apply conflict resolution patches as explained in Section 2.3.3.1.

  2. Load modified SQL files into the database, as explained in Section 2.3.3.2.

  3. Optionally, configure for undo retention (bug 7291739), as explained in Section 2.3.3.3.

  4. Recompile views in the database, if necessary, as explained in Section 2.3.3.4.

2.3.3.1 Applying Conflict Resolution Patches

Apply the patch conflict resolution one-off patches that were determined to be needed when you performed the steps in Section 2.3.1.3, "One-off Patch Conflict Detection and Resolution".

2.3.3.2 Loading Modified SQL Files into the Database

The following steps load modified SQL files into the database. For a RAC environment, perform these steps on only one node.

  1. For each database instance running on the Oracle home being patched, connect to the database using SQL*Plus. Connect as SYSDBA and run the catbundle.sql script as follows:

    cd $ORACLE_HOME/rdbms/admin
    sqlplus /nolog
    SQL> CONNECT / AS SYSDBA
    SQL> STARTUP
    SQL> @catbundle.sql psu apply
    SQL> -- Execute the next statement only if this is the first 10.2.0.4 PSU applied in the Oracle home.
    SQL> @utlrp.sql
    SQL> QUIT
    

    For information about the catbundle.sql script, see My Oracle Support Note 605795.1 Introduction to Oracle Database catbundle.sql.

  2. Check the following log files in $ORACLE_HOME/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".

2.3.3.3 Optional: Configuring for Undo Retention (Bug 7291739)

The PSU includes the fix for bug 7291739, which allows you to specify the high threshold undo retention by setting _first_spare_parameter. The tuned value of undo retention will then not exceed the parameter's value. This underscore parameter is a dynamic parameter, and its value can be changed with "alter system set "_first_spare_parameter"=<new_value>;".

Additional information is available in My Oracle Support Note 742035.1 Contention Under Auto-Tuned Undo Retention.

2.3.3.4 Recompiling Views in the Database

Recompiling views in the database is a one-time action that is required to complete the installation of CPU fixes that were initially released in January, 2008. It requires that the database be in upgrade mode, so this step is not rolling RAC installable. You may defer this step to a later downtime. If you do this, your system will continue to work; however, the installation of the January 2008 CPU fixes will not be complete until the view recompilation is completed.

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.

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.

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

  2. 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
    
  3. 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>
    
  4. Check the log file for any errors. The log file is in the current directory and is named: vcomp_<sid>_<timestamp>.log

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

2.3.4 Post Installation Instructions for Databases Created or Upgraded after Installation of PSU 10.2.0.4.4 in the Oracle Home

These instructions are for a database that is created or upgraded after the installation of PSU 10.2.0.4.4.

You must execute the steps in Section 2.3.3.2, "Loading Modified SQL Files into the Database"" and Section 2.3.3.4, "Recompiling Views in the Database" for any new database only if it was created by any of the following methods:

Upgraded databases require that you perform the steps in Section 2.3.3.4, "Recompiling Views in the Database" if these steps have not previously been performed; otherwise, no post-installation steps need to be performed.

2.4 Patch Deinstallation

These instructions are for both Non-RAC environments and RAC environments.

2.4.1 Patch Deinstallation Instructions for a Non-RAC Environment

Follow these steps:

  1. Verify that an $ORACLE_HOME/rdbms/admin/catbundle_PSU_<database SID>_ROLLBACK.sql file exists for each database associated with this ORACLE_HOME. If this is not the case, you must execute the steps in Section 2.3.3.2, "Loading Modified SQL Files into the Database" against the database before deinstalling the PSU.

  2. Shut down all instances and listeners associated with the Oracle home that you are updating. For more information, see Oracle Database Administrator's Guide.

  3. Run the OPatch utility specifying the rollback argument as follows.

    opatch rollback -id 9352164
    
  4. If there are errors, refer to Section 3, "Known Issues".

2.4.2 Post Deinstallation Instructions for a Non-RAC Environment

Follow these steps:

  1. Start all database instances running from the Oracle home. (For more information, see Oracle Database Administrator's Guide.)

  2. For each database instance running out of the ORACLE_HOME, connect to the database using SQL*Plus as SYSDBA and run the rollback script as follows:

    cd $ORACLE_HOME/rdbms/admin
    sqlplus /nolog
    SQL> CONNECT / AS SYSDBA
    SQL> STARTUP
    SQL> @catbundle_PSU_<database SID>_ROLLBACK.sql
    SQL> QUIT
    

    In a RAC environment, the name of the rollback script will have the format catbundle_PSU_<database SID PREFIX>_ROLLBACK.sql.

  3. If you set the init.ora parameter _first_spare_parameter (as explained in Section 2.3.3.3, "Optional: Configuring for Undo Retention (Bug 7291739)"), then you must clear the setting. Refer to My Oracle Support Note 742035.1 Contention Under Auto-Tuned Undo Retention.

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

2.4.3 Patch Deinstallation Instructions for a RAC Environment

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

  1. Shut down the instance on the node. (Shut down all RDBMS instances before any ASM instances.)

  2. Run the OPatch utility specifying the rollback argument as follows.

    opatch rollback -id 9352164
    

    If there are errors, refer to Section 3, "Known Issues".

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

2.4.4 Post Deinstallation Instructions for a RAC Environment

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.2, "Loading Modified SQL Files into the Database" were executed during the patch application.

All other instances can be started and accessed as usual while you are executing the deinstallation steps.

3 Known Issues

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 1061293.1 Oracle Database Patch Set Update 10.2.0.4.4 Known Issues.

Other known issues are as follows.

Issue 1   

The following ignorable errors may be encountered while running the catbundle.sql script or its rollback script:

ORA-29809: cannot drop an operator with dependent objects
ORA-29931: specified association does not exist
ORA-29830: operator does not exist
ORA-00942: table or view does not exist
ORA-00955: name is already used by an existing object
ORA-01430: column being added already exists in table
ORA-01432: public synonym to be dropped does not exist
ORA-01434: private synonym to be dropped does not exist
ORA-01435: user does not exist
ORA-01917: user or role 'XDB' does not exist
ORA-01920: user name '<user-name>' conflicts with another user or role name
ORA-01921: role name '<role name>' conflicts with another user or role name
ORA-01952: system privileges not granted to 'WKSYS'
ORA-02303: cannot drop or replace a type with type or table dependents
ORA-02443: Cannot drop constraint - nonexistent constraint
ORA-04043: object <object-name> does not exist
ORA-29832: cannot drop or replace an indextype with dependent indexes
ORA-29844: duplicate operator name specified 
ORA-14452: attempt to create, alter or drop an index on temporary table already in use
ORA-06512: at line <line number>. If this error follow any of above errors, then can be safely ignored.
ORA-01927: cannot REVOKE privileges you did not grant
Issue 2   

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.

Issue 3   

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.

4 References

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

Note 9119284.8 Bug 9119284 - 10.2.0.4.3 Patch Set Update (PSU)

5 Bugs Fixed by This Patch

This patch includes the following bug fixes.

5.1 CPU Molecules

CPU molecules in PSU 10.2.0.4.4:

PSU 10.2.0.4.4 contains all molecules previously released in PSU 10.2.0.4.3 and the following new PSU 10.2.0.4.4 molecules:

9442328 - DB-10.2.0.4-MOLECULE-039-CPUAPR2010

9442331 - DB-10.2.0.4-MOLECULE-040-CPUAPR2010

9442335 - DB-10.2.0.4-MOLECULE-041-CPUAPR2010

9442339 - DB-10.2.0.4-MOLECULE-042-CPUAPR2010

5.2 Bug Fixes

PSU 10.2.0.4.4 contains all fixes previously released in PSU 10.2.0.4.3 and the following new fixes:

4726401 - ORA-22921 OCCURS WHEN APPLYING REDO TO LOGICAL STANDBY DATAB

5085288 - ET11.1DICT: ORA-600 [13013] [5001] ON MERGE

5377242 - ORA-600 [16203] ON REFERENCE TO REMOTE SYNONYM

5399699 - LNX060717 - ORA-600 [KMGS_PARAMETER_UPDATE_TIMEOUT_1], IN M

5497338 - CLWS ORA-00600[KCBCHG1_18], RACHA STRESS TEST

5686407 - INSTANCE IS CRASHING WITH ORA-600 [17163]

5695562 - ORA-26773: INVALID DATA TYPE FOR COLUMN "MALFORMED REDO" (W

5902053 - SMON WAITING ON 'UNDO SEGMENT TX SLOT' HANGS DATABASE

5910650 - XF11.1TDE - TRC - SMBOPUT

5929055 - INTERMITTENT CRASH WITH ORA-600 [1113] PMON

6005347 - ORA-7445 [LDXITE()] [SIGBUS] [INVALID ADDRESS ALIGNMENT]

6110752 - ORA-600 [QERBUNSTRP:ERIDGT] USING PARALLEL QUERY

6145687 - BETA4:VERY STRANGE SYSTEM CHANGE NUMBER

6258480 - ORA-07445: ... CORE DUMP [LXHH2CI()+6] [SIGSEGV] [ADDRESS NO

6355586 - RAC ASM INSTANCE CRASHED. LMS FAILED WITH ORA-600 [KFCLBAST0

6445948 - ORA-600 [KDSGRP1] HAPPENING => TABLE AND INDEX ANALYZES FINE

6605106 - AN ASM NULL CONVERTED BUFFER MAY BE REFERENCED

6647480 - AFTER EXECUTED ALLOCATE EXTENT, ORA-600 [KDDUMMY_BLKCHK] OCC

6705822 - 10.2.0 FIXES OF BUG5256839 BUG5234649 BUG5552033

6720712 - DUPLICATE SUBPARTITIONS IN RANGE-LIST TABLE

6725634 - STBH: SYNONYMS ARE INVALIDATED WHEN A TABLE PARTITION IS DRO

6756739 - APPSST: 10203 GSI -INSTANCE CRASHED WITH ERROR ORA-00600: [1

6783812 - SERVER PROCESS AND SMON HANG WITH 'ENQ: SS - CONTENTION' AND

6786022 - ADDING AND DROPPING EXISTING REDOLOG GROUPS IN RAC MAY CAUSE

6824129 - ORA-7445 [KQLVLD()+17135] WHILE STREAMS DATAPUMP OPERATION

6825866 - WRONG RESULT WITH TABLE() - REGRESSION

6852598 - ORA-7445 [KGH***] INSTANCE INSTABILITY

6971433 - ORA-600 [KTREXC_1] OCCURRED DURING MERGE INTO

6981690 - CURSOR NOT SHARED WHEN RUNNING PX QUERY ON MOUNTED RAC SYSTE

7022234 - XF11.2CLOAD - TRC - MSQSUB

7028176 - DIAG DETECTED ORA-600[17147], [OSDEP_INTERNAL], AND [KJZCCLN

7127618 - CPU AT 100%, SESSION MARKED AS KILLED STAYS FOREVER KILLED T

7210921 - STATISTICS WITH SUBPARTITIONS ARE NOT CORRECTLY INTERPRETED

7225204 - ORA-600 [KTRGCM_3] IN 4 NODE RAC INSTANCE

7291739 - CONTENTION UNDER AUTO-TUNED UNDO RETENTION

7299153 - RAC DATABASE AND ASM HANG

7306915 - ORA-4031 / KGL HANDLES MEMORY LEAK OF MVOBIND / MVOBTBL FROM

7329252 - ORA-8102 DURING REBUILD INDEX ONLINE WHEN CONCURRENT W/ UPD

7393292 - PSRC: FIX FOR BUG 5590163 PREVENTS CONDITIONAL DEQUEUE FROM

7535152 - ORA-07445 [KSXPUNMAP] ERRORS IN RAC

7587008 - STBH: UNABLE TO EVICT A HUNGING RAC INSTANCE FROM CLUSTER

7589862 - DISKGROUP MOUNT FAILS WITH ORA-600 KFCCHKAIO01 AND ORA-15196

7610362 - TB: PERFORMANCE: 3-5 SECOND LONG WAITS FOR LOG FILE SYNC

7639602 - HIGH SESSION ALLOCATION LATCH AND RECURSIVE CALLS FOR A JOB

7801939 - AQ HIGH WAITS FOR "CHANNEL OPERATIONS PARENT LATCH" CHILD LA

8220734 - LOG FILE SYNC 1 OR 2 OR 3 SEC TIMEOUT, MISSING THE POST

8354686 - ORA-600 [KSS_GET_TYPE: NULL SO] IN PRIMARY DATABASE

8431487 - INSTANCE CRASH ORA-07445 [KGGHSTFEL()+192] ORA-07445[KGGHSTM

8479537 - WRONG DATA INSERTED WHEN WHEN CURSORS GETS FREQUENTLY FLUSH

8481935 - RFS TRACE FILE GENERATES THE SAME TRACE INFORMATION EVERY CO

8490879 - LOG FILE SYNC LATENCIES

8556586 - ORA-600 QSMEMDNF_MODIFIED_DNF REPORTED ON ALERT.LOG

8815639 - [11GR2-LNX-090813] MULTIPLE INSERT CAUSE DATA ALLOCATION ABO

8866013 - ORA-00060 WHEN DMON STARTS DURING STANDBY CREATE FROM GRID C

9119194 - PSRC: DISTRIBUTED QUERY SLOWER IN 10.2.0.4 COMPARED TO 10.2.

9377578 - MV REFRESH FAILS WITH ORA-07445: [SRSCWD()+80] [SIGFPE] [INT

6 Documentation Accessibility

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.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/support/contact.html or visit http://www.oracle.com/accessibility/support.html if you are hearing impaired.


Patch 9352164 - 10.2.0.4.4 Patch Set Update Release 10.2.0.4.4 for UNIX

Copyright © 2006, 2010, 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.