# 
#-------------------------------------------------------------------------
#  BUNDLE Patch for Base Bug 9207257
#-------------------------------------------------------------------------
#
#  DATE: 11:54:44 Dec 13 2009
#  -------------------------------
#  Platform Patch for : Linux x86-64 (226)
#  Product Version #  : 11.1.0.7.0
#  Product Patched    : CRS/RDBMS
# 
#-------------------------------------------------------------------------
#
#  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. 
#
#  Bugs fixed by this bundle
#  =========================
#
#  CRS HOME
#  ========
#
#
#
#  RDBMS_HOME
#  ==========
#  
#
#
#  NOTE: A non-clustered RDBMs HOME runing the CSSD and ASM may also benefit
#  from a number of the CRS HOME patches.
# 
#
#  Known Issues:
#  =============
#  N/A
#
#  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.
#  RDBMS_HOME = the full path to the server 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.
#
#  % opatch lsinventory -detail -oh <CRS_HOME>
#  % opatch lsinventory -detail -oh <RDBMS_HOME>
#
#  This should list the components the list of nodes.
#
#  If the Oracle inventory is not setup correctly this utility will
#  fail. 
#
#
###########################################################################
#
#  2. Unzip the PSE container file
#
#  % unzip p9207257_11107_LINUX.X64.zip
#
###########################################################################
#
# 3.1 In configuration A, shut down the RDBMS and ASM instances, listeners 
#     and nodeapps on all nodes before shutting down the CRS daemons on 
#     all nodes. Note that these setps must be run in the order specified.
#
#     3.1.1  To shutdown RDBMS on all nodes run the following command: 
#
#       % $ORACLE_HOME/bin/srvctl stop database -d dbname      
#
#     3.1.2  To shutdown ASM instances run the following command on each node:
#
#       % $ORACLE_HOME/bin/srvctl stop asm -n <node_name>
#
#     3.1.3  To shutdown listeners run the following command on each node:
#
#       % $ORACLE_HOME/bin/srvctl stop listener -n <node_name>
#
#     3.1.4  To shutdown nodeapps run the following comand on each node:
#
#       % $ORA_CRS_HOME/bin/srvctl stop nodeapps -n <node_name>
#
#     3.1.5  Now shutdown CRS daemons on each node by running as root:
#
#       crsctl stop crs
#     
#  3.2 In configuration B, shut down the RDBMS and ASM instances, listeners
#      and nodeapps followed by CRS daemons on the local node. 
#
#     3.2.1  To shutdown RDBMS instance on the local node run the following command:
#
#       % $ORACLE_HOME/bin/srvctl stop instance -d dbname -i instance_name
#
#       Then run commands (3.1.2) through (3.1.4) mentioned above. Finally
#       as root, issue the following command to stop the CRS daemons.
#
#       crsctl stop crs
#
###########################################################################
#
#  4.  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.
#
#
###########################################################################
#
#  5. 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.
#
#  ( Please review section 6.2 first ) As the RDBMS software owner;
#  % custom/server/9207257/custom/scripts/prepatch.sh -dbhome <RDBMS_HOME>
#
###########################################################################
#
#  6. Patch the Files
#
#    6.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 Oracle Clusterware (CRS) software owner,
#    from the directory where the patch was unzipped;
#
#    % opatch napply -local -oh <CRS_HOME> -id 9207257
#
#    Note: In configuration A, invoke this only on one node.
#
#
#    6.2 Patch the RDBMS home files.
#
#    Note: The RDBMS portion can only be applied to an RDBMS home that
#          has been upgraded to *11.1.0.7.0*.
#
#    For additional information please read Note.363254.1;
#    Applying one-off Oracle Clusterware patches in a mixed version home
#    environment
#
#    As the RDBMS software owner,
#    from the directory where the patch was unzipped;
#
#    % opatch napply custom/server/ -local -oh <RDBMS_HOME> -id 9207257
#
#    Note: In configuration A, invoke this only on one node.
#
###########################################################################
#
#  7. Configure the HOME
#   
#    7.1 Configure the CRS HOME
# 
#    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.
#
#    7.2 Configure the RDBMS HOME
# 
#    After opatch completes, some configuration settings need to be applied
#    to the patched files. As the RDBMS software owner execute the following; 
#
#    % custom/server/9207257/custom/scripts/postpatch.sh -dbhome <RDBMS_HOME>
#
#    Note: In configuration A, invoke this only on one node.
#
###########################################################################
#
#  8. 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.
#
###########################################################################
#
#  9. On success you can determine whether the patch has been installed by
#  using the following command;
#
#  % opatch lsinventory -detail -oh <CRS_HOME>
#  % opatch lsinventory -detail -oh <RDBMS_HOME>
#
###########################################################################
#
#  Additional Special Notes:
#  -------------------------
#  If there are multiple Server Homes in your configuration, then
#  in step 7b, 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 7b.
#  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-5. In step 6,
#  invoke the following opatch commands to roll back the patch in all homes.
#
#  % opatch rollback -id 9207257 -local -oh <CRS_HOME>
#
#  % opatch rollback -id 9207257 -local -oh <RDBMS_HOME>
#
#  Afterwards, continue with steps 7-9 to complete the procedure.
#
###########################################################################
#
#  If you have any problems installing this PSE or are not sure
#  about inventory setup please call Oracle support.
#
###########################################################################
