#
#  WARNING: Failure to carefully read and understand these requirements may
#  result in your applying a patch that can cause your Oracle Server 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: 
#  
#    - You must have located this patch via a Bug Database entry
#      and have the exact symptoms described in the bug entry. 
#  
#    - Your system configuration (Oracle Server version and patch
#      level, OS Version) must exactly match those in the bug
#      database entry - You must have NO OTHER PATCHES installed on
#      your Oracle Server since the latest patch set (or base release
#      x.y.z if you have no patch sets installed).
#
#    - [Oracle 9.2.0.2 & above] You must have Perl 5.00503 (or later)
#      installed under the ORACLE_HOME, or elsewhere within the host
#      environment. OPatch is no longer included in patches as of 9.2.0.2.
#      Refer to the following link for details on Perl and OPatch:
#      http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=189489.1
# 
#    - [IBM AIX O/S & Java patches for Oracle 9.2] 
#      In order to apply java class updates to IBM AIX based systems using 
#      java_131, you must update your java if you are running a version prior 
#      to Service Refresh build date 20030630a. This is 
#      necessary to fix IBM Defect#60472. 
# 
#      To identify which java build date you are on, enter the following 
#      command ; 
# 
#      > $ORACLE_HOME/jdk/bin/java -fullversion 
#      ... example response ... 
#      java full version "J2RE 1.3.1 IBM AIX build ca131-20030630a" 
# 
#      The string ends in the date format YYYYMMDD or YYYYMMDDa where 'a' 
#      indicates an updated release to the original build. You should always 
#      apply the latest AIX Java SDK 1.3.1  Service Update available from IBM. 
#      As a minimum, the above service refresh can be found under 
#      APAR IY47055. The signature for the updated JVM is ca131-20030630a. 
#      Information on the latest available fixes, as well as how to apply 
#      the APARs to your AIX systems, is available at the IBM Java site.
# 
#      If you are running AIX 5L, you can safely ignore any comment against
#      the APAR that says (AIXV43 only). The APAR is applicable to 
#      both AIX 4.3 and AIX 5L. 
# 
#      Once you have updated your java installation you need to copy these 
#      updated files to Oracle's copies in $ORACLE_HOME/jdk. 
#      As the Oracle owner, simply issue the following commands; 
# 
#      > cd /usr/java131 
#      > cp -fpR * $ORACLE_HOME/jdk 
#
#
#  If you do NOT meet these requirements, or are not certain that you meet
#  these requirements, please log an iTAR requesting assistance with this
#  patch and Support will make a determination about whether you should
#  apply this patch. 
#
#
#  OPatch Information
#  ------------------
#
#  For further details regarding OPatch, see Metalink article Doc ID:
#  293369.1 OPatch Documentation.
#
#  Prior to the Install Phase, following checks are performed:
#
#    - Conflicts with other patches
#
#    - Conflicts with subset patches (existing patch is a subset of the patch
#      being installed)
#
#  If a conflict is found, please abort the install and contact Oracle
#  Support Services.
#
#  If a subset is found, please continue the install, as all fixes for the
#  subset patch are included in the patch being installed.  The subset
#  patch(s) will be automatically rolled back prior to the installation of
#  the new patch.
#
#  It is strongly recommended that you use OPatch version 1.0.0.0.60 or above.
#  If your OPatch version does not satisfy this requirement, the latest version
#  10.1.0.0.0 (Bug 6880880) can be downloaded from My Oracle Support
#  (formerly Metalink). Please follow the instructions to install OPatch. The
#  OPatch scripts should be copied to $ORACLE_HOME/OPatch directory.
#  Note: This is only a one time task unless new OPatch version is made
#  available.
#
#  Additionally, if the Oracle inventory is not setup correctly this utility
#  will fail. To check accessibility to the inventory you can use the command:
#
#     % opatch lsinventory
#
#  If you have any problem installing this patch or are not sure about the
#  inventory setup, please call Oracle support.
#
#-------------------------------------------------------------------------
#  Interim Patch for Base Bugs: 8467564
#-------------------------------------------------------------------------
#
#  DATE:  Wed May 20 05:11:36 2009
#  -------------------------------
#  Platform Patch for : Linux-x86
#  Product Version #  : 11.1.0.7.0
#  Product Patched    : ORCL_PF
#
#  Bugs Fixed by this patch:
#  -------------------------
#  8467564: DRCP - ORA-56600 WHEN OCI STATEMENT CACHE SIZE EXCEEDED
#
#  Patch Installation Instructions:
#  --------------------------------
#  Make sure that all instances running under the ORACLE_HOME being patched
#  are cleanly shutdown before installing this patch. Also ensure that
#  the tool used to terminate the instance(s) has exited cleanly.
#
#  1. To apply the patch, unzip the PSE container file:
#  p8467564_111070_Linux-x86.zip
#
#  2. PreInstall steps:
#
#  3. Set your current directory to the directory where the patch
#  is located:
#
#     % cd 8467564
#
#
#     Ensure that the directory containing the opatch script appears in
#     your $PATH; then enter the following command:
#
#     % opatch apply
#
#
#  4. PostInstall Steps:
#
#
#  Patch Deinstallation Instructions:
#  ----------------------------------
#  Use the following command:
#
#    % cd 8467564
#    % opatch rollback -id 8467564
#
