# 
#  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 bug : 4642651
#-------------------------------------------------------------------------
#  DATE:  October 21st 2005
#  -----------------------
#  Platform Patch for : Linux x86
#  Product Version #  : 10.2.0.1
#  Product Patched    : CRS/RDBMS
#
#  Bugs Fixed by this patch:
#  -------------------------
#  4642651:CSS DOES NOT ALWAYS RESOLVE SPLIT BRAINS WHEN HEAVY LOAD OR LONG I/O
#
#  Patch Installation Instructions:
#  --------------------------------
#  Make sure 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.
#
#  Ensure that the directory containing the opatch script appears in
#  your $PATH. Execute "which opatch" to confirm.
#
#  Configuration A:   With a shared CRS Home, a full cluster outage must 
#  be planned. The patch will update the shared copy of the binaries, 
#  and no daemons can be online while the binaries are modified.
#
#  Configuration B:   When each node of the cluster has its own CRS Home, 
#  the patch should be applied as a rolling upgrade. All of the following 
#  steps should be followed for each node. Do not patch two nodes at once.
#  
###########################################################################
#
#  0. Set your ORACLE_HOME environment variable to point to the CRS Home.
#
###########################################################################
#
#  1. Verify that the Oracle Inventory is properly configured.
#
#  % opatch lsinventory -detail
#
#  This should list the components the list of nodes.
#
###########################################################################
#
#  2. Unzip the PSE container file
#
#  % unzip p4642651_10201_LINUX.zip
#
###########################################################################
#
#  3. Set your current directory to the directory where the patch
#  is located, and ensure that the packaged scripts are executable.
#
#  % cd 4642651
#  % chmod +x custom/scripts/*.sh
#
###########################################################################
#
#  4. Shut down all RDBMS and ASM instances dependent on the CRS daemons
#     being shut down in step 5. 
#
###########################################################################
#
#  5. In configuration A, shut down the CRS daemons on all nodes.
#     In configuration B, shut down the CRS daemons on the local node.
#
#     As root, issue the following command to stop the CRS daemons.
#     Linux#  /etc/init.d/init.crs stop
#     SunOS#  /etc/init.d/init.crs stop
#     AIX#    /etc/init.crs stop
#     HP-UX#  /sbin/init.d/init.crs stop
#     OSF1#   /sbin/init.d/init.crs stop
#
###########################################################################
#
#  6.  Prior to applying this part of the fix, you must invoke this script
#  as root to unlock protected files.
#  
#  Specify the fully qualified path for the CRS Home.
#
#  <username> is the software installer/owner for the CRS Home.
#
#  # custom/scripts/prerootpatch.sh -crshome <CRS Home> -crsuser <username>
#
#  Note: In configuration A, invoke this only on one node.
#
###########################################################################
#
#  7. Now invoke an additional script as the software installer/owner. This
#  script will save important configuration settings.
#
#  % custom/scripts/prepatch.sh -crshome <CRS Home path>
#
#  Note: In configuration A, invoke this only on one node.
#
###########################################################################
#
#  8a. Patch the CRS home files.
#  After unlocking any protected files and saving configuration settings
#  you are now ready to run opatch using the following command.
#
#  % opatch apply -local
#
#  Note: In configuration A, invoke this only on one node.
#
#  8b. Patch the Server home files.
#  Change the ORACLE_HOME environment variable to point to the RDBMS server
#  home. Then run opatch to apply the changed files to that home.
#
#  % ORACLE_HOME=<Server home>
#  % export ORACLE_HOME
#  % opatch apply custom/server/4642651 -local
#
#  Note: In configuration A, invoke this only on one node.
#
###########################################################################
#
#  9. After opatch completes, some configuration settings need to be applied
#  to the patched files. 
#
#  % custom/scripts/postpatch.sh -crshome <CRS Home path>
#
#  Note: In configuration A, invoke this only on one node.
#
###########################################################################
#
#  10. Now security settings need to be restored on the CRS Home. This script
#  will also restart the CRS daemons. Invoke this script as root.
#
#  # custom/scripts/postrootpatch.sh -crshome <CRS Home path>
#
#  Note: This script should only be invoked as part of the patch process.
#
#  Note: In configuration A, invoke this on each node. Do not invoke this
#        in parallel on two nodes.
#
###########################################################################
#
#  11. On success you can determine whether the patch has been installed by
#  using the following command;
#
#  % opatch lsinventory -detail
#
#  Installed Patch List:
#  =====================
#  1) Patch 4642651 applied on Wed Sep 01 18:31:11 EDT 2004
#      [ Base Bug(s): 4642651 ]
#        /u01/app/oracle/product/crs/bin/ocssd.bin -> OH/bin
#
###########################################################################
#
#  Additional Special Notes:
#  -------------------------
#  If there are multiple Server Homes in your configuration, then
#  in step 8b, apply the patch to each home before continuing.
#
#  If you later install an additional Server home, or if you skip a
#  server home, then applying the patch to additional homes is easier.
#  1. Shut down all instances using that Server home
#  2. Invoke opatch as described in step 8b.
#  3. Restart the instances in that Server home
#  This can be done while CRS is active.
#
#
#  Patch Deinstallation Instructions:
#  ----------------------------------
#
#  To roll back the patch, follow all of the above steps 1-7. In step 8,
#  invoke the following opatch commands to roll back the patch in all homes.
#
#  % ORACLE_HOME=<CRS home path>
#  % export ORACLE_HOME
#  % opatch rollback -id 4642651 -local
#
#  % ORACLE_HOME=<Server home path>
#  % export ORACLE_HOME
#  % opatch rollback -id 4642651 -local
#
#  Afterwards, continue with steps 9-11 to complete the procedure.
#
###########################################################################
#
#  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.
#
###########################################################################
