GI-PSU Patch on CRS/Grid Home

April 3, 2012

Note : We Applied GI-PSU only For CRS/GRID HOME.

Some Insight on Opatch auto command:——————————————————Q1) To confirm Does this patch needs to be executed as root or oracle OS user?Ans) “opatch auto” needs to be executed as root.Q2) If root user is must, then Is there a way where oracle user can execute opatch for GI without root user?Ans) You cannot use “opatch auto” to patch as oracle user, but you can patch it manually. However you will have to ask root user to run the rootcrs.pl -unlock to unlock the GI home so that oracle can apply the patch and after the patch is applied root has to execute rootcrs.pl -patch to lock the binaries.Q3) Does “opatch auto” applies patch only to one host at a time. i.e. if you run opatch on node 1 then only that node is patched?Ans) ‘opatch auto’ applies patches to multiple OHs on a single host (no cross-host patching). It automatically detects all ORACLE_HOME and ASM_HOME equivalent to CRS version and applies patch only to those home. Q4) Will “opatch auto” takes care of stop/start and no need to bring down anything manually?Ans) Using auto option, there are no manual steps like stopping crs, instance, nodeapps, asm, running rootprepatch.sh or any other scripts require to be performed by user while applying or rolling back patch. All this steps are automatically taken care by opatch.Q5) We generally bring down CRS or DB’s using HA command’s, since CRS and DB’s resource are under the control of VCS (VERITAS).so does your “opatch auto” will take of bringing the CRS and DB’s down automatically using HA command’s?1) Do you want us to manually Bring DB’s resource manually using HA Command’s, but not CRS?2) Even if I bring down DB’s using HA’s commands, I am wondering how “opatch auto” will bring the CRS down while patching as CRS is also under the control of VCS ?Ans) :opatch uses crsctl and srvctl to stop the crs and resources as applicable so it will be a clean stop if that is your concern it does not use HA commands.1. We would recommend that you let opatch do it automatically.2. There should not be an issue for opatch to bring down the crs. Do you have issues stopping crs using crsctl stop crs? If not it should not be a problem.Q6) We have scheduled to apply this GI PSU patch in DEV on Tuesday. However, I saw following note on Metalink and I am concerned if we will face this issue after applying GI PSU patch:Bug 10224621 – Lots of requests to UISERVER (every sec) after installing GI PSU 2 patch 9655006 [ID 10224621.8] ?Ans) It is not an issue actually only normal messages written to crsd.log the bug was raised because customer wanted to suppress the messages.The messages means that commands like crs_stat, crsctl or srvctl are being executed.You can ignore it and go ahead with patching.Q7) Are PSU’s and CPUS’s cumulative ?Ans) Yes the CPU and PSU are cumulative.That is if you apply the JAN 2012 CPU then all the previous CPU’s will also be applied including the OCT CPU.But you have to apply either of CPU or PSU as their patching mechanism is different.Also all the PSU also contain the CPU fixes. SO if you apply the JAN2012 PSU it will contain all the previous PSU fixes plus CPU fixes.So you either apply JAN2012 CPU or JAN 2012 PSUQ8) As what OS user do we need to take backup of CRS, root or oracle user ?Ans) Backup CRS_HOME as root,As few files are owned by root in CRS_HOME , if you try taking backup using taras oracleOS user, they will not get backedup and you may receive the error as below.ls -ltR /u01/app/crs |grep “root root” => check file owned by root in crs HOME (/u01/app/crs)maldevsrv01:/opt/oracle: ls -ltR /u01/app/crs |grep “root root”
-rw-r–r– 1 root root 4361 Apr 1 06:29 oradaemonagent
-rw-r–r– 1 root root 4361 Apr 1 06:29 oradnssd
-rw——- 1 root root 6914048 Apr 7 15:21 backup00.ocrtar: crs/log/maldevsrv01/client/ocrconfig_20722.log: Permission denied
tar: crs/cdata/maludev-clustr/backup00.ocr: Permission deniedCheck IF the specific file is backedupas below:===================================
tar -tvf maldevsrv01.oraHome_CRS_11.2.0.1.0.bkup.10.04.2012.07.13.44.tar |grep /sqlplus |grep -v /sqlplus/
-rwxr-x–x 104/3001 9536 Feb 19 09:13 2012 crs/bin/sqlplusExtarct single file (Aud_info_D041.28-MAR-12-09.59.24.log_FL)
==================================================
cd /tmp/SR
tar -xvf /opt/oracle/abc.tar Aud_info_D041.28-MAR-12-09.59.24.log_FL

Ooops!!! seems oracle OS user do not have Priv’s to rename or backup the existing Opatch folder in CRS Home. Instead I will remove all contents from /u01/app/crs/Opatch and copy back from downloaded location as below steps

Executing /usr/bin/perl /u01/orasoft/opatch/OPatch/crs/patch112.pl -patchdir /u01/orasoft/patches -patchn grid_psu -oh /u01/app/crs -paramfile /u01/app/crs/crs/install/crsconfig_paramsopatch auto log file location is /u01/orasoft/opatch/OPatch/crs/log/opatchauto2012-04-01_07-03-58.logDetected Oracle Clusterware installUsing configuration parameter file: /u01/app/crs/crs/install/crsconfig_paramsOPatch is bundled with OCM, Enter the absolute OCM response file path:/u01/orasoft/opatch/OPatch/ocm/ocm.rsp(Here it ask the location for the ocm file)Unable to determine if /u01/app/crs is shared oracle homeEnter ‘yes’ if this is not a shared home or if the prerequiste actions are performed to patch this shared home (yes/no): yes(Type yes)Successfully unlock /u01/app/crspatch /u01/orasoft/patches/grid_psu/9655006 apply successful for home /u01/app/crspatch /u01/orasoft/patches/grid_psu/9654983 apply successful for home /u01/app/crsCRS-4123: Oracle High Availability Services has been started.

Verify the Patch is applied.

opatch lsinventory -detail -oh /u01/app/crs |grep 9655006

Check If CRS and DB have come up:==============================

ps -ef |grep d.bin

ps -ef |grep pmon

ps -ef |grep tns

/u01/app/crs/bin/crsctl stat resource

/u01/app/crs/bin/crsctl check cluster -n maldevsrv01

Make sure all VCS resources are ONLINE use below command.===============================================pbrun hastatus -sumpbrun hares -statetail -f /var/VRTSvcs/log/engine_A.logI have attached the log for which the patch was applied.