#-------------------------------------------------------------------------
#  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 5365683 
#-------------------------------------------------------------------------
#
#  DATE:  Tue Mar  6 22:51:39 PST 2007
#  -------------------------------
#  Platform Patch for : Linux x86-64
#  Product Version #  : 10.2.0.3
#  Product Patched    : RDBMS Server
#
#  Bugs fixed by this patch :
#  -------------------------
#  5365683:CRS REPEATEDLY STOPS AND RESTARTS VIPS WHILE RECOVERING MULTIPLE
#  NODES
#  
#
#
#  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.
#
#  CRS_HOME   = the full path to the crs home.
#
#  If the owner of these homes are different ensure you execute the 
#  following steps as the correct owner in the correct environment.
#
#  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.
#
###########################################################################
#
#  1. Verify that the Oracle Inventory is properly configured.
#
#  As the crs software owner;
#  % opatch lsinventory -detail -oh <CRS_HOME>
#
#  This should list the components installed and a list of nodes.
#
#  If the Oracle inventory is not setup correctly this utility will
#  fail. 
#
###########################################################################
#
#  2. As the crs software owner, unzip the PSE container file, and enter
#     the patch container directory. 
#
#  % unzip p5365683_10203_Linux-x86-64.zip
#  % cd 5365683
#
###########################################################################
#
#  3. Shut down all Applications replying on the RDBMS/ASM instances, which
#     rely on RDBMS and ASM instances dependent on the CRS daemons being shut
#     down in step 4. Then shutdown the RDBMS and ASM instances dependent
#     on the CRS daemons being shut down in step 4.
#
###########################################################################
#
#  4. 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
#
###########################################################################
#
#  5.  Prior to applying this part of the fix, you must invoke this script
#  as root to unlock protected files.
#  
#  <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.
#
#
###########################################################################
#
#  6. Now invoke an additional script as the crs software installer/owner.
#  This script will save important configuration settings.
#
#  % custom/scripts/prepatch.sh -crshome <CRS_HOME>
#
#  Note: In configuration A, invoke this only on one node.
#
###########################################################################
#
#  7. Patch the Files 
# 
#    7.1 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.
#
#    As the crs software owner;
#
#    % opatch apply -local -oh <CRS_HOME>
#
#    Note: In configuration A, invoke this only on one node.
#
###########################################################################
#
#  8. After opatch completes, some configuration settings need to be applied
#  to the patched files. As the crs software owner execute the following; 
#
#  % custom/scripts/postpatch.sh -crshome <CRS_HOME>
#
#  Note: In configuration A, invoke this only on one node.
#
###########################################################################
#
#  9. 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>
#
#  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.
#
###########################################################################
#
#  10. On success you can determine whether the patch has been installed by
#  using the following command;
#
#  % opatch lsinventory -detail -oh <CRS_HOME>
#
#  Installed Patch List:
#  =====================
#
#   Patch  5365683      : applied on Tue May  1 17:23:25 PST 2007
#     Created on 6 Mar 2007, 22:51:39 hrs US/Pacific
#     Bugs fixed:
#     ...
#
###########################################################################
#
#  Patch Deinstallation Instructions:
#  ----------------------------------
#
#  To roll back the patch, follow all of the above steps 1-6. In step 7,
#  invoke the following opatch commands to roll back the patch in all homes.
#
#  % opatch rollback -id 5365683 -local -oh <CRS_HOME>
#
#  Afterwards, continue with steps 8-10 to complete the procedure.
#
###########################################################################
#
#  If you have any problems installing this PSE or are not sure
#  about inventory setup please call Oracle support.
#
###########################################################################
