# 
#  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
# 
#  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. 
# 
#-------------------------------------------------------------------------
#  Interim Patch for Base Bugs: 5606601
#-------------------------------------------------------------------------
#
#  DATE:  Wed Oct 18 13:30:20 2006
#  -------------------------------
#  Platform Patch for : Solaris 64-bit(23) 
#  Product Version #  : 9.2.0.8.0
#  Product Patched    : RDBMS
#
#  Bugs Fixed by this patch:
#  -------------------------
#  5606601:WRONG PERMISSIONS FILES AFTER PATCHSET 9.2.0.8 HAS BEEN APPLIED
#
#  Patch Installation Instructions:
#  --------------------------------
#  To apply the patch, unzip the PSE container file:
#
#  p5606601_9208_SOLARIS64.zip
#
#  Set your current directory to the directory where the patch
#  is located:
#
#    % cd 5606601
#
#  Ensure that the directory containing the opatch script appears in
#  your $PATH; then enter the following command:
#
#    % opatch apply
#
#  Patch Special Instructions:
#  ---------------------------
#
#  After opatch applies the patch, please do the following manually :
#
#  1.  cd $ORACLE_HOME/install
#  2.  Run changePerm.sh script.
#
#  After applying the 9.2.0.8 patchset to an Oracle Database or Oracle Database 
#  Client installation, permissions on some directories and files in the Oracle 
#  Home changed.  This is because the default umask used by the installation
#  in 9.2.0.8 changed to 007, causing any new file or directory, or any file
#  or directory that was regenerated as part of the patchset installation to 
#  have more restrictive permissions than it had originally.
#  
#  Specifically, there are a small number of files for which read, write, and 
#  execute permissions for "others" has been removed.  This effectively prevents
#  client-side utilities such as sqlplus from being invoked from the home by 
#  users who do not have user or group-level access to the files in the Oracle
#  home. 
#  
#  This script will relax the permissions on the handful of files and
#  directories in the installed Oracle Home to restore back read and execute
#  permissions for "others".  Some of the directories and files (like log, 
#  trace, etc.,) will still have restricted access.  Note that this script
#  should be run only after considering the security ramifications of relaxing
#  permissions on files in the Oracle Home so that "others" can execute 
#  client-side utilities in the home.
#
#  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 problems installing this PSE or are not sure
#  about inventory setup please call Oracle support.
