Monday 12 May, 2008 - 22:48
Completed the pre-installation customisation of richmond2. Adding richmond2 to the richmond cluster.
Using the procedure on p.10-3 of Oracle® Clusterware and Oracle RAC Administration and Deployment Guide
$ cd /u00/crs/oracle/product/10/app
$ ./addNode.sh
On richmond2,
$ su -
# /u00/app/oracle/oraInventory/orainstRoot.sh
Changing permissions of /u00/app/oracle/oraInventory to 770.
Changing groupname of /u00/app/oracle/oraInventory to oinstall.
The execution of the script is complete
On richmond1,
$ su -
# /u00/crs/oracle/product/10/app/install/rootaddnode.sh
clscfg: EXISTING configuration version 3 detected.
clscfg: version 3 is 10G Release 2.
Attempting to add 1 new nodes to the configuration
Using ports: CSS=49895 CRS=49896 EVMC=49898 and EVMR=49897.
node :
node 2: richmond2 richmond2-priv richmond2
Creating OCR keys for user 'root', privgrp 'root'..
Operation successful.
/u00/crs/oracle/product/10/app/bin/srvctl add nodeapps -n richmond2 -A richmond2-vip/255.255.255.0/eth0 -o /u00/crs/oracle/product/10/app
Caught cluster exception oracle.ops.mgmt.cluster.ClusterException: PRKC-1044 : Failed to check remote command execution setup for node richmond2 using shells /usr/bin/ssh and /usr/bin/rsh
richmond2: Connection refused
Found a metalink hit (PRKC-1044) at "PRKC-1044 : Failed To Check Remote Command'' While Run Rootaddnode.Sh (Note:392415.1). The solution is to:
Temporarily define an empty rsa and dsa passphrase for oracle user ssh configuration before add node operation, so that no prompt of "Enter passphrase for key '/home/oracle/.ssh/id_rsa' will show up in any newly spawned oracle session.
This will allow rootaddnode.sh to finish without error.
I managed to stuff up the authorized_keys file on richmond2.