Oracle RAC升級補丁及中間的錯誤提示

發布時間: 2012/8/23 17:48:36

tail -f /var/log/messages
/u01/app/Oracle/product/10.2.0/db_1/OPatch/opatch
/u01/app/Oracle/product/10.2.0/crs_1/OPatch/opatch

ORA_CRS_HOME=/u01/app/Oracle/product/10.2.0/crs_1
-

Oracle_HOME=/u01/app/oracle/product/10.2.0/db_1增加CSS
/u01/app/oracle/product/10.2.0/crs_1/bin/crsctl add css votedisk /u02/oradata/orcl/CSSFile3 -force

custom/scripts/prerootpatch.sh -crshome /u01/app/Oracle/product/10.2.0/crs_1 -crSUSEr oracle
custom/scripts/prepatch.sh -crshome /u01/app/Oracle/product/10.2.0/crs_1

/u01/app/Oracle/product/10.2.0/db_1/OPatch/opatch apply -local -oh /u01/app/oracle/product/10.2.0/crs_1
/u01/app/oracle/product/10.2.0/db_1/OPatch/opatch apply custom/server/4896338 -local -oh /u01/app/oracle/product/10.2.0/db_1

[Oracle@racdb4 4896338]$ /u01/app/oracle/product/10.2.0/db_1/OPatch/opatch apply custom/server/4896338 -local -oh /u01/app/oracle/product/10.2.0/db_1
Invoking OPatch 10.2.0.4.9
Oracle Interim Patch Installer version 10.2.0.4.9
Copyright (c) 2009, Oracle Corporation. All rights reserved.

Oracle Home       : /u01/app/oracle/product/10.2.0/db_1
Central Inventory : /u01/app/Oracle/oraInventory
   from           : /etc/oraInst.loc
OPatch version    : 10.2.0.4.9
OUI version       : 10.2.0.1.0
OUI location      : /u01/app/Oracle/product/10.2.0/db_1/oui
Log file location : /u01/app/Oracle/product/10.2.0/db_1/cfgtoollogs/opatch/opatch2010-01-14_17-32-49PM.log
Patch history file: /u01/app/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/opatch_history.txt
ApplySession applying interim patch '4896338' to OH '/u01/app/oracle/product/10.2.0/db_1'
Running prerequisite checks...
Prerequisite check "CheckPatchApplicableOnCurrentPlatform" failed.
The details are:
Patch ( 4896338 ) is not applicable on current platform.
Platform ID needed is : 226
Platform IDs supported by patch are: 46
ApplySession failed during prerequisite checks: Prerequisite check "CheckPatchApplicableOnCurrentPlatform" failed.
System intact, OPatch will not attempt to restore the system
OPatch failed with error code 74