Oracle Critical Patch Update Jan-06

Oracle Critical Patch Update January 2006
Release Notes for Oracle Database Server Version 8.1.7.4
Release Date: Jan 17th, 2006

Note: You are required to read the Advisory and Pre-installation notes for Critical Patch Update - January 2006 before you proceed.

CONTENTS

Introduction
Requirements
Bugs Fixed by this patch
Patch Installation Instructions
Patch Deinstallation Instructions

Introduction

Database Server Patch for Oracle Critical Patch Update January 2006 is a bundle patch for components in the data server and client.

This patch should be applied to the Oracle home for the Database.

This document guides your through the Installation, Post Installation Actions and optionally, De-Installation steps required for Oracle Critical Patch Update January 2006 Database Server Patch. Failure to carefully read and understand these steps may result in your applying a patch that can cause your Oracle Installation to malfunction, including interruption of service and/or loss of data.

If you do not meet all of the following requirements, please log an iTAR, so that an Oracle support analyst may review your situation. The Oracle analyst will help you determine if this patch is suitable for you to apply to your system. We recommend that you avoid applying any temporary patch unless directed by an Oracle Support Analyst who has reviewed your system and determined that it is applicable.

Requirements

Your system configuration (Oracle Server version and patch level, OS Version) must exactly match those listed below.

Patch for Base Bug:    4751906
Patch for Platforms:   Sun SPARC SOLARIS, Linux, HP-UX, HP Tru64, AIX
Product Version:        8.1.7.4
Product Patched:        Database

Components Patched: Database, Client, Oracle Http Server, MODPLSQL, OID, SSO

Bugs Fixed by this patch

4754820 - SECURITY BUGS FIXED IN CPUJAN2006

4567933 - SECURITY BUGS FIXED IN CPUJan2006

4392451 - SECURITY BUGS FIXED IN CPUJUL2005

4199417 - SECURITY BUGS FIXED IN CPUAPR2005

4057713 - SECURITY BUGS FIXED IN CPUJAN2005

3828166 - SECURITY BUGS FIXED IN ALERT 68

3398060 - JAVASSL DIF RDBMS_MAIN_SOLARIS_040110

2109825 - INCORRECT CARDINALITY ESTIMATE WITH OR PREDICATES AND NULL VALUES

2630054 - ORA-03113 & ORA-7445 [EVAOPN2()+692] [SIGSEGV]

2048231 - FETCH PERFORMANCE DOWN IN MULTITHREAD APPLICATION

2285638 - SUB-QUERY WITH COLUMN OF OUTER TABLE FAILS WITH ORA-00600 [15160]

4568330 - MLR ON TOP OF 8174 FOR CPUJUL_MERGE

2884469 - FXD : APPS_SQL : ORA-00600 [729] [SPACE LEAK]

2225569 - ORA-600 [KOKBNP2] EXECUTING PACKAGE WITH NESTED CURSOR AS GRANTED USER

2259466 - MULTIPLE ASSIGNMENT OF VARRAY FAILS WITH ORA-6533

2307892 - CBO : POOR EXECUTION WITH LARGE IN-LISTS

2316487 - ORA-604 AND ORA-942 WITH STAR_TRANSFORMATION_ENABLED

2430113 - WRONG VALUES WITH STAR_TRANSFORMATION AND _B_TREE_BITMAP_PLANS

2456761 - FUNCTION NOT RE-EVALUATED FOR SQL MATCHING

2286794 - STAR TRANSFORMATION CAUSING ORA-600[EVAOPN2]

2305613 - ORA-3113 ORA-7445: [11] WITH KKODISLIKE WHEN EXECUTING A COMPLEX QUERY

3889519 - UPLOAD IN SSL DOES NOT WORK WITH IE AFTER SECALERT 68 OR DB PATCH 9015
2363247 - UNNECESSARY BITMAP PATH GENERATION AND BITMAP MEM ALLOCATION
2379325 - WRONG COST CALCULATED AT KPRCDT
2410612 - CONVENTIONAL EXPORT HAS WRONG DATA ON IMPORT
2528524 - CLEAR TEXT PASSWORDS IN TRACE FILE
2598387 - WRONG DATA ON IMPORT AFTER EXPORT VIA CONVENTIONAL PATH
2643579 - ORA-7445 [10] CURSOR_SHARING=FORCE KXSPOAC
2337115 - INTERRUPTEDEXCEPTION NO HANDLED PROPERLY BY JAVASSL
1811914 - RDBMS BAD RECOVERY, LOST DATA IF CRASH DURING ALTER TABLESPACE...READ ONLY
2073948 - ORA-6550 IN ANONYMOUS PL/SQL AFTER DROPPING TWO PARTITIONS IN A REMOTE TABLE
2238718 - RMAN BACKUP TO DISK HANGS, WAITING FOR CHANNEL TO FINISH (IOCTL)
2268284 - ORA-12842 SCHEMA MODIFIED DURING PARALLEL EXECUTION
2271499 - ORA-1115,ORA-27063: CKPT CRASHED INSTANCE WHEN NON SYSTEM DATAFILES UNAVAILABLE.
2346568 - DBMS_LOB.COMPARE HAS ORA600 AFTER CSCONV
2386334 - ORA-7445[QERUAROWPROCEDURE] SELECT FROM VIEW WITH UNION ALL
2401670 - ORA-1002 AFTER ROLLBACK-TO-SAVEPOINT IN PRO*C OR OCI APPLICATION
2450264 - SIGSEGV, ORA-7445 [KOKMEOC()+48], THEN ORA-4031 AND MANY ORA-600'S
2486714 - PATCH SET 8174 CHANGE THE PLAN FROM NESTED LOOP TO HASH JOIN.
2660592 - EXCESSIVE PARSE WHEN EXECUTING QUERIES THE FIRST TIME
2663395 - ACCESS ACROSS LOCAL VARIABLE BOUNDARY IN KCFRMC()
2664217 - APPST9202 HR FAMILY PACK CAUSES PACKAGE LOCKING
2791662 - ENTIRE INSTANCE SOMETIMES EXTREMELY SLOWS DOWN
0917604 - DB CRASHES WHEN INIT.ORA ORACLE_TRACE_COLLECTION_SIZE IS REACHED
2128784 - TNS 12537 FROM DISPATCHER ON HPUX 8.1.7 WITH FAILOVER MODE SETUP IN TNSNAMES
2198861 - TRYING TO DROP TRANSPORTABLE TABLESPACE GIVES ORA-600[KTFBFGET-1]
2225569 - ORA-600 [KOKBNP2] EXECUTING PACKAGE WITH NESTED CURSOR AS GRANTED USER
2228280 - CUSTOMER RECEIVING A NUMBER OF ORA-7445 ORA-600 ERROR
2288481 - SELECT DATA FROM A PARTITIONED TABLE CAUSES COREDUMP, ORA-600[15212] OR ORA-7445
2293786 - TST1159.9 "SUBSTRB" GIVES INCORRECT WITH UTF8 IN PLSQL
2324795 - PERFORMANCE OF DICTIONARY VIEW DBA_SEGMENTS IS UNACCEPTABLE
2405244 - SIGSEGV, ORA-7445, CORE DUMP WHILE RMAN REPORTING RE-READ OF CORRUPTED BLOCK
2444568 - ORA-600 [2886] [2] [1] IN DBWR, INSTANCE CRASH IF FGND DIES IN ALTER...RDONLY
2479110 - SELF DEADLOCK WAITING ON "LIBRARY CACHE PIN" ON AUTO RECOMPILATION OF PLSQL
2556845 - ORA-14452 ON EXPORT TABLESPACES IN PARALLEL
2580648 - MISSES IN LIBRARY CACHE FOR RECURRENT CALLS TO PL/SQL PROCEDURE
2594253 - SSL HANDSHAKE FAILURE IN 8.1.7.4
2656881 - SESSION EVENT REQUIRED TO DISABLE THE CLOB VARYING WIDTH FIX IN BUG 2133357
2767834 - EXP OF META DATA FOR TRANSPORTABLE TABLESPACES IS SLOW FOR MORE DATAFILES
2905667 - INSTANCE IS TERMINATED BY CKPT/LGWR DUE TO ORA-1110 DURING SHUTDOWN.
2986643 - CHILD CURSORS ARE NOT CACHED WHEN EXECUTING SQL WITH DB LINK AND SQL_TRACE=TRUE
3019460 - DBWR REPEATEDLY OPEN/CLOSES THE DATAFILES
3212916 - IP GETINPUTSTREAM ERRORS WITH "READ ERROR IN STREAM READ"
3315378 - BLOCKED INDEX ONLINE REBUILD HANGS OTHER SESSIONS
3197147 - JVM CRASHES ON AN E-BIZ 11.5.9 ENVIRONMENT CONFIGURED TO USE SSL

Patch Installation Instructions

Please review the ‘Known Issues’ section in the Pre-installation notes for Critical Patch Update - January 2006 before proceeding with the patch installation.
(Note 343384.1:Oracle CPUJan2006 Pre-Installation for Oracle Database Server)

Make sure that all processes, running out of the ORACLE_HOME being patched, are cleanly shutdown before installing this patch.

1) Please ensure that ORACLE_HOME is set.

2) Please ensure that $ORACLE_HOME/bin is included in your PATH environment variable,

and also ensure that the following executables must be present in the $PATH: make, jar, ar, ld, and nm.

3) Set JDK_HOME to the JDK directory (JDK 1.3.1 or above)

For example, if you have JDK version 1.3.1 installed under /usr/local/packages/jdk directory, then set JDK_HOME to /usr/local/packages/jdk

4) Set ORAINST to the location of the oraInst.loc file only if the OUI inventory has been moved from the default location.

For example, if you have moved the inventory to /tmp directory,

then set ORAINST to /tmp/oraInst.loc

If ORAINST is not set, then the default location for that platform is used. The default location on Solaris 32 is /var/opt/oracle/oraInst.loc

To apply the patch, set your current directory to the directory where the patch is located and then run the installcpu.sh script by entering the following Unix command:

sh installcpu.sh

Please inspect the following install log file for any errors:

installcpu.sh log file $ORACLE_HOME/cpu/CPUJan2006/install<timestamp>.log

If you have encountered any errors, please refer to the ‘Known Issues’ section in the Pre-installation notes for Critical Patch Update - January 2006

Run the cpu_root.sh as user root by entering the following Unix command:

sh cpu_root.sh

Post Installation Instructions

For all platforms except HP-UX PA-RISC (64-bit) install, please inspect $ORACLE_HOME/Apache/Apache/conf/httpd.conf file to see if the following line exists -

LoadModule perl_module libexec/libperl.so

If the file does not contain the above line, please add it to the “Dynamic Shared Object ( DSO ) Support Section” in httpd.conf file.

For Linux install only, inspect $ORACLE_HOME/Apache/Apache/conf/httpd.conf and $ORACLE_HOME/Apache/Apache/bin/apachectl files to see if PERL5LIB variable includes the following line:

<ORACLE_HOME>/Apache/perl/lib/5.00503:<ORACLE_HOME>/Apache/perl/lib/5.00503/i686-linux-thread:<ORACLE_HOME>/Apache/perl/lib/site_perl/5.005:<ORACLE_HOME>/Apache/perl/lib/site_perl/5.005/i686-linux-thread

If PERL5LIB does not contain the above line from httpd.conf and apachectl files, please back up the files and include the above line into the existing PERL5LIB variable.

Start up all database instances running out of the ORACLE_HOME being patched.

For each database instance running out of the ORACLE_HOME being patched,
connect to the database using Sqlplus as sysdba and run catcpu.sql as follows –

Note: Before running catcpu.sql or catcpu_rollback.sql,
execute 'set serveroutput on;' in sqlplus. If you get the following error:

SP2-0614: Server version too low for this feature

you must log off the session and log back on before running catcpu.sql
or catcpu_rollback.sql.

sqlplus /nolog

sqlplus> connect / as sysdba

sqlplus> STARTUP

sqlplus> ALTER SYSTEM ENABLE RESTRICTED SESSION;

sqlplus> @catcpu.sql

sqlplus> ALTER SYSTEM DISABLE RESTRICTED SESSION;

Inspect the logfile for any errors. If you have encountered any errors, please refer to the ‘Known Issues’ section in the Pre-installation notes for Critical Patch Update - January 2006

If catcpu.sql reports any Invalid Objects, Oracle recommends that you compile the invalid objects using the following;

(Please note that for large numbers of objects, this compilation step can take some time.)

cd $ORACLE_HOME/rdbms/admin

sqlplus /nolog

sqlplus> connect / as sysdba

sqlplus> @utlrp.sql

You can check for any invalid objects by executing following statement;

sqlplus> select OBJECT_NAME from DBA_OBJECTS where status = 'INVALID';

Patch De-installation Instructions

Make sure that all processes, running out of the ORACLE_HOME being patched, are cleanly shutdown before de-installing this patch.

Please ensure that ORACLE_HOME, JDK_HOME, PATH and ORAINST environment variables are set as described in the Patch Installation Instructions.

To deinstall the patch, if there are errors or other problem with this patch, set your current directory to the directory where patch is located and run rollbackcpu.sh shell script by entering the following Unix command:

sh rollbackcpu.sh

Please inspect the following rollback log file for any errors:

rollbackcpu.sh log file $ORACLE_HOME/cpu/CPUJan2006/rollback<timestamp>.log

If you have encountered any errors, please refer to the ‘Known Issues’ section in the Pre-installation notes for Critical Patch Update - January 2006

After the patch has been deinstalled successfully, please set your current directory to the directory where the patch is located and then run the cpu_root.sh as user root by entering the following Unix command:

sh cpu_root.sh

If you relinked any Non-Oracle Applications manually after installing this patch with installcpu.sh then you should relink those as well after the undo script has finished.

Post Deinstallation Instructions

Restore the files $ORACLE_HOME/Apache/Apache/conf/httpd.conf and $ORACLE_HOME/Apache/Apache/bin/apachectl from backup if you had modified these as part of post installation actions.

sqlplus /nolog

sqlplus> connect / as sysdba

sqlplus> STARTUP

sqlplus> ALTER SYSTEM ENABLE RESTRICTED SESSION;

sqlplus> @catcpu_rollback.sql

sqlplus> ALTER SYSTEM DISABLE RESTRICTED SESSION;

Inspect the logfile for any errors. If you have encountered any errors, please refer to the ‘Known Issues’ section in the Pre-installation notes for Critical Patch Update - January 2006

If catcpu_rollback.sql reports any Invalid Objects, Oracle recommends that you compile the invalid objects using the following;

(Please note that for large numbers of objects, this compilation step can take some time.)

cd $ORACLE_HOME/rdbms/admin

sqlplus /nolog

sqlplus> connect / as sysdba

sqlplus> @utlrp.sql

You can check for any invalid objects by executing following statement;

sqlplus> select OBJECT_NAME from DBA_OBJECTS where status = 'INVALID';