Monday, October 30, 2006

Oracle AS101202 Installation Step on RHEL4

Oracle AS 1012.02 installation step on RHEL4 is summarized from Reference: Oracle® Application Server Quick Installation Guide 10g Release 2 (10.1.2) for Linux x86

1) System hardware requirement.
Skip. No need to check, the runInstaller script will check for you.

2) Software dependency. Cut and paste the following command.
$ rpm -q glibc glibc-common binutils gcc gcc-c++ libstdc++ libstdc++-devel openmotif21 pdksh setarch make gnome-libs sysstat compat-db control-center xscreensaver
$ rpm -qa grep compat-libstdc++

3) Edit Kernel Parameters.

Execute $ ulimit -Hn
If the value is less than 65536, edit /etc/security/limits.conf
* soft nproc 2047
* hard nproc 16384
* soft nofile 2048
* hard nofile 65536

Edit /etc/sysctl.conf to include the following:
kernel.shmall = 2097152
kernel.shmmax = 2147483648
kernel.shmmni = 4096
# semaphores: semmsl, semmns, semopm, semmni
kernel.sem = 256 32000 100 142
fs.file-max = 131072
kernel.msgmni = 2878
kernel.msgmax = 8192
kernel.msgmnb = 65535

4) Edit /etc/hosts such that the machine has a proper domain name.
Eg. as1012

5) As root, add oracle user and oinstall group.
# /usr/sbin/groupadd oinstall
# /usr/sbin/useradd -g oinstall oracle

Set password for newly created user,
# passwd oracle

6) As root user, execute xhost + to enable any user to startup graphical interface.

7) As oracle user, execute /media/cdrom/disk1/runInstaller

Saturday, October 28, 2006

Oracle AS - Clustering and remove clustering for AS1013

Enable Clustering

In AS1013 we do not need to explicitly select multiple nodes via EM to join them into a cluster. However we configure a broadcasting address to opmn.xml of different nodes, different nodes will discover each other automatically and join as a cluster.

E.g. Running the following command for each node.
$ opmnctl config topology update discover "*"
$ opmnctl reload

The above command will update AS1013/opmn/conf/opmn.xml file with the following entry:

<discover list="*">

To see the cluster status in terminal,
$ opmnctl @cluster status -l

To see the individual application status,
$ opmnctl status -l -app

To see more usage of opmnctl command,
$ opmnctl usage config

When you login EM, at some point it will prompt you that only 1 EM should exist to rule the rest of AS instances.

Remove Clustering
To remove the instance from cluster, we'll execute the following command in that instance.
$ opmnctl config topology delete discover "*"
$ opmnctl reload
(Note: obtain the discover broadcasting value from AS1013/opmn/conf/opmn.xml)

Immediately it'll be out from the cluster.

As a stand-alone instance, it'll need to have EM running so that we can manage it easily. To explicitly startup EM, execute the following:
$ opmnctl startproc ias-component=OC4J application=ascontrol