Table 1 Installation Types and Security Content

2.1 OPatch Utility

You must use the OPatch utility version 11.2.0.3.6 or later to apply this patch. Oracle recommends that you use the latest released OPatch version for 11.2, which is available for download from My Oracle Support patch 6880880 by selecting the 11.2.0.0.0 release.

For information about OPatch documentation, including any known issues, see My Oracle Support Document 293369.1 OPatch documentation list.

3.1 Patch Pre-Installation Instructions

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

• Section 3.1.1, "Applying Database PSU Along Side the Oracle JavaVM Component 11.2.0.4.1 Database PSU Patch"

• Section 3.1.2, "Environments with Grid Infrastructure (GI)"

• Section 3.1.3, "Environment Checks"

• Section 3.1.4, "One-off Patch Conflict Detection and Resolution"

3.2 Patch Installation Instructions

Conflicting patches should be rolled back before applying the patch, otherwise opatch apply will report conflicts again.

Follow these steps:

1. If you are using a Data Guard Physical Standby database, you must install this patch on both the primary database and the physical standby database, as described by My Oracle Support Document 278641.1.

2. If this is an Oracle RAC environment, install the PSU patch using the OPatch rolling (no downtime) installation method as the PSU patch is rolling Oracle RAC installable. Refer to My Oracle Support Document 244241.1 Rolling Patch - OPatch Support for RAC.

3. If this is not a Oracle RAC environment, shut down all instances and listeners associated with the Oracle home that you are updating. For more information, see Oracle Database Administrator's Guide.

4. Rollback any patches found during the One-off Patch Conflict Detection.

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 p19121551_112040_<platform>.zip
   
   cd 19121551
   
   opatch apply
   

6. Install all resolutions to conflicts found during the One-off Patch Conflict Detection.

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

3.3 Patch Post-Installation Instructions

After installing the patch, perform the following actions:

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

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

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

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

4.1 Patch Deinstallation Instructions for a Non Oracle RAC Environment

Follow these steps:

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

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

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

   opatch rollback -id 19121551
   

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

4.2 Patch Post-Deinstallation Instructions for a Non Oracle 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 an Oracle RAC environment, the name of the rollback script will have the format catbundle_PSU_<database SID PREFIX>_ROLLBACK.sql.

3. Check the log file for any errors. The log file is found in $ORACLE_BASE/cfgtoollogs/catbundle and is named catbundle_PSU_<database SID>_ROLLBACK_<TIMESTAMP>.log where TIMESTAMP is of the form YYYYMMMDD_HH_MM_SS. If there are errors, refer to Section 5, "Known Issues".

4.3 Patch Deinstallation Instructions for an Oracle RAC Environment

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

1. Shut down the instance on the node.

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

   opatch rollback -id 19121551
   

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

3. Start the instance on the node as follows:

   srvctl start instance –d <db-unique-name> -n <nodename>
   

4.4 Patch Post-Deinstallation Instructions for an Oracle RAC Environment

Follow the instructions listed in Section Section 4.2, "Patch Post-Deinstallation Instructions for a Non Oracle RAC Environment" only on the node for which the steps in Section 3.3.2, "Loading Modified SQL Files into the Database" were executed during the patch application.

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

7.1 CPU Molecules

CPU molecules in PSU 11.2.0.4.4:

PSU 11.2.0.4.4 contains the following new PSU 11.2.0.4.4 molecules:

7.2 Bug Fixes

See My Oracle Support Document 1611785.1 that documents all the non-security bugs fixed in each 11.2.0.4 Patch Set Update (PSU).

PSU 11.2.0.4.4 contains the following new fixes:

Advance Queuing

   14764829 - ORA-600 [KWQICGPC:CURSTA] WHEN USING AQ

Automatic Storage Management

   13955826 - ORA-15133 AND ORA-600 [KFGFINALIZE_2] IN ASM

Buffer Cache Management

   12747740 - NODE JOIN RECONFIGURATION (PCMREPLAY) DOES NOT SCALE WITH MORE LMS'S

   16494615 -  READ BY OTHER SESSION WAITS ON UNDO BLOCK

   17390160 - KCBL STATE OBJECT SEARCH CAN CAUSE CPU REGRESSION

   17586955 - ORA-600 [KTSPFMDB:OBJDCHK_KCBNEW_3]

   17951233 - ORA-600 [KCBLIN_3] [103] AFTER SETTING _PGA_MAX_SIZE AT 4G

Enterprise Manager

   18673304 - Fix for bug 18673304

   18673325 - Fix for bug 18673325

   18673342 - Fix for bug 18673342

   19211724 - Fix for bug 19211724

Generic

   9756271 - SOME SQL STATEMENTS INVOLVING CONNECT BY OR RECURSIVE WITH MAY CAUSE SEGV

   14245531 - LARGE AMOUNT OF TEMP SPACE IS USED DURING IAS LOADING

   16042673 - DATABASE HANG WHEN SYSTEM TRYING TO ADD INTERVAL PARTITION TO THE TABLE

   17037130 - EXADATA: ORA-4031 WITH HUGE ALLOCATION IN PRTMV

   17040527 - ALTER STORAGE (BUFFER_POOL KEEP) DOESN'T WORK UNTIL FLUSH LIBRARY CACHE

   17242746 - ORA-4025 ON RECURSIVE SQL FROM PLSQL

   17267114 - INVALID DATA IN SYS.TYPE$ WAS CAUSING DBMS_PICKLER.GET_METADATA ROUTINE TO FAIL

   17449815 - ORA-8102 ORA-1499 AFTER ORA-1/ORA-2291 BY MERGE WITH DML ERROR LOGGING

   17570240 - >6% REGRESSION SEEN IN PROFILE FROM NEW KPOSPFDRV OF WHICH 50% FROM SPRINTF

   17587063 - ORA-600 [QERGHFETCH:INC] REPORTED ON QUERY WITH CURSOR_SHARING=FORCE

   17705023 - ORA-600 [KKZUASID] ON MV REFRESH

   17824637 - ORA-1403 AFTER SESSION CONTEXT CHANGE

   17842825 - ORA-600 [KQRFRPO] AND INSTANCE CRASH

   17891946 - RCA: INSTANCE CRASH BY USER PROCESS

   17982555 - ORA-4020: DEADLOCK DETECTED WHILE TRYING TO LOCK OBJECT FUSION.SYS_PLSQ

   18199537 - "CHILD ROW CACHE OBJECTS" LATCH CONTENTION AND CONNECTING DB HANG

   18230522 - CORE DUMP WITH REFERENCE PARTITIONED OBJECTS AND FULL PARTITION-WISE JOIN

   18436307 - TRIGGER 'WHEN CONDITION' RETURNING FALSE WHEN TABLE HAS A SECURITY DBA_POLICY

   18973907 - NEW REMOTE RPC FOR NULL INDEX STATS HAS BEEN REMOVED

   19458377 - CHECKS TO ENSURE COMPATIBILITY OF BUNDLES WITH JOX CHANGES

   19554106 - CONFLICT RESOLVING FIX FOR BUNDLES FOR JOX CHANGES

High Availability

   14285317 - RMAN DUPLICATE FAILS ORA-01507 IF SOURCE HAS ARCHIVELOG MODE AND COLD BACKUP

   16692232 - RMAN BACKUP ARCHIVELOG ALL NOT BACKED UP DELETE ALL INPUT DOESNOT WORK AS EXPECT

   17006183 - ARCHIVER CONFUSES DESTINATIONS FOR EOR ARCHIVELOG UPON ROLECHANGE TO PRIMARY

   17232014 - INITIAL ALLOCATION FOR KJBR&KJBL ARE TOO LOW W/ LARGE CACHES DUE TO UB4 OVERFLOW

   17237521 - DELAY IN ARC0 STARTING UP

   18009564 - RMAN IS SENDING WRONG INFORMATION TO MML, THUS MML IS FAILING

   18280813 - INSERT /*+ APPEND */ STUCK IN GC CURRENT REQUEST

JavaVM

   19289642 - Fix for bug 19289642

Oracle Multimedia

   18262334 - PROCESSCOPY TO JPEG IMAGE FAILED FOR INDEX COLOR IMAGE

Oracle Security

   16524926 - APEX: ORA-1031 WITH ORACLE MULTIMEDIA AND REALM PROTECTED DB SCHEMA

   18264060 - AUDIT_TRAIL=*,EXTENDED DOES NOT WRITE BIND CORRECTLY WITH 16817814 FIX

Oracle Space Management

   14829250 - ET12.1TXN: ORA-7445 [KTBDBH] ON A MERGE TABLE

Oracle Transaction Management

   11733603 - ORA-54 WITH SELECT STATEMENT USING NOWAIT CLAUSE WITH NO CONCURRENT ACTIVE TX

   17787259 - TURNING MINACTSCN DUMP OFF SHOULD BE POSSIBLE

Oracle Utilities

   17036973 - CRASH IN CLUSTER_SET

Oracle Virtual Operating System Services

   14657740 - ORA-600 [510] [0X2E4781268] [CACHE BUFFERS CHAINS]

   17299889 - XDB QUERIES ARE SLOW DUE TO TIME SPENT IN KGHFREMPTY

   18191164 - PERFORMANCE ISSUE SEEN WITH DIRECT NFS DUE TO SPIN IN RECONNECT CODE PATH

   18328509 - ORA-4030 AFTER UPGRADE TO 11.2.0.4 WITH SHARED SERVER AND JDBC THIN CLIENT

PL/SQL

   18641419 - Fix for bug 18641419

Patch Automation

   17343514 - REMOVE JAVA FROM CATBUNDLE

   19727057 - HANDLE JVMPSU.SQL IN CATBUNDLE

Server Manageability

   14084247 - STBH: ORA-1555 DUE TO WRH$_ACTIVE_SESSION_HISTORY NOT PURGED

   17042658 - ORA-600 [KEWRSP_SPLIT_PARTITION_2] ON UPGRADE FROM 11.2 TO 12.1

XML Database

   16198143 - WHILE USING DATA REDACTION  THERE ARE CHANGES FOR A CRASH  IN QMXSAXCREATEDOCTYP