*項目aix5.3+hacmp5.4+oracle10gRAC

 總的配置過程分三步
    1.劃分磁碟給做RAC的兩台主機,在主機端識別磁碟陣列
    2.在兩台主機之間安裝HACMP,配置CONCURRENT VG
    3.在主機(aix)上配置 RAC

 

 

 

1.在DS4800 上準備空間給磁碟陣列

主機磁碟      lun(DS4800)       屬性
hdisk2       ma-ocr              RAC OCR
hdisk3       ma-vote            RAC VOTE
hdisk4       ma-data01       RAC DATA
hdisk5        ma-rman          RMAN使用
hdisk6        ma-arch1        第一個節點的歸檔
hdisk7        ma-arch2        第二個節點的歸檔

 一個盤一個盤指派,然後再在主機上識別
主機識別的命令為
cfgmgr -v

2.安裝配置HA

2.1 安裝HACMP 軟體
插入作業系統的光碟片，選擇從光碟片打補丁
lslpp -l bos.adt.lib bos.adt.libm bos.adt.syscalls bos.net.tcp.client bos.net.tcp.server 
lslpp -l bos.rte.SRC bos.rte.libc bos.rte.libcfg bos.rte.libcur bos.rte.libpthreads bos.rte.odm 　　　　        bos.data
lslpp -l bos.rte.lvm bos.clvm.enh
這些補丁包也要安裝，
特別注意，需要安裝這幾個軟體bos.data, * rsct.compat.basic.hacmp 2.5.0.0
從AIX第三張光碟安裝
插入 ha 的光碟，選擇從光碟安裝

掛載光碟片

/usr/sbin/mount -rv cdrfs /dev/cd0 /dvd
Smitty installp
選擇安裝ha軟體:
參照文檔　hacmp_manual.pdf 選擇以下的部分

   |   | * rsct.compat.basic.hacmp 2.5.0.0   第三張
  
注意：license aggree一定要選中。
 即可成功安裝ＨＡＣＭＰ　軟體。

2.配置HA

參考文檔Hacmp_mannul.pdf

記得配置  concurrentvg,(datafile ,controlfile,redo都對應了其中的lv)

 

 

3.安裝RAC ，參照 文檔 CookBook_V1.10gRAC_R1_AIX5L.pdf
安裝  CRS( 可以兩種選擇方式，本例採用的方式是 在concurrent vg上建立兩個lv,分別對應 ocr，vote )
3.1 安裝時間伺服器
參照下面的文檔
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||、、
AIX配置時間伺服器及客戶機實戰筆記
 xntpd是關於網路時間協議的守護進程，它遵循了網際網路時間伺服器的通用標準。在啟動 xntpd 時, xntpd 會讀取 /etc/ntp.conf 設定檔來確定網路中系統時鐘伺服器，以 ntp 伺服器的系統時間為標準，來調整原生系統時間。

可以用 ntpq 命令來顯示 xntpd 進程的內部變數。使用 ntp 時應注意，xntpd 伺服器和 xntpd 用戶端的時鐘不能相差超過1000秒。若有大於1000秒的位移，在用戶端啟動 xntpd 守護進程前，用 data 命令或 ntpdate 命令調整原生系統時間，使位移量在1000秒之內。然後啟動 xntpd.

1. 構造一個NTP環境的基本步驟:

1.1 設定NTP 伺服器(以192.168.5.2為例), 其它NTP客戶服務器以此伺服器的時間為準,與其進行時間同步.
1.1.1 編輯 /etc/ntp.conf 檔案, 內容如下:
----------------------------
#broadcastclient
server 127.127.1.0
driftfile /etc/ntp.drift
tracefile /etc/ntp.trace
----------------------------
請注意檔案中的 server 127.127.1.0 這一行, 此處的127.127.1.0 是一特殊的地址,表示NTP主伺服器是與自身的系統時鐘同步.

1.1.2 編輯好 /etc/ntp.conf後, 啟動xntpd守護進程
# startsrc -s xntpd
也可通過調用smitty , 使 xntpd 在以後重啟伺服器時能自動啟動.
# smitty xntpd

1.1.3 xntpd 狀態查詢 , 使用 #lssrc -ls xntpd
剛啟動xntpd時, sys peer 為 'insane', 表明xntpd還沒有完成同步, .
#lssrc -ls xntpd
Program name: --/usr/sbin/xntpd
Version: -------3
Leap indicator: 11 (Leap indicator is insane.) Sys peer: ------no peer, system is insane ...

等待 6 - 10 分鐘後, sys peer 就不再是 'insane' 了.
#lssrc -ls xntpd
Program name: --/usr/sbin/xntpd
Version: -------3
Leap indicator: 00 (No leap second today.) Sys peer: ------127.127.1.0 ...

1.2. NTP用戶端的設定
1.2.1 編輯 NTP 用戶端上的 /etc/ntp.conf檔案, 內容如下:
----------------------------
#broadcastclient
server 192.168.5.2
driftfile /etc/ntp.drift
tracefile /etc/ntp.trace
----------------------------
其中的 server 192.168.5.2 表明, 此用戶端與IP地址為 192.168.5.2 的NTP伺服器進行時間同步.

1.2.2 在NTP用戶端啟動xntpd守護進程
# startsrc -s xntpd
也可通過調用smitty , 使 xntpd 在以後重啟伺服器時能自動啟動.
# smitty xntpd

1.2.3 查詢xntpd的狀態
當 system peer 不為 'insane' 時, 表明用戶端已與伺服器端成功地進行了同步.
# lssrc -ls xntpd
Program name: --/usr/sbin/xntpd
Version: -------3
Leap indicator: 00 (No leap second today.) Sys peer: ------192.168.5.2 ...

1.3. NTP用戶端查詢NTP伺服器
ntp用戶端使用 ntpdate 命令來確認是否可用指定的 ntp 伺服器進行時間同步。
命令的結果會顯示用戶端與伺服器的時間位移。
#ntpdate -d 192.168.5.2
...
18 Jan 15:49:57 ntpdate[98462]: adjust time server 192.168.5.2 offset -0.000868
2 sec

若時間間隔大於1000秒，使用ntpdate 進行手工調整, 如：
#date
Thu Jan 18 15:52:00 BEIST 2007

#ntpdate 192.168.5.2
18 Jan 15:49:57 ntpdate[23832]: step time server 9.185.43.189 offset 23.40260
7 sec

#date
Thu Jan 18 15:52:00 BEIST 2007
完成上述操作後 ntp 用戶端與 ntp 伺服器系統時鐘完成同步，ntp 用戶端得到了新的系統時間。

查看同步的時間間隔（poll）
# xntpdc -c peers
    remote           local    st poll reach   delay offset disp
=======================================================================
*192.168.5.2     192.168.7.1    4 64   377 0.00230 -0.000426 0.00026
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||

3.2.在concurrent vg 上建立lv,並修改lv 屬主為 oracle:dba ，許可權為 660

3.3 安裝 CRS
    解壓縮 patch 6718715 執行 rootpre.sh，在兩個節點都要執行
    安裝過程中曾經出現錯誤
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Expecting the CRS daemons to be up within 600 seconds.
Failure at final check of Oracle CRS stack.
10
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
按照metalink 文檔    725878.1  ，

通過下面的步驟來驗證是否是 init.d的問題
This can be verified by adding a simple entry in /etc/inittab:
test:2:once:/usr/bin/echo "HELLO TEST" > /tmp/test.log
run "init q" as root user. If the init is working, then there should be a file /tmp/test.log generated.

通過下面步驟來解決 init.d起不來的問題

1. Starting the script install_assist (AIX GUI utility Installation Assistance)
2. Updating for example the date, then exit install_assist properly
3. Reboot the system
After that daemon process in /etc/inittab started, CRS installation completed.

     3.4 安裝DB

附錄; metalink相關的內容

TIP:           Click help for a detailed explanation of this page.
        書籤         轉到末尾

主題:         Root.sh failed at Failure at final check of Oracle CRS stack 10
          文檔 ID:         725878.1         類型:         PROBLEM
          上次修訂日期:         16-JAN-2009         狀態:         PUBLISHED

In this Document
  Symptoms
  Changes
  Cause
  Solution
  References

Applies to:
Oracle Server - Enterprise Edition - Version: 10.2.0.1
This problem can occur on any platform.
Symptoms

2 node RAC, performing CRS 10.2.0.1 installation, failure at root.sh, CRS stack not started

WARNING: directory '/oracle' is not owned by root
Checking to see if Oracle CRS stack is already configured
Setting the permissions on OCR backup directory
Setting up NS directories
Oracle Cluster Registry configuration upgraded successfully
WARNING: directory '/oracle' is not owned by root
Successfully accumulated necessary OCR keys.
Using ports: CSS=49895 CRS=49896 EVMC=49898 and EVMR=49897.
node <nodenumber>: <nodename> <private interconnect name> <hostname>
node 1: ndb1 ndb1-rac ndb1
node 2: ndb2 ndb2-rac ndb2
Creating OCR keys for user 'root', privgrp 'system'..
Operation successful.
Now formatting voting device: /dev/rhdisk3
Format of 1 voting devices complete.
Startup will be queued to init within 30 seconds.
Adding daemons to inittab
Adding daemons to inittab
Expecting the CRS daemons to be up within 600 seconds.
Failure at final check of Oracle CRS stack.
10

Checking "ps -ef | grep init" during this 600 seconds period, see there is no crs related init processes, eg: init.crsd/init.evmd/init.cssd running. When no processes are detected, then this case apply.
Changes
New installation
Cause

This particular case is caused by the OS init system does not working.

" Failure at final check of Oracle CRS stack.
10"
means CRS daemon did not startup during 600 seconds period.

In root.sh script, it will add CRS related entry in /etc/inittab, run "init q" and expect those 3 CRS related daemon processes to start. With init system problem, none of these daemon processes spawned, this caused CRS process startup failure as they rely on init daemon process to start first.

This can be verified by adding a simple entry in /etc/inittab:
test:2:once:/usr/bin/echo "HELLO TEST" > /tmp/test.log
run "init q" as root user. If the init is working, then there should be a file /tmp/test.log generated.
Solution

Please consult with system administrator for init issue.

e.g. here the solution reference only valid for AIX platform:
1. Starting the script install_assist (AIX GUI utility Installation Assistance)
2. Updating for example the date, then exit install_assist properly
3. Reboot the system
After that daemon process in /etc/inittab started, CRS installation completed.

For other platforms, please consult your system admin or vendor for its solution.
References
Note 761259.1 - How to Check the Clusterware Processes via the ps Command
Keywords
INSTALLATION~FAILS ; RAC ; INIT ; PROCESS~STARTUP ;
Help us improve our service. Please email us your comments for this document. .