# #------------------------------------------------------------------------- # BUNDLE Patch for Base Bug 26839277 #------------------------------------------------------------------------- # # DATE: 03:13:00 Sep 21 2017 # ------------------------------- # Platform Patch for : Linux x86-64 (226) # Product Version # : 12.2.0.1.0 # Product Patched : WLM # #------------------------------------------------------------------------- # # 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). # # 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 # ========================= # # WLM # ======== # # 26584906 UPDATE WLM TESTS TO RUN ON TOMCAT 8.0.44 # # # Known Issues: # ============= # N/A # # Patch Installation Instructions: # -------------------------------- # # Configuration scenarios: # # 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. # # Before start set the following environment variables: # # ORACLE_HOME = the full path to the GI home. # ########################################################################### # # 1. Verify that the Oracle Inventory is properly configured. # # % opatch lsinventory -detail -oh # # 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 p26839277_12201_LINUX.X64.zip # ########################################################################### # # 3. Disable and stop QoS Management Server resource # # In any node of the cluster perform the following commands as grid home # user: # # % srvctl disable qosmserver # % srvctl stop qosmserver # ########################################################################### # # 4. Unlock GI HOME # # Prior to applying this part of the fix, you must invoke this script # as root to unlock protected files. # # % /crs/install/rootcrs.pl -unlock # # Note: In configuration A, invoke this only on one node. # ########################################################################### # # 5. Patch the 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 -id 26839277 # # Note: In configuration A, invoke this only on one node. # ########################################################################### # # 6. Restart CRS daemons # # This script will restart the CRS daemons. Invoke this script as root. # # % /crs/install/rootcrs.pl -patch # # 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. # ########################################################################### # # 7. Enable and start QoS Management Server resource # # In any node of the cluster perform the following commands as grid home # user: # # % srvctl enable qosmserver # % srvctl start qosmserver # ########################################################################### # # 8. Verify patch application # # On success you can determine whether the patch has been installed by # using the following command; # # % opatch lsinventory -detail -oh # ########################################################################### # # Additional Special Notes: # ------------------------- # # None for this patch. # ########################################################################### # # Patch Deinstallation Instructions: # ---------------------------------- # # To roll back the patch, follow all of the above steps 1-4. In step 5, # invoke the following opatch command to roll back the patch: # # % opatch rollback -id 26839277 -local -oh # # Afterwards, continue with steps 6-8 to complete the procedure. # ########################################################################### # # If you have any problems installing this PSE or are not sure # about inventory setup please call Oracle support. # ###########################################################################