0 Replies Latest reply: May 4, 2012 3:58 AM by user13436034 RSS

    How to do Pre patching in clusterware :11.1.0.7

    user13436034
      Hello experts,

      I wont to apply CRS latest patches to crs_home.

      1) current crs home : 11.1.0.7

      2) i wont to apply patch 11.1.0.7.7 (PI 11724953)

      3) this action plan form read me patch

      a) Run the following script (on only one node if the CRS home is shared, but on each node if the CRS home is not shared) as root to unlock protected files:

      custom/scripts/prerootpatch.sh -crshome <CRS_HOME> -crsuser <username>

      where <username> is the software installer/owner for the CRS home.
      b) Run the following script (on only one node if the CRS home is shared, but on each node if the CRS home is not shared) as the CRS software installer/owner to save important configuration settings:

      % custom/scripts/prepatch.sh -crshome <CRS_HOME>

      Note: The RDBMS portion can only be applied to an RDBMS home that has been upgraded to 11.1.0.7.0.

      Also, If the CRS Version and RDBMS version are the same, enter the following command as the RDBMS software owner:

      % custom/server/11724953/custom/scripts/prepatch.sh -dbhome <RDBMS_HOME>



      from session log at root user
      =====================
      [root@auhodiron01 11724953]# custom/scripts/prerootpatch.sh -crshome /oracrs/oracle/product/111 -crsuser ororacrs
      Checking to see if Oracle CRS stack is down...


      =======================================================
      = =
      = Oracle's Enterprise Linux x86_64 64bit OSCC =
      = =
      =======================================================



      ===NOTICE===NOTICE===NOTICE===NOTICE===NOTICE===NOTICE===NOTICE===

      YOU HAVE LOGGED INTO AN AMD64 SYSTEM RUNNING OEL5 (Oracle LINUX 64-BIT.)

      PLEASE INSURE ANY ACTIVITY YOU DO ON THIS SYSTEM TAKES THAT INTO ACCOUNT.

      FOR EXAMPLE. INSURE ANY PATCHING YOU DO IS FOR 64-BIT VS 32-BIT

      ===NOTICE===NOTICE===NOTICE===NOTICE===NOTICE===NOTICE===NOTICE===


      Oracle CRS stack is run status. Stop the CRS stack using the following command
      /etc/init.d/init.crs stop
      If the CRS Home is shared, also make sure that the Oracle CRS stack is stopped on other cluster nodes


      [root@auhodiron01 11724953]# custom/scripts/prepatch.sh -crshome /oracrs/oracle/product/111
      custom/scripts/prepatch.sh completed successfully.


      [root@auhodiron01 11724953]# custom/server/11724953/custom/scripts/prepatch.sh -dbhome /tiron7/oracle/product/111
      custom/server/11724953/custom/scripts/prepatch.sh completed successfully.


      now can i proceed with applying patch,

      is need to pre check again? If need to recheck again let know how to do Pre Patch analysis.



      Thx in advance.

      Edited by: user13436034 on May 4, 2012 1:58 AM