Shulou(Shulou.com)06/01 Report--

27282436 = 27107360 (PSU) + 26925532 (OJVM)

0. In order to avoid conflicts with system background jobs when installing patches to run data dictionary scripts, check AutoTask. If there is an Enabled, Disable first, and then Enable after patching.

Su-oraclesqlplus "/ as sysdba" set lin 180 pages 10000COL CLIENT_NAME FORMAT A40COL CONSUMER_GROUP FORMAT A30COL WINDOW_GROUP FORMAT A30select CLIENT_NAME,STATUS,CONSUMER_GROUP,WINDOW_GROUP from dba_autotask_client CLIENT_NAME STATUS CONSUMER_GROUP WINDOW_GROUP -auto optimizer stats collection ENABLED ORA$AUTOTASK_STATS_GROUP ORA$AT_WGRP_OSauto space advisor DISABLED ORA$AUTOTASK_SPACE_GROUP ORA$AT_WGRP_SAsql tuning advisor DISABLED ORA$AUTOTASK_SQL_GROUP ORA$AT_WGRP_SQBEGINDBMS_AUTO_TASK_ADMIN.DISABLE (client_name = > 'auto optimizer stats collection' Operation = > NULL, window_name = > NULL) END;/BEGINDBMS_AUTO_TASK_ADMIN.DISABLE (client_name = > 'auto space advisor', operation = > NULL, window_name = > NULL); END;/BEGINDBMS_AUTO_TASK_ADMIN.DISABLE (client_name = >' sql tuning advisor', operation = > NULL, window_name = > NULL); END;/

Reconfirm that the current database component status is normal, and record the current status:

Set lin 170 pages 10000select comp_id,status,version from dba_registry COMP_ID STATUS VERSION-- OWB VALID 11.2.0.4.0APEX VALID 3.2.1.00.12EM VALID 11.2.0.4.0AMD VALID 11.2.0.4.0SDO VALID 11.2.0.4.0ORDIM VALID 11.2.0.4.0XDB VALID 11.2.0.4.0CONTEXT VALID 11.2.0.4.0EXF VALID 11.2.0.4.0RUL VALID 11.2.0.4.0OWM VALID 11.2.0.4.0CATALOG VALID 11.2.0.4.0CATPROC VALID 11.2.0.4.0JAVAVM VALID 11.2.0.4.0XML VALID 11.2.0.4.0CATJAVA VALID 11.2.0.4.0APS VALID 11.2.0.4.0XOQ VALID 11.2.0.4.0RAC VALID 11.2.0.4.019 rows selected.

1. Stop listener with the grid user and kill the database session process

Su-gridsrvctl stop listenersrvctl stop scan_listenerkill-9 `ps-ef | grep LOCAL=NO | grep-v grep | grep-iv ASM | awk'{print $2}'`

two。 Disable db automatic startup as oracle user, and then stop db

Su-oraclesrvctl disable db-d pubdbsrvctl stop db-d pubdb

3. (this step has been completed ahead of schedule) replace the opatch tool with root users to the latest version

Su-rootcat / home/oracle/.profile | grep HOMEexport PATCH_DIR=/oracle/softwareexport PATCH_GRID_HOME=/grid/app/11.2.0.4/gridexport PATCH_ORACLE_HOME=/oracle/app/oracle/11.2.0.4/db_1mv $PATCH_GRID_HOME/OPatch $PATCH_GRID_HOME/ Opatch.orig`date +% Y% m% d`mv $PATCH_ORACLE_HOME/OPatch $PATCH_ORACLE_HOME/ OPatch.orig`date +% Y% m% d`cd $PATCH_DIRunzip p6880880_112000_HPUX-IA64.zipcp -r. / OPatch $PATCH_GRID_HOME/cp-r. / OPatch $PATCH_ORACLE_HOME/cd $PATCH_GRID_HOME/ Chown-R grid:oinstall. / OPatchcd $PATCH_ORACLE_HOME/; chown-R oracle:oinstall. / OPatch

4. Follow these steps to install the patch

Su-oracleexport PATCH_DIR=/oracle/softwarecd $ORACLE_HOME/OPatch/ocm/bin./emocmrsp-output / tmp/ocm.rspcd $PATCH_DIRunzip p27282436_112040_HPUX-IA64.zipsu-root

a. Check the environment variables of root users. If you have settings such as ORACLE_HOME,ORA_GRID_HOME,GRID_HOME, you need to log out of these environment variables, and then log in to the system again.

b. Check whether there is enough space in the file system where crs and db are installed, and ensure at least 50g of free space before patching.

c. Check the crontab jobs of root/grid/oracle users, log out the jobs that access $ORACLE_HOME and $GRID_HOME before patching, and then enable them after patching

d. Check to see if there are grid/oracle independent processes that are not registered in OCR, such as other listener, kill these processes through kill-9; if you are not sure which processes are independent

You can consider stopping CRS and then pulling it up again, and then perform the next steps

Su-rootexport PATCH_DIR=/oracle/softwareexport PATCH_GRID_HOME=/grid/app/11.2.0.4/gridexport PATCH_ORACLE_HOME=/oracle/app/oracle/11.2.0.4/db_1export PSU_PATCH_ID=27282436/27107360# $PATCH_GRID_HOME/OPatch/opatch auto $PATCH_DIR/$PSU_PATCH_ID-oh $PATCH_GRID_HOME-ocmrf / tmp/ocm.rsp# $PATCH_ORACLE_HOME/OPatch/opatch auto $PATCH_DIR/$PSU_PATCH_ID-oh $PATCH_ORACLE_ HOME-ocmrf / tmp/ocm.rsp error processing

Opatch version check failed for oracle home / grid/app/11.2.0.4/grid

Opatch version check failed

ERROR: update the opatch version for the failed homes and retry

UtilSession failed: IPMRWServices::verifyPatchStorageDirectory () cannot read or write to / grid/app/11.2.0.4/grid/.patch_storage

OPatch failed with error code 73

CRMAPP3# [/] # cd / grid/app/11.2.0.4/grid/CRMAPP3# [/ grid/app/11.2.0.4/grid] # mkdir .patch _ storageCRMAPP3# [/ grid/app/11.2.0.4/grid] # chown grid:oinstall .patch _ storage

-the following script is used for patch rollback operation-

# $PATCH_GRID_HOME/OPatch/opatch auto $PATCH_DIR/$PSU_PATCH_ID-rollback-oh $PATCH_GRID_HOME-ocmrf / tmp/ocm.rsp# $PATCH_ORACLE_HOME/OPatch/opatch auto $PATCH_DIR/$PSU_PATCH_ID-rollback-oh $PATCH_ORACLE_HOME-ocmrf / tmp/ocm.rspsu-grid$ORACLE_HOME/OPatch/opatch lsinvsu-oracle$ORACLE_HOME/OPatch/opatch lsinv

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.