poniedziałek, 18 lutego 2008

Oracle CRS 10g running on Sun Solaris 10

Instead of rewriting cofiguration instructions, i'd like to shed some light on potential problems you may hit during CRS installation process on SUN Solaris 10 64-bit operating system.

Let's start from the begining..

Folowing documentation provided by Oracle Corporation, you set up all preinstallation parameters required to set up Clusterware software ( kernel parameters, environment variables and many other mentioned on manual pages) and you think you're done with operating system preparation? Unfortunately it is barely truth..

Oracle installer will search for SSC/SCP software in hardcoded locations, which are simply not avaliable in standard Sun Solaris 10 installation.
You have to create symlinks:
/usr/local/bin/ssh -> /usr/bin/ssh
/usr/local/bin/scp -> /usr/bin/scp

Than, if your system is 64-bit capable, you have to "tell" Oracle Universal Installer to prepare 64-bit libraries by setting up:

crle -64 -u -l $CRS_HOME/lib

Otherwise you may hit the problem with libclntsh.so. Of course it's corrigible, and it's not much complicated:

export ORACLE_HOME="/oracle/crs/"
cd $ORACLE_HOME/bin
Edit ./genclntsh file and replace:
LD="ld -m -Dfiles -i -G -z text -L${ORACLE_HOME}/${LIB}"
with:
LD="ld -m -Bsymbolic -i -G -z text -L${ORACLE_HOME}/${LIB}"

Run "relink all" again.
./genclntsh

/bin/clscfg -install -nn $CRS_NODE_NAME_LIST -pn $CRS_PRIVATE_NAME_LIST \
$HOSTNAMES_ARGS -o $CH -c $CRS_CLUSTER_NAME -l "$CRS_LANGUAGE_ID" \
-q $CRS_VOTING_DISKS $CLSCFG_MISCNT

Eg.
./clscfg -install -nn node1,1,node2,2,node3,3 -pn node1-priv,1,node2-priv,2,node3-priv,3 -hn node1,1,node2,2,node3,3 -o /oracle/crs/ -c mycluster -l "'AMERICAN_AMERICA.WE8ISO8859P1'" -q /dev/rdsk/c4t600508B400105E660001000003960000d0s6 -force

After above operations, you can check your RAC health.

root@node1:/oracle/crs/bin# ./olsnodes
node1
node2
node3

root@node1:/oracle/crs/bin# ./crsctl check crs
CSS appears healthy
CRS appears healthy
EVM appears healthy

Juppie! ;)

The last step is to configure VIP interfaces:
$CRS_HOME/bin/vipca -silent -nodelist $CRS_NODELIST -nodevips $CRS_NODEVIPS

Brak komentarzy: