HPUX11.31下安裝11GRAC遇到的問題

tonyzhou_cn發表於2012-12-20
UX
1、[INS-40718] Single Client Access Name (SCAN):bydb-cluster-scan could not be resolved.
Cause - The name you provided as the SCAN could not be resolved using TCP/IP host name lookup. 
Action - Provide name to use for the SCAN for which the domain can be resolved.
這是因為/etc/hosts配置的scan和介面中指定的scan name不一致引起
hosts檔案配置:
192.168.201.16   rac-scan.localdomain rac-scan
所以介面中的SCAN Name要是rac-scan才不會報錯。

2、incorrect setting for minor number
在安裝oracle 11g rac的時候會報錯如下：
Checking settings of device file "/dev/async"
  Node Name     Available                 Comment                
  ------------  ------------------------  ------------------------
  racdb2        yes                       failed (incorrect setting for minor number.)
  racdb1        yes                       failed (incorrect setting for minor number.)
查了下support，得知：
Minor number   Description
0x0    This is the HP-UX default value for /dev/async
0x4    Enable disc device timeouts to complete with an error code rather than retrying forever. This setting is necessary                for application-level disc mirroring, so as to avoid the situation where the application waits forever for a failed disc            device to be repaired. Oracle RDBMS users should enable this feature when Automatic Storage Management      mirroring/replication (internal redundancy) is used. SGA will be locked in memory. 
0x100    Enable on-demand locking of memory pages by async driver when asyncdsk_open(2) is called. A low-overhead      routine is then used to lock a page into memory during I/O operations.
    On-demand locking is critically important when using Oracle's Automatic Memory Management feature (the use of
    MEMORY_TARGET
    in the
    init.ora
    file to control memory usage). RDBMS deployments utilizing dynamic nPar or dynamic vPar features should also      configure on-demand locking.
    More traditional RDBMS deployments can consider on-demand locking in light of its more obvious effects.      Generally speaking, RDBMS startup will be quicker because the complete SGA is not locked into memory       immediately. However, some instances will experience a slight run-time performance penalty with on-demand      locking as memory pages are dynamically locked/unlocked for each I/O request.
    
0x104     This is a combination of 0x100 and 0x4. Both the features are enabled
顯然解決辦法：
rm /dev/async
/sbin/mknod /dev/async c 101 0x104
chmod 666 /dev/async
非同步io    (http://blog.csdn.net/renfengjun/article/details/7972065)  其他人的解答
兩個節點都需要設定，不然檢查過不去。
XXJ-02#[/]ll /dev/async
crw-rw-rw-  1 bin        bin        101 0x000000 Aug 28 10:42 /dev/async
需要設定
XXJ-02#[/]rm /dev/async
XXJ-02#[/] /sbin/mknod /dev/async c 101 0x4 
XXJ-02#[/]chmod 666 /dev/async
XXJ-02#[/]ll /dev/async
crw-rw-rw-  1 root       sys        101 0x000004 Aug 28 14:14 /dev/async
如果這裡沒有發現裝置，可以直接使用mknod命令建立
./runcluvfy.sh stage -pre crsinst -n racdb1,racdb2 -fixup -verbose
Checking settings of device file "/dev/async"
  Node Name     Available                 Comment                
  ------------  ------------------------  ------------------------
  racdb2        yes                       passed                 
  racdb1        yes                       passed                 
Result: Check for settings of device file "/dev/async" passed.

3、Check: User equivalence for user "grid"
  Node Name                             Status                 
  ------------------------------------  ------------------------
  bydb2                                 passed                 
  bydb1                                 failed                 
Result: PRVF-4007 : User equivalence check failed for user "grid"
將/home/grid/.ssh/known_hosts 清空，解決
參考故障：
linux中ssh登入Permanently added (RSA) to the list of known&nb
[root@www]# ssh
2 The authenticity of host 'xxx.xxx.xxx.xxx' can't be established.
3 RSA key fingerprint is f4:d0:1a:9c:09:65:78:71:25:33:79:c2:d5:aa:0b:c1.
4 Are you sure you want to continue connecting (yes/no)? yes
5 Warning: Permanently added 'xxx.xxx.xxx.xxx' (RSA) to the list of known hosts.
6 Permission denied (publickey,gssapi-with-mic,password).
1）、可以把~/.ssh/known_hosts清除
2）、如果還是不行
修 改/etc/ssh/sshd-config檔案，將其中的PermitRootLogin no修改為yes，PubkeyAuthentication yes修改為no，AuthorizedKeysFile .ssh/authorized_keys前面加上#遮蔽掉，PasswordAuthentication no修改為yes就可以了。
同時設定 UseDNS no，最後儲存修改，重啟sshd服務再連線這個問題就可以解決了。等同於第四步註釋掉DNS
3）、如果還是有問題，那可以用下面的方式解決：
用命令 ssh -l username hostname
 1）、這個是ssh安全認證是的一個RSA認證。此處必須選擇yes才能連線。第一次yes後，他會詢問你是否永久把這個RSA認證加入本地，選擇yes後，以後不會再出現提醒。每次登陸只需要輸入密碼即可。
 2）、也可以不用輸入1中的yes，但是需要修改本機配置。
4）有能配置了DNS，沒有配的話，沒有下面兩個檔案。
在這裡兩個檔案裡註釋掉相關資訊
linux
/etc/ nsswitch.conf
/etc/resolv.conf
HP-UX 配置DNS伺服器引數檔案：
/etc/ nsswitch.conf
/etc/resolv.conf
 AIX配置DNS伺服器引數檔案
/etc/netsvc.conf
/etc/resolv.conf          ##如沒有可以手動建立
修改server上/etc/nsswitch.conf中hosts為hosts： files

4、配置SSH發現不成功，經檢查發現可能是檔案許可權問題。
修改/home/oracle的許可權為0755。
然後修改~/.ssh/的許可權為0700
修改其他檔案的許可權如下：
$ ls -l ~/.ssh
total 64
-rw-r--r--   1 oracle     oinstall       788 Jun 21 11:44 authorized_keys
-rw-------   1 oracle     oinstall      1675 Jun 21 11:40 id_rsa
-rw-r--r--   1 oracle     oinstall       394 Jun 21 11:40 id_rsa.pub
-rw-r--r--   1 oracle     oinstall      1326 Jun 21 11:39 known_hosts
然後測試成功。

5、如何處理11gR2 RAC下oc4j和gsd服務為OFFLINE狀態？
http://blog.163.com/xiaohan_008/blog/static/126347420129994358263/
$ crs_stat -t
Name           Type           Target    State     Host       
------------------------------------------------------------
ora.CRSDATA.dg ora....up.type ONLINE    ONLINE    bydb1      
ora.DATA01.dg  ora....up.type ONLINE    ONLINE    bydb1      
ora....CKUP.dg ora....up.type ONLINE    ONLINE    bydb1      
ora....ER.lsnr ora....er.type ONLINE    ONLINE    bydb1      
ora....N1.lsnr ora....er.type ONLINE    ONLINE    bydb1      
ora.asm        ora.asm.type   ONLINE    ONLINE    bydb1      
ora.bydb.db    ora....se.type OFFLINE   OFFLINE              
ora....SM1.asm application    ONLINE    ONLINE    bydb1      
ora....B1.lsnr application    ONLINE    ONLINE    bydb1      
ora.bydb1.gsd  application    OFFLINE   OFFLINE              
ora.bydb1.ons  application    ONLINE    ONLINE    bydb1      
ora.bydb1.vip  ora....t1.type ONLINE    ONLINE    bydb1      
ora....SM2.asm application    ONLINE    ONLINE    bydb2      
ora....B2.lsnr application    OFFLINE   OFFLINE              
ora.bydb2.gsd  application    OFFLINE   OFFLINE              
ora.bydb2.ons  application    ONLINE    ONLINE    bydb2      
ora.bydb2.vip  ora....t1.type ONLINE    ONLINE    bydb2      
ora.cvu        ora.cvu.type   ONLINE    ONLINE    bydb1      
ora.gsd        ora.gsd.type   OFFLINE   OFFLINE              
ora....network ora....rk.type ONLINE    ONLINE    bydb1      
ora.oc4j       ora.oc4j.type  OFFLINE   OFFLINE              
ora.ons        ora.ons.type   ONLINE    ONLINE    bydb1      
ora.scan1.vip  ora....ip.type ONLINE    ONLINE    bydb1      
$ lsnrctl start
那麼，是我們的RAC配置有問題嗎?這兩類服務沒有ONLINE會不會影響RAC資料庫呢？我們又該如何啟動這些服務呢？
        其實，我們的RAC配置是沒有問題的，也不會影響資料庫正常執行。在預設情況下，其中的ora.gsd服務狀態是OFFLINE狀態，我們可不予理會，除非需要在11g Cluster上配置Oracle 9iR2的RAC。但凡以grid使用者執行crs_stat -t命令，看到Target和State這兩列的狀態均為OFFLINE，我們均可忽略。但是，我們該如何使之啟動呢？
 1、 啟動ora.oc4j服務：
$ srvctl start oc4j 
OC4J could not be started
PRCR-1079 : Failed to start resource ora.oc4j
CRS-2501: Resource 'ora.oc4j' is disabled
$ srvctl enable oc4j -h
Enable OC4J instance for Oracle Clusterware management.
Usage: srvctl enable oc4j [-n ] [-v]
    -n            Node name
    -v                       Verbose output
    -h                       Print usage
$ srvctl enable oc4j   
$ srvctl start oc4j -v
OC4J has been started
2、 啟動ora.gsd服務：
$ srvctl status nodeapps 
VIP bydb1_vip is enabled
VIP bydb1_vip is running on node: bydb1
VIP bydb2_vip is enabled
VIP bydb2_vip is running on node: bydb2
Network is enabled
Network is running on node: bydb1
Network is running on node: bydb2
GSD is disabled
GSD is not running on node: bydb1
GSD is not running on node: bydb2
ONS is enabled
ONS daemon is running on node: bydb1
ONS daemon is running on node: bydb2
$ srvctl enable nodeapps -g
$ srvctl status nodeapps 
VIP bydb1_vip is enabled
VIP bydb1_vip is running on node: bydb1
VIP bydb2_vip is enabled
VIP bydb2_vip is running on node: bydb2
Network is enabled
Network is running on node: bydb1
Network is running on node: bydb2
GSD is enabled
GSD is not running on node: bydb1
GSD is not running on node: bydb2
ONS is enabled
ONS daemon is running on node: bydb1
ONS daemon is running on node: bydb2
然後，啟動GSD服務 --------------因為沒有配置GNS所以不能啟動
$ srvctl start nodeapps -g
PRCR-1079 : Failed to start resource ora.gsd
CRS-5016: Process "/oracle/ora11g/crs_home/bin/gsdctl" spawned by agent "/oracle/ora11g/crs_home/bin/oraagent.bin" for action "start" failed: details at "(:CLSN00010:)" in "/oracle/ora11g/crs_home/log/bydb1/agent/crsd/oraagent_grid/oraagent_grid.log"
CRS-5016: Process "/oracle/ora11g/crs_home/bin/gsdctl" spawned by agent "/oracle/ora11g/crs_home/bin/oraagent.bin" for action "start" failed: details at "(:CLSN00010:)" in "/oracle/ora11g/crs_home/log/bydb2/agent/crsd/oraagent_grid/oraagent_grid.log"
CRS-2674: Start of 'ora.gsd' on 'bydb1' failed
CRS-2674: Start of 'ora.gsd' on 'bydb2' failed
$ srvctl start nodeapps
PRCR-1079 : Failed to start resource ora.gsd
CRS-5016: Process "/oracle/ora11g/crs_home/bin/gsdctl" spawned by agent "/oracle/ora11g/crs_home/bin/oraagent.bin" for action "start" failed: details at "(:CLSN00010:)" in "/oracle/ora11g/crs_home/log/bydb2/agent/crsd/oraagent_grid/oraagent_grid.log"
CRS-5016: Process "/oracle/ora11g/crs_home/bin/gsdctl" spawned by agent "/oracle/ora11g/crs_home/bin/oraagent.bin" for action "start" failed: details at "(:CLSN00010:)" in "/oracle/ora11g/crs_home/log/bydb1/agent/crsd/oraagent_grid/oraagent_grid.log"
CRS-2674: Start of 'ora.gsd' on 'bydb2' failed
CRS-2674: Start of 'ora.gsd' on 'bydb1' failed
PRKO-2421 : Network resource is already started on node(s): bydb1,bydb2
PRKO-2420 : VIP is already started on node(s): bydb1
PRKO-2420 : VIP is already started on node(s): bydb2
PRKO-2422 : ONS is already started on node(s): bydb1,bydb2

來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/27038344/viewspace-751391/，如需轉載，請註明出處，否則將追究法律責任。

相關文章