Oracle Rac opatch auto的時候為什麼不打到Rac database home上，opatchrac

Oracle Rac opatch auto的時候為什麼不打到Rac database home上，opatchrac
先交代環境：作業系統：AIX 7.1Oracle版本：Oracle Rac 11.2.0.3之前打了11.2.0.3.9的補丁集，Rac裝上還沒正式用，所以就乾脆再打到最新的11.2.0.3.11補丁集。
今日在前段時間新裝的兩套Rac打最新的psu，同樣使用opatch auto的方式來打psu，但是其中一套Rac是連同Rac和Grid一起patch，而另一套是只patch Grid的補丁集。很鬱悶，兩套rac的crsconfig_params是基本一樣的，兩套Rac的相關配置都是我一手安裝配置的，為什麼會有如此多偏差？
如下是Rac和Grid一同patch的那套Rac：root@HDB01:/oraapp/oracle/backup>/oraapp/grid/gridhome/OPatch/opatch auto /install/psu -ocmrf /home/grid/grid.rspExecuting /oraapp/grid/gridhome/perl/bin/perl /oraapp/grid/gridhome/OPatch/crs/patch11203.pl -patchdir /install -patchn psu -ocmrf /home/grid/grid.rsp -paramfile /oraapp/grid/gridhome/crs/install/crsconfig_params
This is the main log file: /oraapp/grid/gridhome/cfgtoollogs/opatchauto2014-09-28_15-07-56.log
This file will show your detected configuration and all the steps that opatchauto attempted to do on your system:/oraapp/grid/gridhome/cfgtoollogs/opatchauto2014-09-28_15-07-56.report.log
2014-09-28 15:07:56: Starting Clusterware Patch SetupUsing configuration parameter file: /oraapp/grid/gridhome/crs/install/crsconfig_params
Stopping RAC /oraapp/oracle/product/11.2.0/dbhome_1 ...Stopped RAC /oraapp/oracle/product/11.2.0/dbhome_1 successfully
patch /install/psu/17592127/custom/server/17592127  apply successful for home  /oraapp/oracle/product/11.2.0/dbhome_1 patch /install/psu/18522512  apply successful for home  /oraapp/oracle/product/11.2.0/dbhome_1 
Stopping CRS...Stopped CRS successfully
patch /install/psu/17592127  apply successful for home  /oraapp/grid/gridhome patch /install/psu/18522512  apply successful for home  /oraapp/grid/gridhome 
Starting CRS...CRS-4123: Oracle High Availability Services has been started.
Starting RAC /oraapp/oracle/product/11.2.0/dbhome_1 ...Started RAC /oraapp/oracle/product/11.2.0/dbhome_1 successfully
opatch auto succeeded.root@DB01:/oraapp/oracle/backup>su - grid

如下是只patch 了 Grid的那套Rac：root@ODB01:/install/psu>/oraapp/grid/gridhome/OPatch/opatch auto /install/psu -ocmrf /home/grid/grid.rspExecuting /oraapp/grid/gridhome/perl/bin/perl /oraapp/grid/gridhome/OPatch/crs/patch11203.pl -patchdir /install -patchn psu -ocmrf /home/grid/grid.rsp -paramfile /oraapp/grid/gridhome/crs/install/crsconfig_params
This is the main log file: /oraapp/grid/gridhome/cfgtoollogs/opatchauto2014-09-28_15-08-19.log
This file will show your detected configuration and all the steps that opatchauto attempted to do on your system:/oraapp/grid/gridhome/cfgtoollogs/opatchauto2014-09-28_15-08-19.report.log
2014-09-28 15:08:19: Starting Clusterware Patch SetupUsing configuration parameter file: /oraapp/grid/gridhome/crs/install/crsconfig_params
Stopping CRS...Stopped CRS successfully
patch /install/psu/17592127  apply successful for home  /oraapp/grid/gridhome patch /install/psu/18522512  apply successful for home  /oraapp/grid/gridhome 
Starting CRS...CRS-4123: Oracle High Availability Services has been started.
opatch auto succeeded.root@ODB01:/install/psu>    
通過查看Mos文檔：（Doc ID 1479651.1）得知，HDB中是有資料庫存在的（即通過dbca等形式建立資料庫的），而ODB上並沒有資料庫DB的存在。ps：這時突然想起來，前段時間確實在HDB上建立過資料庫，並做了一些資料移轉做測試。。。（愚鈍啊） opatch的時候oracle在發現沒有資料庫database註冊到OCR中，因此只是patch了Grid。
如下：通過Mos提供的命令發現HDB上CRS中確實有ora.hdb.db的存在：grid@HDB01:/home/grid>crsctl stat res -p -w "TYPE = ora.database.type"|egrep '^NAME|^ORACLE_HOME' NAME=ora.hdb.dbORACLE_HOME=/oraapp/oracle/product/11.2.0/dbhome_1ORACLE_HOME_OLD=NAME=ora.hdb.dbORACLE_HOME=/oraapp/oracle/product/11.2.0/dbhome_1ORACLE_HOME_OLD=grid@HDB01:/home/grid>
而在ODB上，次命令下去無任何輸出，查看一下/etc/oratab檔案，確實未發現除ASM之外的其他資料庫：grid@ODB01:/home/grid>crsctl stat res -p -w "TYPE = ora.database.type"|egrep '^NAME|^ORACLE_HOME'grid@SRMBODB01:/home/grid>
可以通過以下命令來另外給Rac patch 補丁：As root user, execute the following command:opatch auto <UNZIPPED_PATCH_LOCATION> -oh <DATABASE_HOME> -ocmrf <ocm response file>
2節點oracle rac 資料庫，在rac1宕機後，rac2因為業務量太大不可以及時響應

1、手動，查session找出處理時間最長的事務，然後看看具體是什麼事務。根據事務執行的sql定位問題；
2、執行ADDM並查看報告，根據報告分析處理掛起的原因。

這個很多原因，跟是不是RAC關係不大。
 
oracle安裝rac的時不可以解析san名

scan name需要在/etc/hosts檔案中聲明。
如果使用了dns伺服器，也需要有相關的正向反向解析配置。