# 
#  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 5256865
#-------------------------------------------------------------------------
#
#  DATE:  Wed Aug 16 13:15:01 PDT 2006
#  -------------------------------
#  Platform Patch for : 226: Linux 64bit X86-64
#  Product Version #  : 10.2.0.2
#  Product Patched    : PCW/RDBMS
#
#  Bugs fixed by this bundle
#  =========================
#
#  CRS HOME
#  ========
#  5256865: PLACEHOLDER BUG FOR PCW 10.2.0.2 CRS BUNDLE II
#  5244242: ORACLE CSSD FAILURE 134 AND ORACLE CLSOMON FAILURE STATUS 12
#  5252605: CSS RECONFIG STARTS BEFORE <MISSCOUNT> SECONDS HAVE ELAPSED
#  5232672: IMPENDING RECONFIGURATION THRESHOLD -1 WITH MISSCOUNT 3
#  5232652: ORACLE CSSD FAILURE 134; INIFINITE REBOOT LOOP WITH CSS PRIORITY 4
#  5232700: VIP START/CHECK FAILS DUE TO IP ALREADY BEING UP
#  5238599: 90% HEARTBEAT FATAL MESSAGES CONSTANTLY AT MISSCOUNT 3
#  5232290: WARNING REPORTED EVERY SECOND: 50% HEARTBEAT FATAL, EVICTION IN 2
#           SECONDS
#  5232279: AT NODE JOIN, OTHER NODES ARE EVICTED - CLSOMON FAILED WITH FATAL
#           STATUS 13
#  5258999: RACGIMON BINARY WITH FIX FOR BUG 4737607 IS MISSING FROM CRS
#           BUNDLE 1
#  4127644: CSS NOT SET IN HIGH/FIXED PRIORITY CLASS USING CRSCTL SET CSS
#           PRIORITY
#  4230367: POST EVM PW_NW_DOWN EVENT BEFORE BRINGING DOWN DEPENDENT RESOURCES
#  4437727: VIPCA FAILS COMPLAINING THAT INTERFACE IS NOT PUBLIC
#  4459961: [10201-050624]INVALID COMPONENT KEYS ARE LISTED IN "CRSCTL
#           LSMODULES CSS"
#  4493093: INSTALL - CRS- ROOTADDNODE.SH REPORTS HASCONTEXT INTERNAL ERROR
#           [PRKH-1001
#  4556878: CRSD CORE AT CLS_THRMXUNLOCK()
#  4669874: RLB EVENT DELIVERY STOPS AFTER INSTANCE RESTART
#  4702263: CRSD FAILURE IS NOT HANDLED IN THE INIT SCRIPT
#  4707711: -D64 OPTION REQUIRED IN THE JRE COMMAND LINE IN CLUVFY.SBS
#  4716107: CVU FAILS IF CENTRAL INVENTORY CONTAINS A DEINSTALLED CRS HOME
#  4723189: MERGE VERITAS FIXES FOR PLE PLATFORMS IN THE INIT SCRIPTS
#  4726670: 10202-TC2: TOTAL SPACE OF OCR IS REPORTED AS 0 WHILE EXECUTING
#           ROOT102.SH
#  4728396: DBCA IS NOT CHANGING THE PARAMETER REQUIRED_RESOURCES FOR USING ASM.
#  4734413: PERFORMANCE:OCR READ FROM LOCAL CACHE BLOCKED BY WRITER WORKING ON
#           DIFFERENT KEY
#  4737607: VIPS DON'T FAILOVER WHEN IP IS DOWN
#  4739742: CLWS CRSD COREDUMP SYSSEGV IN PROU_CHECK_TAG<-PROCR_CLOSE_KEY
#  4741766: PRSRVUT.C : COMMENT PROBLEM IN AIX
#  4742803: READ RETURNS SUCCESSFUL AFTER 5 FAILED RETRY
#  4743518: PERFORMANCE:  14S TO START VIP DUE TO PING; BLOCKS ALL CRS RESOURCES
#  4745373: OCSSD SOCKET LEAK DENIAL OF SERVICE VULNERABILITY
#  4748946: CRSD CRASHES WITH OCR ERRORS
#  4755275: CLWS CRSD ABORTS: FAIL TO START MONITOR THREAD, COMM FAILURE
#  4756170: OCR: S_UPDATE_REMOTE_CACHE_INT: FAILED TO RCV ACK BLOCKS FAILOVER
#  4759984: ROOT102.SBS NEEDS FIX
#  4772904: PRKR-1007 WHEN ISSUING COMMAND SRVCTL ENABLE DATABASE -D ODSCMPS
#  4865736: ASM RESOURCE SHOULD NOT HAVE DEPENDENCY ON VIP
#  4870817: OCRDUMP -BACKUPFILE IS FAILING WITH PROT-302
#  4870952: CLWS RACGIMON COREDUMPS SEGV USUALLY WITH CORE FILE ROUTINES
#           ON STACK
#  4879951: CLWS CRSD COREDUMP SEGV IN EVENTUTIL::SET_CONTEXT, OR NO STACK
#  4883916: PERFORMANCE: 60S TO STOP CRS RESOURCE ON SHUTDOWN ABORT
#  4890793: ASM RESOURCE DEPENDS ON VIP EVEN AFTER REMOVING REQUIRED_RESOURCES
#  4919514: CSSD DOES NOT FAIL WHEN VENDOR CLUSTERWARE PRESENT AND SKGXNREG
#           FAILS
#  4925962: FIX NEEDED IN ROOTDELETE.SBS, ROOTUPGRADE.SBS AND LOCALCONFIG.SBS
#  4926814: CLWS EVMD ABORTS IN RECONFIGURATION
#  4936206: CSS CLIENTS FAIL WHEN VENDOR SKGXN RETURNS 0 FOR SKGXNTPSHL
#  4936950: CHANGES TO ROOT AND INIT SCRIPTS TO SUPPORT SUNCLUSTER ON
#           SOLARIS X86
#  4937400: MAKE GSD NO-OP AND DEFINE LD_LIBRARY_PATH ON SOLARIS X86 PLATFORMS
#  4945458: CLWS 2 OCSSDS TIMES OUT IN NESTED RECONFIG, GOING 1 TO 5 NODES
#  4946339: 10202-TC6: ENABLING CRSD LOGGING WITH ENV  DOES NOT WORK
#  4951958: CSSD REPORTS GRACEFUL SHUTDOWN ON PRIVATE NETWORK CABLE PULL
#  4963850: FAILOVER BLOCKED - SERVICE START WAITS ON SECOND PASS RECOVERY
#           TO ACQUIRE UL
#  4967761: 1.6S - 2.0S "GAP" IN CRSD BEFORE CRS STARTS RECOVERING RESOURCES
#  4997470: CSS STARTUP INCORRECTLY TERMINATES WHEN ANOTHER NODE COMES UP
#           DURING RECONFIG
#  5004962: ASM IS STOPPED ON NETWORK DOWN, WHEN THERE ARE NO REQUIRED RESOURCES
#  5007623: 10202-TC7: SEGV IN CLSSGMFMTDATAREQRESP CAUSED NODE REBOOT
#  5011915: NEEDS LONG TIME FOR SPLIT-BRAIN RESOLUTION AFTER APPLYING
#           PATCH 4642651
#  5015469: OPROCD REBOOTS NODE WHEN TIME IS SET BACK BY XNTPD
#  5022314: CLSRWRAP.SBS - HANDLE SOLARIS X86 AND X64 CONDITIONS
#  5037858: ENH:OPROCD WARNING LEVELS WHEN GETTING CLOSE TO REBOOT
#  5037871: ENH: CSSD LOGGING
#  5041498: PROBLEM INITIALIZING OCR ON A SHARED DEVICE
#  5052569: WAIT FOR 'REBOOTTIME' AFTER THE KILL ECHO ON NON-SKGXN PLATFORMS
#  5071602: NEED OCR PATCH UTILITY / KEY EDITOR FOR DIAGNOSIS/REPAIR OF OCR
#           CORRUPTIONS
#  5077218: NT10202-RC3: CSS ASSERTS IN CLSSNMHANDLEVOTEINFO, CLSSNM.C 2224,
#           NODE REBOOTED
#  5079815: PERFORMANCE: STARTCHECKSLEEP BEFORE STARTING CSS
#  5087485: OCRPATCH NEEDS PASSWORD PROTECTION
#  5087948: OCRPATCH NEEDS WRAPPER SHELL SCRIPT JUST LIKE OTHER OCR* TOOLS
#  5092622: OCLSOMON USES THE WRONG TIMEOUT VALUE
#  5136712: OCRDUMP PRINTS OUT NO VALUE FOR A KEY WHEN KEY HAS A ACTUALLY
#           LARGE VALUE
#  4667776: CLSCFG -DOWNGRADE FAILES IN AMD ( X86_64 )
#  4682574: PERFORMANCE: 500-900MS DELAY BETWEEN END OF CSS RECONFIG AND
#           LMON RECOVERY
#  4893560: CLSCSELECT DOES NOT HANDLE TIMEOUT = 0 CORRECTLY
#
#
#
#  RDBMS_HOME
#  ==========
#  4669874: RLB EVENT DELIVERY STOPS AFTER INSTANCE RESTART
#  4728396: DBCA IS NOT CHANGING THE PARAMETER REQUIRED_RESOURCES FOR USING ASM.
#  4772904: PRKR-1007 WHEN ISSUING COMMAND SRVCTL ENABLE DATABASE -D ODSCMPS
#  4870952: CLWS RACGIMON COREDUMPS SEGV USUALLY WITH CORE FILE ROUTINES ON
#           STACK
#  4937400: MAKE GSD NO-OP AND DEFINE LD_LIBRARY_PATH ON SOLARIS X86 PLATFORMS
#  5022314: CLSRWRAP.SBS - HANDLE SOLARIS X86 AND X64 CONDITIONS
#
#  NOTE: A non-clustered RDBMs HOME runing the CSSD and ASM may also benefit
#  from a number of the CRS HOME patches.
# 
#
#  Known Issues:
#  =============
#  Under certain conditions the following bug, 4518443, maybe encountered.
#  This bug manifests itself as a race condition that appears with many
#  concurrent CRS actions. If you encounter this bug please contact support
#  for a pse if one is not available for your platform.  
#
#
#  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.
#
#  As the crs software owner:
#  % opatch lsinventory -detail -oh <CRS_HOME>
#
#  As the rdbms server software owner:
#  % 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. As the crs software owner, unzip the PSE container file, and enter
#     the patch container directory. 
#
#  % unzip p5256865_10202_LINUX.zip
#  % cd 5256865
#
###########################################################################
#
#  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.
#
#     $ORA_CCRS_HOME/bin/crsctl stop crs
#
###########################################################################
#
#  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.
#
#  ( Please review section 7.2 first ) As the RDBMS software owner;
#  % custom/server/5256865/custom/scripts/prepatch.sh -dbhome <RDBMS_HOME>
#
###########################################################################
#
#  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.
#
#
#    7.2 Patch the RDBMS home files.
#
#    Note: The RDBMS portion can only be applied to an RDBMS home that
#          has been upgraded to *10.2.0.2*.
#
#    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;
#
#    % opatch apply custom/server/5256865 -local -oh <RDBMS_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.
#
#  ( Please review section 7.2 first ) As the RDBMS software owner;
#  % custom/server/5256865/custom/scripts/postpatch.sh -dbhome <RDBMS_HOME>
#
###########################################################################
#
#  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>
#  % opatch lsinventory -detail -oh <RDBMS_HOME>
#
#  Installed Patch List:
#  =====================
#
#   Patch  5256865      : applied on Wed Aug 16 02:13:02 EDT 2006
#     Created on 15 Aug 2006, 17:23:25 hrs US/Pacific
#     Bugs fixed:
#     ...
#
#  % opatch lsinventory -detail -oh <RDBMS_HOME>
#
#  Installed Patch List:
#  =====================
#  Patch  5256865      : applied on Wed Aug 16 02:15:36 EDT 2006
#     Created on 15 Aug 2006, 17:20:44 hrs US/Pacific
#     Bugs fixed:
#     ...
#
#
###########################################################################
#
#  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-6. In step 7,
#  invoke the following opatch commands to roll back the patch in all homes.
#
#  % opatch rollback -id 5256865 -local -oh <CRS_HOME>
#
#  % opatch rollback -id 5256865 -local -oh <RDBMS_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.
#
###########################################################################
