一、配置oracle使用者等效性
1、建立等效性檔案
cd;
mkdir .ssh; cd .ssh
ssh-keygen
–t
rsa
ssh-keygen
–t
dsa
cat
id_rsa.pub >>
authorized_keys --記住這些檔案名(man
ssh搜尋_keys能找到)
cat
id_dsa.pub >>
authorized_keys
打開這個檔案看下：
看樣子應該是将通路每個節點的兩種密鑰(rsh、dss)儲存在這個檔案中了，要合并下所有節點的這個檔案。
這個要是節點多了，比較麻煩，容易漏，以後要寫個腳本
2、等效性驗證
ssh
node1 date
ssh
node1-priv date
ssh
node1-vip date (這個vipca後再執行)
二、/xxx/runInstall or /xxx/runInstall
--ingoreSysPreReqs
執行到提示root執行腳本時，第一個是賦權限啥的，/opt/oracle/oraInventory/orainstRoot.sh
1、第一次執行/opt/oracle/product/10.2.0/crs/root.sh
Failed to upgrade Oracle Cluster Registry configuration
=>
see
/opt/oracle/product/10.2.0/crs/log/node1/client/ocrxxx.log
Oracle
Database 10g CRS Release 10.2.0.1.0 Production Copyright 1996, 2005
Oracle. All rights reserved.
2012-04-21
13:54:02.283: [ OCRCONF][2959764352]ocrconfig starts...
2012-04-21
13:54:02.284: [ OCRCONF][2959764352]Upgrading OCR data
2012-04-21
13:54:02.457: [ OCRCONF][2959764352]OCR already in current
version.
2012-04-21
13:54:02.492: [ OCRCONF][2959764352]Failed to call clsssinit
(21)
2012-04-21
13:54:02.492: [ OCRCONF][2959764352]Failed to make a backup copy of
OCR
2012-04-21
13:54:02.492: [ OCRCONF][2959764352]Exiting
[status=failed]...
=>原因：ocr(/dev/raw/raw5中有上次執行/opt/oracle/product/10.2.0/crs/root.sh
腳本的資料，需要手動清空一下)
dd
if=/dev/zero of=/dev/raw/raw5 bs=10M count=10
2、第二次/opt/oracle/product/10.2.0/crs/root.sh
WARNING:
directory '/opt/oracle/product/10.2.0' is not owned by root
WARNING:
directory '/opt/oracle/product' is not owned by root
WARNING:
directory '/opt/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 '/opt/oracle/product/10.2.0' is not owned by root
WARNING:
directory '/opt/oracle/product' is not owned by root
WARNING:
directory '/opt/oracle' is not owned by root
Successfully
accumulated necessary OCR keys.
Using
ports: CSS=49895 CRS=49896 EVMC=49898 and EVMR=49897.
node
:
interconnect name>
node
1: node1 node1-priv node1
Creating
OCR keys for user 'root', privgrp 'root'..
Operation
successful.
Now
formatting voting device: /dev/raw/raw7
Format
of 1 voting devices complete.
Startup
will be queued to init within 90 seconds.
Adding
daemons to inittab
Expecting
the CRS daemons to be up within 600 seconds.
CSS
is active on these nodes.
node1
CSS
is active on all nodes.
Waiting
for the Oracle CRSD and EVMD to start
Oracle
CRS stack installed and running under init(1M)
Running
vipca(silent) for configuring nodeapps
/opt/oracle/product/10.2.0/crs/jdk/jre//bin/java:
error while loading shared libraries: libpthread.so.0: cannot open
shared object file: No such file or directory
=>因10.2.0.1的vipca腳本是為了适應redhat4的某些版本的，而redhat4有一些相關的bug，到了後期版本已經修複，
是以注釋掉相關内容
/opt/oracle/product/10.2.0/crs/bin/vipca
#LD_ASSUME_KERNEL=2.4.19
#export
LD_ASSUME_KERNEL
=>
LD_ASSUME_KERNEL=
export
LD_ASSUME_KERNEL
改完後，root再執行
$CRS_HOME/bin/vipca 彈出一個界面，選擇好後下一步，填入相應的vipip
3、以下是安裝日志(/opt/oracle/product/10.2.0/crs/cfgtoollogs/oui/installActions2012-04-21_01-23-19PM.log)中報的錯：
證明是vipca腳本的問題，用上面的方法解決後重新驗證一把，下一步，exit就完成了
Note:
Do not run the scripts simultaneously on the listed
nodes.
INFO:
Starting to execute configuration assistants
INFO:
Command = /opt/oracle/product/10.2.0/crs/bin/racgons add_config
node1:6200
INFO:
Configuration assistant "Oracle Notification Server Configuration
Assistant" succeeded
INFO:
Command = /opt/oracle/product/10.2.0/crs/bin/oifcfg setif -global
eth0/192.168.136.0:cluster_interconnect
eth1/192.168.56.0:public
INFO:
Configuration assistant "Oracle Private Interconnect Configuration
Assistant" succeeded
INFO:
Command = /opt/oracle/product/10.2.0/crs/bin/cluvfy stage -post
crsinst -n node1
Performing
post-checks for cluster services setup
Checking
node reachability...
Node
reachability check passed from node "node1".
Checking
user equivalence...
User
equivalence check passed for user "oracle".
Checking
Cluster manager integrity...
Checking
CSS daemon...
Daemon
status check passed for "CSS daemon".
Cluster
manager integrity check passed.
Checking
cluster integrity...
Cluster
integrity check passed
Checking
OCR integrity...
Checking
the absence of a non-clustered configuration...
All
nodes free of non-clustered, local-only configurations.
Uniqueness
check for OCR device passed.
Checking
the version of OCR...
OCR
of correct Version "2" exists.
Checking
data integrity of OCR...
Data
integrity check for OCR passed.
OCR
integrity check passed.
Checking
CRS integrity...
Checking
daemon liveness...
Liveness
check passed for "CRS daemon".
Checking
daemon liveness...
Liveness
check passed for "CSS daemon".
Checking
daemon liveness...
Liveness
check passed for "EVM daemon".
Checking
CRS health...
CRS
health check passed.
CRS
integrity check passed.
Checking
node application existence...
Checking
existence of VIP node application (required)
Check
failed.
Check
failed on nodes:
node1
Checking
existence of ONS node application (optional)
Check
ignored.
Checking
existence of GSD node application (optional)
Check
ignored.
Post-check
for cluster services setup was unsuccessful on all the nodes.
Command
= /opt/oracle/product/10.2.0/crs/bin/cluvfy has failed
INFO:
Configuration assistant "Oracle Cluster Verification Utility"
failed
-----------------------------------------------------------------------------
***
Starting OUICA ***
Oracle
Home set to /opt/oracle/product/10.2.0/crs
Configuration
directory is set to /opt/oracle/product/10.2.0/crs/cfgtoollogs. All
xml files under the directory will be processed
INFO:
The
"/opt/oracle/product/10.2.0/crs/cfgtoollogs/configToolFailedCommands"
script contains all commands that failed, were skipped or were
cancelled. This file may be used to run these configuration
assistants outside of OUI. Note that you may have to update this
script with passwords (if any) before executing the same.
-----------------------------------------------------------------------------
SEVERE:
OUI-25031:Some of the configuration assistants failed. It is
strongly recommended that you retry the configuration assistants at
this time. Not successfully running any "Recommended" assistants
means your system will not be correctly configured.
1.
Check the Details panel on the Configuration Assistant Screen to
see the errors resulting in the failures.
2.
Fix the errors causing these failures.
3.
Select the failed assistants and click the 'Retry' button to retry
them.