Few Days back i have installed 10.2.0.2 on solaris and i will like to share with you all my experience of installing 10.2.0.2 solaris 10
It is always advisable to run preinstall script provided by metalink.So I downloaded the preinstall script for 10gr2 installation on solaris SPARC 64 bit from metalink(ref mtalink ID 334567.1)
the script was in tar format so it is necessary to untar it as shown
tar xvf 10gR2_rdbms_solaris_hcve_091705.tar
the output will be a *.txt and validate.pl
Execute validate filename.txt from the command line, as in the following examples:
# validate 10gR2_rdbms_solaris_hcve_091705.txt
OR
# perl validate.pl 10gR2_rdbms_solaris_hcve_091705.txt
To verify whether perl is present in your system use the folllowing command
perl -v
Manual pre-Installation checks
1. As Root User
i. Check for the display.
# xhost +
# xclock
ii. Create the oracle inventory group (oinstall) and OSDBA (dba).
# /usr/sbin/groupadd oinstall
# /usr/sbin/groupadd dba
iii. Create the users oracle and nobody.
# /usr/sbin/useradd -u 202 -g oinstall -G dba oracle
# passwd oracle
# /usr/sbin/useradd nobody
iv. Get the ids of oinstall and dba groups from the node 1 and create the groups with same id on the node 2. Similarly, for the oracle user find the id from node 1 and create the user on the node 2 with the same password as of node 1. Create also the user nobody without fail.
On Node 1:
# id oracle
uid=202(oracle) gid=200(oinstall) groups=201(dba)
On Node 2:
# /usr/sbin/groupadd -g 200 oinstall
# /usr/sbin/groupadd -g 201 dba
# /usr/sbin/useradd -u 202 -g oinstall -G dba oracle
# passwd oracle Give the same password as of Node 1
# /usr/sbin/useradd nobody
Important: Ensure to add dba group as the secondary group for oracle user.
i. Add an entry for node 1 and node 2 in the
Node 1
/oracle/home
Vi .rhosts
$ +
$ sharedb2 oracle
$ sharedb2 root
$ :wq!
Node 2
$ +
$ sharedb1 oracle
$ sharedb1 root
$:wq!
The ‘+’ sign is used to give Adminstrative priviledges to oracle user so that it can it can remotely login into other nodes and perform the installation on other nodes as well
ii. Check for the rsh configuration. Ex. Node 1 #> rsh node2 date
3. As Oracle User
Use the following command to determine path of make,ld,nm,ar binaries
$ which make
$ which ld
$ which ar
$which nm
All the above must be included in PATH environment variable of .profile
i. Configure the .profile file.
umask 022
export ORACLE_BASE= /oracle/app/oracle
export ORACLE_HOME=/clusterware/crs/oracle/product/10.2.0
PATH=$PATH:$ORACLE_HOME/bin:/usr/local/bin:/usr/bin:/usr/ccs/bin:(PATH of make,ld,nm,ar)
Unset LD_LIBRARY_PATH
If the /tmp directory has less than 400 MB of free disk space, then identify a file system with at least 400 MB of free space and set the TEMP and TMPDIR environment variables to specify a temporary directory on this file system.
As root,
# mkdir /mount_point/tmp
# chmod 775 /mount_point/tmp
As oracle,
$ export TEMP=/mount_point/tmp
$ export TMPDIR=/mount_point/tmp
ii. Enter the following command to ensure that X Window applications can display on this system:
$ xhost + hostname
The hostname is the name of the local host.
4. Checking the Hardware Requirements
Each node must meet the following minimum hardware requirements:
i. At least 1 GB of physical RAM
# /usr/sbin/prtconf | grep “Memory size”
ii. Swap space equivalent to the multiple of the available RAM, as indicated in the following table:
Available RAM Swap Space Required
Between 1 GB and 2 GB 1.5 times the size of RAM
1.5 times the size of RAM Equal to the size of RAM
# /usr/sbin/swap -s
iii. 400 MB of disk space in the /tmp directory
# df -k /tmp
iv. 4 GB of disk space for the Oracle software, depending on the installation type and platform
# df -k
v. To determine whether the system architecture can run the software, enter the following command:
# /bin/isainfo –kv
9. Checking the Software Requirements
Item Requirement
Packages SUNWarc
SUNWbtool
SUNWhea
SUNWlibC
SUNWlibm
SUNWlibms
SUNWsprot
SUNWtoo
SUNWi1of
SUNWi1cs
SUNWi15cs
SUNWxwfnt
SUNWsprox
# pkginfo -i SUNWarc SUNWbtool …
Patches 118345-03
119961-01
# /bin/showrev -p
Kernel Parameters
project.max-sem-ids
process.max-sem-nsems
project.max-shm-memory
project.max-shm-ids
100
256
4294967295
100
On Solaris 10, use the following procedure to view the current value specified for resource controls, and to change them without system reboot, if necessary:
i. To view the current values of the resource control, enter the following commands:
# id -p // to verify the project id
uid=0(root) gid=0(root) projid=1 (user.root)
# prctl -n project.max-shm-memory -i project user.root
# prctl -n project.max-sem-ids -i project user.root
ii. To modify the value of max-shm-memory to 6 GB:
# prctl -n project.max-shm-memory -v 6gb -r -i project user.root
To modify the value of max-sem-ids to 128:
# prctl -n project.max-sem-ids -v 128 -r -i project user.root
To modify the value of max-sem-nsems to 256:
# prctl -n process.max-sem-ids -v 256 -r -i process $$
Note: If you are modifying any kernel parameters using process control make sure to change the values in the /etc/system also. Since the modification of kernel parameter using process control is not persistent across the reboot.
There are few other pre-installation tasks which i will write in my next posts
