首页 > Linux操作系统 > Linux操作系统 > Oracle 10g RAC Setup in Linux AS5.3 Step By Step(二)

Oracle 10g RAC Setup in Linux AS5.3 Step By Step(二)

原创 Linux操作系统 作者:golden_zhou 时间:2011-08-30 14:39:56 0 删除 编辑

And then ‘Add’ node2 hostname information .
I am so unfortunate to encounter IP conflict (here is VIP) , Normally , you would not see this picture.
Ok, let’s overcome it .

Edit network interface , and notice public and private for network card .

We need to create crs directory on the shared disk for OCR and voting disk , because it’s shared disk ,
we only need to perform. this step on Node 1 Server .



Run ‘ ’ on node1 server .
Run ‘ ’ on node2 server .
Then run ‘ ’ on node1 server .

The following script. is the execution process ( # sh )on node1 server .
[root@mxb2bcoredb01 crs]# sh
WARNING: directory '/u01/product' is not owned by root
WARNING: directory '/u01' is not owned by root
Checking to see if Oracle CRS stack is already configured
/etc/oracle does not exist. Creating it now.
Setting the permissions on OCR backup directory
Setting up NS directories
Oracle Cluster Registry configuration upgraded successfully
WARNING: directory '/u01/product' is not owned by root
WARNING: directory '/u01' is not owned by root
Successfully accumulated necessary OCR keys.
Using ports: CSS=49895 CRS=49896 EVMC=49898 and EVMR=49897.
node :
node 1: mxb2bcoredb01 mxb2bpri01 mxb2bcoredb01
node 2: mxb2bcoredb02 mxb2bpri02 mxb2bcoredb02
Creating OCR keys for user 'root', privgrp 'root'..
Operation successful.
Now formatting voting device: /b2bdata/crs/votingdisk
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.

CSS is inactive on these nodes.
Local node checking complete.
Run on remaining nodes to start CRS daemons.
Then run ‘ ’ on node2 server .

Error message when run ‘ ’ :
Running vipca(silent) for configuring nodeapps
/u01/product/crs/jdk/jre//bin/java: error while loading shared libraries: cannot open
shared object file: No such file or directory
In order to fix this error during running ‘’ on node2 server , we need to modify vipca file on
both servers .
[root@mxb2bcoredb01 ~]# vi /u01/product/crs/bin/vipca
[root@mxb2bcoredb02 ~]# vi /u01/product/crs/bin/vipca
Find the below script. (bug 3937317) and add “ unset LD_ASSUME_KERNEL “ after ‘ fi ’ , save and
quit .
#Remove this workaround when the bug 3937317 is fixed
arch=`uname ‐m`
if [ "$arch" = "i686" ‐o "$arch" = "ia64" ‐o "$arch" = "x86_64" ]
#End workaround
Run ‘ /u01/product/crs/ ’ on node2 server again , and then run ‘ vipca ’ as root in the
another windows on the node2 server (Notes: X‐window) .

When we run ‘ vipca ’ on node2 server , mostly , we will encounter the below error message , and
we need to fix on the node2 server .
Then we run ‘ vipca ‘ again on the node2 server ( X‐window ).



If you encounter the below error message , maybe there are some problems in the ‘ /etc/hosts ’ , you
need to add ‘ localhost.localdomain localhost ’ , or firewall issue , or time rsync issue .
At last, we return to clusterware (CRS) installation window on the node1 server , and click ‘OK’ .


Oracle database software setup .
1, unzip Oracle database software .

Select ‘ Custom ’ option and



Because available swap is not enough for swap space required , the warning occurs , but we can
ignore it .



# sh /u01/product/oracle/ on the node1 server .

# sh /u01/product/oracle/ on the node2 server .
Click ‘ OK ’ to complete installation .

$ sqlplus “/as sysdba “ to check database installation status and oracle version (here is,
We need to upgrade clusterware and oracle software version to for system stability .

Clusterware and database software upgrade
1, On node1 server , unzip the file ‘ ’ in the directory
‘ /u01/packages ’ .
On node1 server , prepare to upgrade .

Maybe you will encounter the below error message (maybe you will not) . You must quit all
terminal window , and then login with user ‘ oracle ’ instead of ‘ root ’ , especially , you must login
VNC xwindow to upgrade software with user ‘ oracle ’ instead of switching from ‘ root ’ .
The error message is :
Starting Oracle Universal Installer...
Checking installer requirements...
Checking operating system version: must be redhat‐3, SuSE‐9, SuSE‐10, redhat‐4, redhat‐5, UnitedLinux‐
1.0, asianux‐1, asianux‐2 or asianux‐3
All installer requirements met.
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2010‐02‐25_01‐41‐45PM. Please
wait ...mxb2bcoredb01<*wmb2bprd1*/u01/packages/Disk1>$Oracle Universal Installer, Version Production

Copyright (C) 1999, 2008, Oracle. All rights reserved.
Can't connect to X11 window server using '' as the value of the DISPLAY variable.
OUI‐10025:Unable to start an interactive install session because of the following error:Can't connect to
X11 window server using '' as the value of the DISPLAY variable. The DISPLAY environment
variable should be set to :, where the is usually '0.0'.
OUI‐10026:Depending on the Unix Shell, you can use one of the following commands as examples to set
the DISPLAY environment variable:
‐ For csh: % setenv DISPLAY
‐ For sh, ksh and bash: $ DISPLAY=; export DISPLAY
Use the following command to see what shell is being used:
echo $SHELL
Use the following command to view the current DISPLAY environment variable setting:
‐ Make sure that client users are authorized to connect to the X Server.
OUI‐10027:To enable client users to access the X Server, open an xterm, dtterm or xconsole as the user
that started the session and type the following command:
% xhost +
To test that the DISPLAY environment variable is set correctly, run a X11 based program that comes with
the native operating system such as 'xclock':
If you are not able to run xclock successfully, please refer to your PC‐X Server or OS vendor for further
Typical path for 'xclock': '/usr/X11R6/bin/xclock'

Ok, we quit the terminal window , and login with user ‘ oracle ’ . then it run fine .
We must upgrade clusterware (CRS) at first before database software upgrade . please select
‘ OraCrs10g _home’ .

Check all of the status if they are ‘Succeeded’ .


To complete the installation of this patchset, you must perform. the following tasks on each node:
1. Log in as the root user.
2. As the root user, perform. the following tasks:
a. Shutdown the CRS daemons by issuing the following command:
/u01/product/crs/bin/crsctl stop crs
b. Run the shell script. located at:
This script. will automatically start the CRS daemons on the
patched node upon completion.
3. After completing this procedure, proceed to the next node and repeat.

Ok , let’s perform. the above steps one by one .

Ok , you can check the CRS software version on both servers . (

And you need to check the CRS status on node1 server or node2 server .
Then we start to upgrade oracle software on node1 server .

Please Notes: select ‘ OraDb10g_home1 ’ to upgrade database software .




Return to installation window , and click ‘OK’ to complete the installation .

You can check the oracle software version on the both servers .
Ok, the clusterware and oracle software upgrade successfully .

Create Database
1, Maybe we need to create some directory for our database (only perform. this step on node1
server ) . for example ,
mxb2bcoredb01<*wmb2bprd1*/>$cd /b2bdata
mxb2bcoredb01<*wmb2bprd1*/b2bdata>$mkdir ‐p oracle
mxb2bcoredb01<*wmb2bprd1*/b2bdata>$cd oracle/
mxb2bcoredb01<*wmb2bprd1*/b2bdata/oracle>$mkdir ‐p oradata
mxb2bcoredb01<*wmb2bprd1*/>$cd /b2bdata1
mxb2bcoredb01<*wmb2bprd1*/b2bdata1>$mkdir ‐p oracle
mxb2bcoredb01<*wmb2bprd1*/b2bdata1>$cd oracle/
mxb2bcoredb01<*wmb2bprd1*/b2bdata1/oracle>$mkdir ‐p oradata
mxb2bcoredb01<*wmb2bprd1*/>$cd /b2bdata2
mxb2bcoredb01<*wmb2bprd1*/b2bdata2>$mkdir ‐p oracle
mxb2bcoredb01<*wmb2bprd1*/b2bdata1>$cd oracle/
mxb2bcoredb01<*wmb2bprd1*/b2bdata1/oracle>$mkdir ‐p oradata arc
2, Maybe we need to crea





mxb2bcoredb01<*wmb2bprd1*/>$cd /b2bdata1/oracle
mxb2bcoredb01<*wmb2bprd1*/b2bdata1/oracle>$mkdir ‐p recovery



Notes: here physical memory = 64G .



Notes: You can configure the attribute of datafiles and redo logfile after completing database .


Click ‘Yes’ to create default listener .


Run ‘ crs_stat ‐t ’ to check the status of the crs service , database, instance , listener etc .
At last, we need to configure tnsnames.ora and spfile to prevent error ‘ORA‐12545’ (Bug) on the both
servers .


You can perform. the below step on node1 server .
‐‐‐‐‐‐ END ‐‐‐‐‐

来自 “ ITPUB博客 ” ,链接:,如需转载,请注明出处,否则将追究法律责任。

请登录后发表评论 登录


  • 博文量
  • 访问量