Oracle Database Administration

Oracle Database 11g R2 Silent Installation (OUI)::

In this article we will learn Oracle Database 11g R2 Silent Installation (OUI) on Oracle Enterprise Linux (OEL5).

Overview:

This article is a comprehensive guide for Silent OUI installation of Oracle Database 11g Release 2 (11.2.0.3.0) x64 on the Oracle Enterprise Linux 5 (OEL5) x64 Operating System Environment.

Please do keep in mind that this article should not be considered a substitution of the official installation guide and release note from Oracle (http://www.oracle.com). The below mentioned link can be used to download the official installation guide for Oracle Database 11g Release 2 (11.2.0.3.0) x64 on Linux x64 Operating Environment.

http://docs.oracle.com/cd/E11882_01/install.112/e24321/app_nonint.htm#BABFEECI

http://download.oracle.com/docs/cd/E11882_01/install.112/e24321/toc.htm

Hardware Requirements Check:

Note:Login to the system as a root user for performing the below activities.

Memory Requirements:

Minimum:1 GB of RAM

Recommended:2 GB of RAM

To determine the RAM size, enter the following command:

[root@oelinux ~]# grep MemTotal /proc/meminfo

Note:If the size of the RAM is less than the required size, then you must install more memory before continuing.

Available RAM	SWAP Space Requirement
Between 1 GB and 2 GB	1.5 times the size of the RAM
Between 2 GB and 16 GB	Equal to the size of the RAM
More than 16 GB	16 GB

To determine the size of the configured swap space, enter the following command:

[root@oelinux ~]# grep SwapTotal /proc/meminfo

Note:If there is a need of increasing swap space, see O/S documentation for increasing the swap space.

Disk Space Requirements:

At least 1 GB of free disk space should be available in the /tmp directory.

To determine the amount of disk space available in the /tmp directory, enter the following command:

[root@oelinux ~]# df -kh /tmp

If there is less than 1 GB of free disk space available in the /tmp directory, then do one of the below mentioned steps:

Ξ Delete unnecessary files from the tmp directory.

Ξ Increase the size of tmp directory as follows (Extend the file system that contains the /tmp directory):

Disk space requirements for software files, and data files for each installation type on Linux x86-64:

Installation Type	Minimum Requirement for Software Files (GB)
Enterprise Edition	4.35
Standard Edition	4.22
Installation Type	Minimum Requirement for Data Files (GB)
Enterprise Edition	1.7
Standard Edition	1.5

To determine the amount of free disk space on the system, enter the following command:

[root@oelinux ~]# df -kh

If your diskspace is not enough, please contact administrator for increasing the disk space.

Package Requirements Check:

After the installation of OEL5_x64, the next task is to install all packages required by Oracle Database 11g R2 x64. During the installation process the Oracle Universal Installer performs prerequisites checks before the actual installation of database. For ensuring that these prerequisite checks complete successfully, ensure that all the packages listed below are installed properly.The following are the list of packages required for Oracle Database 11g Release 2 (11.2) x64 on OEL5 x64:

binutils-2.17.50.0.6
compat-libstdc++-33-3.2.3
compat-libstdc++-33-3.2.3 (32 bit)
elfutils-libelf-0.125
elfutils-libelf-devel-0.125
gcc-4.1.2
gcc-c++-4.1.2
glibc-2.5-24
glibc-2.5-24 (32 bit)
glibc-common-2.5
glibc-devel-2.5
glibc-devel-2.5 (32 bit)
glibc-headers-2.5
ksh-20060214
libaio-0.3.106
libaio-0.3.106 (32 bit)
libaio-devel-0.3.106
libaio-devel-0.3.106 (32 bit)
libgcc-4.1.2
libgcc-4.1.2 (32 bit)
libstdc++-4.1.2
libstdc++-4.1.2 (32 bit)
libstdc++-devel 4.1.2
make-3.81
sysstat-7.0.2

The packages listed above can be found on the installer disc/image of Oracle Enterprise Linux 5 x64 or can be downloaded from the vendor's website.

To determine whether the required packages are installed, enter commands similar to the following:

[root@oelinux ~]# rpm -q package_name

e.g: [root@oelinux ~]# rpm –q binutils-2.17.50.0.6

if the package is not installed then install the package as mentioned below:

[root@oelinux ~]# rpm -ivh package_name

N.B: To use ODBC, you must also install the following additional ODBC RPMs which are listed below:

unixODBC-2.2.11 (32-bit)
unixODBC-devel-2.2.11 (64-bit)
unixODBC-2.2.11 (64-bit)

The odbc packages can be downloaded from http://www.unixodbc.org and can be installed.

For the screenshots of the activities please visit the mentioned link::: http://www.sensehaze.com/mydata/resources_section/installation/11g_oel_sil/index.php

Network Configuration:

Edit /etc/hosts file:

Ensure that the hostname(oelinux) is not mentioned in the loopback address information in the /etc/hosts file.

Disable SELinux and Firewall:

[root@oelinux ~]# system-config-selinux
[root@oelinux ~]# service iptables stop

Creation of Required O/S Users and Groups:

The following local operating system user and groups are required for oracle database installation:

Oracle Inventory Group -- oinstall
OSBDA Group -- dba
OSOPER Group -- oper
Oracle Software Owner User -- Oracle

Check whether the groups/user exists , if doesn't exist please create them.
Follow the below mentioned steps...

To determine whether "oinstall" group exists, type the following command:
[root@oelinux ~]# more /etc/oraInst.loc
If the output shows oinstall group then the group exists and need not to be created.
.
To determine whether "dba" group exists, type the following command:
[root@oelinux ~]# grep dba /etc/group
If the output shows dba group then the group exists and need not to be created.
.
To determine whether "oracle" user exists, type the following command:
[root@oelinux ~]# id oracle
If the output shows oracle user then the user exists and need not to be created.
The output should be similar to following, indicating "oinstall" as primary and "dba" as secondary group.
uid=1001(oracle) gid=1001(oinstall) groups=1002(dba),1003(oper).
If the primary group is not "oinstall" and the user "oracle" is not the member of "dba" group then we have to modify the user "oracle" as mentioned below::
[root@oelinux ~]#usermod -g oinstall -G dba oracle
If the user or the required groups doesn't exist then create them as mentioned below:
[root@oelinux ~]# groupadd -g 1001 oinstall
[root@oelinux ~]# groupadd -g 1002 dba
[root@oelinux ~]# groupadd -g 1003 oper
[root@oelinux ~]# useradd -m -u 1001 -g oinstall -G dba,oper oracle
Now check the status of "oracle" user.
[root@oelinux ~]# id oracle
The output should be similar to following, indicating "oinstall" as primary and "dba" as secondary group.
uid=1001(oracle) gid=1001(oinstall) groups=1002(dba),1003(oper).
Now set the password of "oracle" user.
[root@oelinux ~]# passwd oracle
and input a password for "oracle" user.
Verify That the User nobody Exists:
Before installation of oracle software, complete the following steps to verify that the user "nobody" exists on the system:
To determine if the user exists, enter the following command:
[root@oelinux ~]# id nobody
If this command displays information about the "nobody" user, then you do not have to create that user.
If the user "nobody" does not exist, then enter the following command to create it:
[root@oelinux ~]# useradd nobody

Configuration of Kernel Parameters:

Verify that the kernel parameters shown in the following table are set to values greater than or equal to the minimum value shown.

Using any text editor, edit the /etc/sysctl.conf file, and add or edit lines similar to the following:

fs.aio-max-nr	1048576
fs.file-max	6815744
kernel.shmall	2097152
kernel.shmmax	536870912
kernel.shmmni	4096
kernel.sem	250 32000 100 128
net.ipv4.ip_local_port_range	9000 65500
net.core.rmem_default	262144
net.core.rmem_max	4194304
net.core.wmem_default	262144
net.core.wmem_max	1048586

[root@oelinux ~]# vim /etc/sysctl.conf

After adding the above lines to the /etc/sysctl.conf file, they persist each time the system reboots. If you would like to make these kernel parameter value changes to the current system without having to reboot, enter the following command:

[root@oelinux ~]# sysctl -p

If the output of the above command shows any error, please rectify the error before proceeding to next step.

To improve the performance on Linux systems, Oracle recommends us to increase the shell limits for the oracle software owner user "oracle".

Update the resource limits in the /etc/security/limits.conf configuration file for the installation owner (Here "oracle" user is the owner).

----------------------------

oracle soft nproc 2047

oracle hard nproc 16384

oracle soft nofile 1024

oracle hard nofile 65536

oracle soft stack 10240

----------------------------

[root@oelinux ~]# vim /etc/security/limits.conf

Creation of Required Directories:

The next step is to create a directory that will be used to store the "Oracle Database software", "Oracle Database Datafiles" and "Flash Recovery Data".

After the directory is created, we must then specify the correct owner, group, and permissions for it.

[root@oelinux ~]# mkdir -p /u01/app/
[root@oelinux ~]# chown -R oracle:oinstall /u01/app/
[root@oelinux ~]# chmod -R 775 /u01/app/

Configuring the oracle User’s Environment:

Set the default file mode creation mask (umask) to 022 for "oracle" user. For setting so, do the following:

[root@oelinux ~]# su - oracle
[oracle@oelinux ~]$ vim ~/.bash_profile

Add a line as written below and save the file.

umask 022

N.B:You do not have to set the DISPLAY environment variable if you are completing a silent mode installation.

For the screenshots of the activities please visit the mentioned link::: http://www.sensehaze.com/mydata/resources_section/installation/11g_oel_sil/index.php

Installation of Oracle Database:

After configuring the oracle user’s environment, create a response file for silent installation and configuration of the database.
A response file is available in the response directory of the installation disc.
I will copy and edit the response file for our purpose.

I will install and configure database through the response file.

Specify the Installation Option in the response file:

Parameter	Response
oracle.install.option	INSTALL_DB_AND_CONFIG
ORACLE_HOSTNAME	oelinux
UNIX_GROUP_NAME	oinstall
INVENTORY_LOCATION	/u01/app/oraInventory
SELECTED_LANGUAGES	en
ORACLE_HOME	/u01/app/oracle/product/11.2.0/dbhome_1
ORACLE_BASE	/u01/app/oracle
oracle.install.db.InstallEdition	EE
oracle.install.db.EEOptionsSelection	false
oracle.install.db.DBA_GROUP	dba
oracle.install.db.OPER_GROUP	oper
oracle.install.db.config.starterdb.type	GENERAL_PURPOSE
oracle.install.db.config.starterdb.globalDBName	mydb
oracle.install.db.config.starterdb.SID	mydb
oracle.install.db.config.starterdb.characterSet	AL32UTF8
oracle.install.db.config.starterdb.memoryOption	true
oracle.install.db.config.starterdb.memoryLimit	700
oracle.install.db.config.starterdb.installExampleSchemas	false
oracle.install.db.config.starterdb.enableSecuritySettings	true
oracle.install.db.config.starterdb.password.ALL	Sensehaze123
oracle.install.db.config.starterdb.control	DB_CONTROL
oracle.install.db.config.starterdb.automatedBackup.enable	false
oracle.install.db.config.starterdb.storageType	FILE_SYSTEM_STORAGE
oracle.install.db.config.starterdb.fileSystemStorage.dataLocation	/u01/app/oracle/oradata
oracle.install.db.config.starterdb.fileSystemStorage.recoveryLocation	/u01/app/oracle/flash_recovery_area
SECURITY_UPDATES_VIA_MYORACLESUPPORT	false
DECLINE_SECURITY_UPDATES	true
oracle.installer.autoupdates.option	SKIP_UPDATES

Open terminal and run installer with the response file option as "oracle" user.

[oracle@oelinux ~]$ ./runInstaller -silent -responsefile /oracle_soft/db_install.rsp

Wait for the installation step to prompt for executing the scripts.

Open terminal and execute the scripts mentioned in the above screenshot as "root" user.

[root@oelinux ~]# /u01/app/oraInventory/orainstRoot.sh

After this run the second script, also as a "root" user .

[root@oelinux ~]# /u01/app/oracle/product/11.2.0/dbhome_1/root.sh

This finishes the Oracle database installation and configuration.

View the setup logfiles :

[root@oelinux ~]# cat /u01/app/oraInventory/logs/silentinstallxxxxx.log

[root@oelinux ~]# cat /u01/app/oraInventory/logs/installactionsxxxxx.log

Set Oracle User Profile :
Open the profile file and add the below mentioned lines:

export ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1
export ORACLE_SID=mydb
export LD_LIBRARY_PATH=$ORACLE_HOME/lib
export PATH=$PATH:$HOME/bin:$ORACLE_HOME/bin

[oracle@oelinux ~]$ vim ~/.bash_profile
Or use any editor of your choice, to edit the profile of "Oracle" user.

After editing the profile run it for checking errors and loading.

[oracle@oelinux ~]$ . ~/.bash_profile
If there is any syntax error in the profile it will be reported.If there is no error then we will get the prompt silently.

Connect to the Database:

[oracle@oelinux ~]$ ps -eaf | grep pmon

[oracle@oelinux ~]$ export ORACLE_SID=mydb

[oracle@oelinux ~]$ sqlplus sys@mydb as sysdba

And you will be connected to the database.

For the screenshots of the activities please visit the mentioned link::: http://www.sensehaze.com/mydata/resources_section/installation/11g_oel_sil/index.php

SenseHaze.com: addnode utility-Extend Oracle Clusterware to new node

2012-03-03T07:40:00.001-08:00

SenseHaze.com: addnode utility-Extend Oracle Clusterware to new node

Oracle Database 11g R2 installation on Redhat Enterprise Linux 6

2012-03-03T07:40:00.000-08:00

Oracle Database 11g R2 installation on Redhat Enterprise Linux 6 (64-bit)::

In this article we will learn how to install oracle database 11g Release 2 on Redhat Enterprise Linux 6 (64-bit).

Overview:

This article is a comprehensive guide for the installation of Oracle Database 11g Release 2 (11.2.0.3.0) on Redhat Enterprise Linux 6 (RHEL-6) 64-bit Operating System Environment.

http://docs.oracle.com/cd/E11882_01/install.112/e24326/toc.htm

Objective of the Article:

By the time we finish this article, we should be able to understand the following:

(1)Installation of oracle database (11.2.0.3.0) x64 on Redhat Enterprise Linux 6 (RHEL6) x64.

(2)Configuration of Oracle Net listener(http://download.oracle.com/docs/cd/E11882_01/network.112/e10836/listenercfg.htm

(3)Creation & configuration of general-purpose Oracle 11g (11.2.0.3.0) database that makes use of the local file system for physical database file storage (control files, data files, flash recovery area, online redo log files).

Installation of RHEL6 x64:

Install Redhat Enterprise Linux 6 (RHEL6) x64 on your machine.

For More information about RHEL6 installation, visit the below site::

http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/index.html

Network Configuration:

Edit /etc/hosts File :

Ensure that the hostname (redhat6) is not in the loopback address in the /etc/hosts file. If it is mentioned then remove the entry.

Disable Firewall :

[root@redhat6 ~]# system-config-firewall

Disable SeLinux :

[root@redhat6 ~]# system-config-selinux

Note : Reboot the node for reflecting the changes.

Download Oracle Database Software:

First we have to download the required Oracle Database software packages from the Oracle Technology Network (OTN) or Oracle Edelivery Site and then extract the Oracle Database Software packages.

Download the Oracle Database 11g Release 2 (11.2.0.3.0) Software for Linux x64 Operating System Environment.

Link for downloading oracle Database Software Package:: http://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html

Hardware Requirements Check:

Note:Login to the system as a root user for performing the below activities.

Memory Requirements:

Minimum:1 GB of RAM

Recommended:2 GB of RAM

To determine the RAM size, enter the following command:

[root@redhat6 ~]# cat /proc/meminfo | grep MemTotal

Note:If the size of the RAM is less than the required size, then you must install more memory before continuing.

Available RAM	SWAP Space Requirement
Between 1 GB and 2 GB	1.5 times the size of the RAM
Between 2 GB and 16 GB	Equal to the size of the RAM
More than 16 GB	16 GB

To determine the size of the configured swap space, enter the following command:

[root@redhat6 ~]# cat /proc/meminfo | grep SwapTotal

Note:If there is a need of increasing swap space, see O/S documentation for increasing the swap space.

Disk Space Requirements:

At least 1 GB of free disk space should be available in the /tmp directory.

To determine the amount of disk space available in the /tmp directory, enter the following command:

[root@redhat6 ~]# df -h /tmp

If there is less than 1 GB of free disk space available in the /tmp directory, then do one of the below mentioned steps:

Ξ Delete unnecessary files from the tmp directory.

Ξ Extend the file system that contains the /tmp directory. If necessary, contact the system administrator for information about extending file systems.

Disk space requirements for software files, and data files for each installation type on Linux x86-64:

Installation Type	Minimum Requirement for Software Files (GB)
Enterprise Edition	4.35
Standard Edition	4.22
Installation Type	Minimum Requirement for Data Files (GB)
Enterprise Edition	1.7
Standard Edition	1.5

To determine the amount of free disk space on the system, enter the following command:

[root@redhat6 ~]# df -kh

If your diskspace is not enough, please contact administrator for increasing the disk space.

Automatic Memory Management:

Starting with Oracle Database 11g, the Automatic Memory Management feature requires more shared memory (/dev/shm)and file descriptors. The shared memory should be sized to be at least the greater of MEMORY_MAX_TARGET and MEMORY_TARGET for each Oracle instance on that computer.To determine the amount of shared memory available, enter the following command:

[root@redhat6 ~]# df -h /dev/shm

System Architecture:

This command displays the processor type. Verify that the processor architecture matches the Oracle software release to install. If you do not see the expected output, then you cannot install the software on this system. To determine whether the system architecture can run the software, enter the following command:

[root@redhat6 ~]# uname -a

For all the screenshots, please visit the link::: LINK FOR STEPS-SCREENSHOT

Package Requirements Check:

After the installation of RHEL6_x64, the next task is to install all packages required by Oracle Database 11g R2 x64. During the installation process the Oracle Universal Installer (OUI) performs prerequisites checks before the actual installation of database. For ensuring that these prerequisite checks complete successfully, ensure that all the packages listed below are installed properly.The following are the list of packages required for Oracle Database 11g Release 2 (11.2) x64 on RHEL6 x64:

binutils-2.20.51.0.2
compat-libstdc++-33-3.2.3
compat-libstdc++-33-3.2.3 (32 bit)
elfutils-libelf-0.148
elfutils-libelf-devel-0.148
gcc-4.4.4
gcc-c++-4.4.4
glibc-2.12-1
glibc-2.12-1 (32 bit)
glibc-common-2.12
glibc-devel-2.12
glibc-devel-2.12 (32 bit)
glibc-headers-2.12
ksh-20100621
libaio-0.3.107
libaio-0.3.107 (32 bit)
libaio-devel-0.3.107
libaio-devel-0.3.107 (32 bit)
libgcc-4.4.4
libgcc-4.4.4 (32 bit)
libstdc++-4.4.4
libstdc++-4.4.4 (32 bit)
libstdc++-devel-4.4.4
libstdc++-devel-4.4.4 (32 bit)
make-3.81
sysstat-9.0.4

The package(s) listed above can be found on the installer disc/image of Redhat Enterprise Linux 6 x64 or can be downloaded from the vendor's website.

To determine whether the required packages are installed, enter commands similar to the following:

[root@redhat6 ~]# rpm -q package_name

if the package is not installed then install the package as mentioned below:

[root@redhat6 ~]# rpm -ivh package_name

N.B: To use ODBC, you must also install the following additional ODBC RPMs which are listed below:

unixODBC-2.2.14 (32-bit)
unixODBC-devel-2.2.14
unixODBC-2.2.14

The odbc packages can be downloaded from http://www.unixodbc.org and can be installed as mentioned above.

Creation of Required O/S Users and Groups:

The following local operating system user and groups are required for oracle database installation:

Oracle Inventory Group -- oinstall
OSBDA Group -- dba
Oracle Software Owner User -- Oracle

Check whether the groups/user exists , if doesn't exist please create them. Follow the below mentioned steps...

To determine whether "oinstall" group exists, type the following command:
[root@redhat6 ~]# more /etc/oraInst.loc
If the output shows oinstall group then the group exists and need not to be created.
.
To determine whether "dba" group exists, type the following command:
[root@redhat6 ~]#grep dba /etc/group
If the output shows dba group then the group exists and need not to be created.
.
To determine whether "oracle" user exists, type the following command:
[root@redhat6 ~]#id oracle
If the output shows oracle user then the user exists and need not to be created.
The output should be similar to following, indicating "oinstall" as primary and "dba" as secondary group.
uid=1001(oracle) gid=1001(oinstall) groups=1002(dba).
If the primary group is not "oinstall" and the user "oracle" is not the member of "dba" group then we have to modify the user "oracle" as mentioned below::
[root@redhat6 ~]#usermod -g oinstall -G dba oracle
.
If the user or the required groups doesn't exist then create them as mentioned below:
[root@redhat6 ~]# groupadd -g 1001 oinstall
[root@redhat6 ~]# groupadd -g 1002 dba
[root@redhat6 ~]# useradd -m -u 1001 -g oinstall -G dba oracle

Now check the status of "oracle" user.
[root@redhat6 ~]# id oracle
The output should be similar to following, indicating "oinstall" as primary and "dba" as secondary group.
uid=1001(oracle) gid=1001(oinstall) groups=1002(dba).

Now set the password of "oracle" user.
[root@redhat6 ~]# passwd oracle
and input a password for "oracle" user.
Verify that the user "nobody" Exists:
Before installtion of oracle software, complete the following steps to verify that the user "nobody" exists on the system:
To determine if the user exists, enter the following command:
[root@redhat6 ~]# id nobody
If this command displays information about the "nobody" user, then you do not have to create that user.
If the user "nobody" does not exist, then enter the following command to create it:
[root@redhat6 ~]# useradd nobody

For all the screenshots, please visit the link::: LINK FOR STEPS-SCREENSHOT

Configuration of Kernel Parameters:

Verify that the kernel parameters shown in the following table are set to values greater than or equal to the minimum value shown.

Using any text editor, edit the /etc/sysctl.conf file, and add or edit lines similar to the following:

fs.aio-max-nr	1048576
fs.file-max	6815744
kernel.shmall	2097152
kernel.shmmax	4294967295
kernel.shmmni	4096
kernel.sem	250 32000 100 128
net.ipv4.ip_local_port_range	9000 65500
net.core.rmem_default	262144
net.core.rmem_max	4194304
net.core.wmem_default	262144
net.core.wmem_max	1048586

[root@redhat6 ~]# vim /etc/sysctl.conf

[root@redhat6 ~]# sysctl -p

If the output of the above command shows any error, please rectify the error before proceeding to next step.

To improve the performance on Linux systems, Oracle recommends us to increase the shell limits for the oracle software owner user "oracle".

Update the resource limits in the /etc/security/limits.conf configuration file for the installation owner (Here "oracle" user is the owner).

----------------------------

oracle soft nproc 2047
oracle hard nproc 16384
oracle soft nofile 1024
oracle hard nofile 65536
oracle soft stack 10240

----------------------------

[root@redhat6 ~]# vim /etc/security/limits.conf\

Creation of Required Directories:

The next step is to create a directory that will be used to store the "Oracle Database software", "Oracle Database Datafiles" and "Flash Recovery Data".

After the directory is created, we must then specify the correct owner, group, and permissions for it.

For example:

[root@redhat6 ~]# mkdir -p /u01/app/
[root@redhat6 ~]# chown -R oracle:oinstall /u01/app/
[root@redhat6 ~]# chmod -R 775 /u01/app/

Mount Oracle Database Disc:

If the installer is in zip format then unzip it .If it is on a disc then mount the disc and copy the contents as follows:

N.B: I have created "oracle_soft" named directory for storing "oracle database installation files".

[root@redhat6 ~]# mkdir -p /oracle_soft
[root@redhat6 ~]# chown -R oracle:oinstall /oracle_soft/
[root@redhat6 ~]# chmod -R 775 /oracle_soft/

Configuring the oracle User’s Environment:

Set the default file mode creation mask (umask) to 022 for "oracle" user. For setting so, do the following:

[root@redhat6 ~]# su - oracle
[oracle@redhat6 ~]$ vim ~/.bash_profile

Add a line as written below and save the file.

umask 022

N.B:Before starting the Oracle Universal Installer, we should first verify that the server from where we are doing the installation, have X server installed on it. For verification we can type "xclock" in the terminal, it will show a clock if X server is available.

Before starting the installation we have to run the xhost + command as root from the console to allow X Server connections.

[root@redhat6 ~]# xhost +

If we are performing installation from a remote machine then we have to give complete IP address of the remote machine, as shown below:

[oracle@redhat6 ~]$ export DISPLAY=IP_REMOTE_MACHINE:0

Installation of Oracle Database:

After configuring the oracle user’s environment, start Oracle Universal Installer (OUI) and install Oracle Database as follows:

[root@redhat6 ~]# su - oracle

Go to the directory where our installation software is copied and type "./runInstaller" , then our installation will begin:

[oracle@redhat6 ~]$cd /oracle_soft/dbsoft/database
[oracle@redhat6 ~]$ ./runInstaller

Link for Installation of Oracle Database

Set Oracle User Profile:
Open the profile file and add the below mentioned lines:

export ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1
export ORACLE_SID=mydb
export LD_LIBRARY_PATH=$ORACLE_HOME/lib
export PATH=$PATH:$HOME/bin:$ORACLE_HOME/bin
umask 022

[oracle@redhat6 ~]$ vim ~/.bash_profile
Or use any editor of your choice, to edit the profile of "Oracle" user.

After editing the profile run it for checking errors and loading.

[oracle@redhat6 ~]$ . ~/.bash_profile
If there is any syntax error in the profile it will be reported.If there is no error then we will get the prompt silently.

Listener Creation:

[root@redhat6 ~]# xhost +

Open command prompt(terminal) & type “netca” as shown in the below screen:

[oracle@redhat6 ~]$ netca

Link for Listener Creation

Database Creation:

[root@redhat6 ~]# xhost +

Open command prompt and type "dbca", as shown in the below screenshot:

[oracle@redhat6 ~]$ dbca

Link for Database Creation

Connect to the Database:

Open command prompt(terminal).

[oracle@redhat6 ~]$ export ORACLE_SID=mydb

[oracle@redhat6 ~]$ sqlplus sys@mydb as sysdba

And you will be connected to the database.

For all the screenshots, please visit the link::: LINK FOR STEPS-SCREENSHOT

Add a New Node to an Existing Oracle RAC 10g Cluster on Linux

2012-02-20T07:33:00.000-08:00

Add a New Node to an Existing Oracle RAC 10g Cluster on Linux::

Overview:

This article is a comprehensive guide to adding a new node to an existing Oracle RAC 10g Release 2 cluster .
In most businesses, a primary business requirement for an Oracle Real Application Clusters (RAC) configuration is scalability of the database tier across the entire system—so that when the number of users increases, additional instances can be added to the cluster to distribute the load.

Please do keep in mind that this article should not be considered a substitution of the guide from Oracle (http://www.oracle.com). The below mentioned link can be used to acceess the Guide:

http://www.oracle.com/technetwork/articles/vallath-nodes-095339.html

Existing Environment:

Softwares used:

Operating System	RHEL 5 - 32bit (All the nodes).
Shared Storage	Openfiler
Oracle Database	10.2.0.1.0
Cluster Manager	Oracle Clusterware 11.1.0.6.0
File System	OCFS and ASM

Names and Values used:

Database Name	RACDB
Database Service Name	RACDB_SRVC
Number of Nodes	Two Nodes - RAC1,RAC2
Number of Instances	Two Instances - RACDB1,RACDB2

Note: In this article the new Node to be added is named "RAC3" and the new Instance to be added is named "RACDB3".
So after addition of the new node, the details will be as follows:

Database Name	RACDB
Database Service Name	RACDB_SRVC
Number of Nodes	Three Nodes - RAC1,RAC2,RAC3
Number of Instances	Three Instances - RACDB1,RACDB2,RACDB3

Dependencies and Prerequisites for Node Addition in the Cluster:

→ Install the Linux Operating System - The new node (RAC3) should have the same version of the operating system as the existing nodes, including all patches required for Oracle.

→ Install Required Linux Packages for Oracle RAC Database - After installing Linux on RAC3, verify and install all packages required by Oracle RAC Database.

→ Configure Public and Private Network - We need to configure the network (RAC3) for access to the public network as well as the private interconnect.
We need to configure the /etc/hosts file on all nodes in the RAC cluster. Notice that the /etc/hosts settings should the same for all nodes. So we will add the "Public IP", "Private IP", and "Virtual IP" of the new node (RAC3) in the /etc/hosts file of the other nodes (RAC1,RAC2) and similarly the network info of the other nodes should be mentioned in the /etc/hosts file of RAC3.
Verify that the new node (RAC3) has access to the public and private network of all current nodes (using the ping utility).

→ Turnoff Firewall - Turnoff firewall of the new node (RAC3). Similary disable SELinux also.

→ Update the kernel parameters and Shell Limits - As per the recomendation from Oracle, please update the kernel parameters and shell limits.

→ Create the Administrative User - In all existing nodes the administrative owner is "oracle", so the next step is to create an administrative user account on node RAC3. While creating this user account, it is important that the UID and the GID of user oracle are identical to that of the other RAC nodes.

→ Create the Oracle Binaries Directory - Create oracle binaries directory structure similar to the other nodes, that will be used to store the Oracle Database software and give the ownership of the directory to "oracle" user.

→ Synchronize Time on the new node (RAC3) - Synchronize Time on the new node (RAC3) to keep it in sync with the other nodes.

→ Configure Shared-Storage on RAC3 -
Configure the iSCSI Initiator.
Install and Configure Oracle Cluster File System (OCFS).
Install and Configure Automatic Storage Management (ASMLib).

→ Establish User Equivalence with SSH - When adding nodes to the cluster, Oracle copies files from the node where the installation was originally performed to the new node (RAC3) in the cluster. Such a copy process is performed either by using ssh protocol where available or by using the remote copy (rcp). In order for the copy operation to be successful, the "oracle" user on the RAC node must be able to login to the new RAC node without having to provide a password or passphrase.
Note :We will do the node addition activity from this session(RAC1 Node).

Install cvuqdisk RPM Package:

RAC3 (as root user):

[root@rac3 ]# CVUQDISK_GRP=oinstall; export CVUQDISK_GRP
[root@rac3 ]# rpm -ivh cvuqdisk-1.0.1-1.rpm

Cluster Verification: In Oracle Database 10g R2, Oracle introduced a new utility called Cluster Verification Utility (CVU) as part of the clusterware software. Executing the utility using the appropriate parameters determines the status of the cluster. At this stage, before beginning installation of the Oracle Clusterware, we should perform two verifications:
(1) If the hardware and operating system configuration is complete:

cluvfy stage -post hwos -n rac1,rac3

(2) Perform appropriate checks on all nodes in the node list before setting up Oracle Clusterware.

cluvfy stage -pre crsinst -n rac1,rac3

Extend Oracle Clusterware to new node(RAC3):

Oracle Clusterware is already installed on the cluster; the task here is to add the new node to the clustered configuration. This task is performed by executing the Oracle provided utility called "addnode" located in the clusterware_home/oui/bin directory. Oracle Clusterware has two files (Oracle cluster repository (OCR) and Oracle Cluster Synchronization service (CSS), voting disk) that contain information concerning the cluster and the applications managed by the Oracle Clusterware. These files need to be updated with the information concerning the new node.
I will do the addnode activity from first node (RAC1).

RAC1 :

[root@rac1 ~]# xhost +
Go to the direcory, clusterware_home/oui/bin

[oracle@rac1 bin]$ ./addNode.sh

Link for Extending Oracle Clusterware to new node

Verify Clusterware Installation :

Verify Cluster Services:

[oracle@rac3 ~]$ /u01/app/crs/bin/crs_stat -t

Check Cluster Nodes:

[oracle@rac1 ~]$ /u01/app/crs/bin/olsnodes -n

Check CRS Status:

[oracle@rac3 ~]$ /u01/app/crs/bin/crsctl check crs

Check Oracle Clusterware files:

[oracle@rac3 ~]$ ls -l /etc/init.d/init.*

Extend Oracle Database Software to New Node(RAC3):

Note: Extend the Oracle Database software to new node from RAC1.

The next step is to install the Oracle database software on the new node (RAC3). Oracle has provided a new executable called "addNode.sh" located in the $ORACLE_HOME/oui/bin directory.

RAC1:

[root@rac1 ~]# xhost +
Go to the direcory, oracle_home/oui/bin

[oracle@rac1 bin]$ ./addNode.sh

Link for Extending Oracle Database to new node

Set Oracle User Environment:

RAC3:

[oracle@rac3 ~]$ vi ~/.bash_profile

export ORACLE_BASE=/u01/app/oracle
export ORACLE_HOME=$ORACLE_BASE/product/10.2.0/db_1
export ORA_CRS_HOME=/u01/app/crs
export ORACLE_SID=racdb3
export PATH=$PATH:$HOME/bin:$ORACLE_HOME/bin
umask 022

For all the screenshots, please visit ::: http://www.sensehaze.com/mydata/resources_section/rac/addnode/index.php

Run netca to add Listener to new node(RAC3):

Once the RDBMS software is installed, it is a good practice to run netca before moving to the next step. Netca will configure all required network files and parameters such as the listener, sql*net, and tnsnames.ora files.

RAC1:

[oracle@rac1 bin]$ netca

Link for adding Listener to new node(RAC3)

Add Instance to New Node:

DBCA has all the required options to add additional instances to the cluster.

Requirements:

Make a full cold backup of the database before commencing the upgrade process
Oracle Clusterware should be running on all nodes.

RAC1:

[oracle@rac1 ~]$ dbca

Link for adding Instance to new node(RAC3)

At this stage, the following is true:
-- The clusterware has been installed on node RAC3 and is now part of the cluster.
-- The Oracle software has been installed on node RAC3.
-- The ASM3 and new Oracle instance RACDB3 has been created and configured on RAC3.

Verify that the upgrade is successful:

Verify the Instance :

Verify that all instances in the cluster are started, using the GV$INSTANCE view from any of the participating instances.

SQL> select instance_name from gv$instance ;

Check Cluster Services :

[oracle@rac1 ~]$ crs_stat -t

For all the screenshots, please visit ::: http://www.sensehaze.com/mydata/resources_section/rac/addnode/index.php

Creating RMAN Recovery Catalog

2012-02-09T07:55:00.000-08:00

Creating RMAN Recovery Catalog::

Overview:

This article is a comprehensive guide for Creation of RMAN Recovery Catalog.

RMAN can be used either with or without a recovery catalog. A recovery catalog is a schema stored in a database that tracks backups and stores scripts for use in RMAN backup and recovery situations. Generally, RMAN catalog schema be placed on a server separate from the main servers.

Please do keep in mind that this article should not be considered a substitution of the official guide from Oracle (http://www.oracle.com). The below mentioned link can be used to download the official documentation for RMAN Recovery Catalog.

http://docs.oracle.com/cd/B19306_01/backup.102/b14191/rcmcatdb.htm#BRADV179s

For the screenshots of the steps, please visit the following link:: http://www.sensehaze.com/mydata/resources_section/bck_rec/recv_catalog_rman/index.php

Disk Space Allocation for the Recovery Catalog Database:

If we are creating our recovery catalog in an already-existing database, add enough space to hold the default tablespace to the recovery catalog schema. If we are creating a new database to hold our recovery catalog, then, in addition to the space for the recovery catalog schema itself, we must allow space for other files in the recovery catalog database:

SYSTEM tablespace
Temporary tablespaces
Rollback segment tablespaces
Online redo log files

Typical Recovery Catalog Space Requirements for 1 Year

Type of Space	Space Requirement
SYSTEM tablespace	90 MB
Temp tablespace	5 MB
Rollback or undo tablespace	5 MB
Recovery catalog tablespace	15 MB for each database registered in the recovery catalog
Online redo logs	1 MB each (3 groups, each with 2 members)

Note : For the purpose of this guide i will use a separate database (Catalog DBName - CATALOG).

Create a user and schema for Recovery Catalog:

Start SQL*Plus and connect as administrator-privileged-user to the database containing the recovery catalog.

cmd > set ORACLE_SID=CATALOG
cmd > sqlplus sys/sys as sysdba

Create Catalog Tablespace:

SQL> create tablespace reco_cat
datafile 'E:\app\admin\oradata\catalog\reco_cat.dbf' SIZE 100m ;

Create Catalog User:

SQL> CREATE USER rman IDENTIFIED BY rman
DEFAULT TABLESPACE reco_cat
TEMPORARY TABLESPACE temp
QUOTA UNLIMITED ON reco_cat;

Grant RECOVERY_CATALOG_OWNER role to the schema owner:

SQL> GRANT RECOVERY_CATALOG_OWNER, CONNECT, RESOURCE TO rman;

For the screenshots of the steps, please visit the following link:: http://www.sensehaze.com/mydata/resources_section/bck_rec/recv_catalog_rman/index.php

Create the Recovery Catalog:

Connect to the database that will contain the catalog as the catalog owner.

CMD> rman CATALOG rman/rman@catalog

Run the CREATE CATALOG command to create the catalog. The creation of the catalog can take several minutes.

RMAN> CREATE CATALOG ;

Register a Database with RMAN:

After making sure the recovery catalog database is open, connect RMAN to the target database and recovery catalog database.

CMD> rman target sys/sys@mydb CATALOG rman/rman@catalog

If the target database is not mounted, then mount or open it.

RMAN> STARTUP MOUNT ;
-or-
RMAN> STARTUP OPEN ;

RMAN> REGISTER DATABASE ;

RMAN creates rows in the catalog tables to contain information about the target database, then copies all pertinent data about the target database from the control file into the catalog, synchronizing the catalog with the control file.

The database can now be operated on using the RMAN utility with catalog option.

For the screenshots of the steps, please visit the following link:: http://www.sensehaze.com/mydata/resources_section/bck_rec/recv_catalog_rman/index.php

Oracle Database 11g R2 (11.2.0.2) RAC One Node Installation On Solaris 10

2012-02-06T07:04:00.000-08:00

Oracle Database 11g R2 (11.2.0.2) RAC One Node Installation On Solaris 10 (x86-64)::

In this article we are going to learn Oracle Database 11g R2 (11.2.0.2) RAC One Node Installation On Solaris 10 (x86-64).

Overview:

This article is a comprehensive guide for Oracle Database 11g R2 (11.2.0.2) RAC One Node Installation On Solaris 10 (x86-64).
Oracle RAC One Node is a single instance of an Oracle Real Application Cluster database that runs on one node in a cluster. This option adds to the flexibility that Oracle offers for database consolidation. We can consolidate many databases into one cluster while also providing the high availability benefits of failover protection, online rolling patch application, and rolling upgrades for the operating system.

http://docs.oracle.com/cd/E11882_01/rac.112/e16795/onenode.htm

Objective of the Article:

By the time we finish this article, we should be able to understand the following:

(1)Basic idea of RAC One Node.

(2)Use of Openfiler for shared storage Configuration.

(3)Oracle Grid Infrastructure 11.2.0.2 installation for Cluster.

(4)Oracle Database 11.2.0.2 installation for RAC One Node.

(5)Database creation for RAC One Node.

Softwares used:

Operating System	Solaris 10 - 64bit (Both the nodes).
Shared Storage	Openfiler
Oracle Grid Infrastructure	11.2.0.2 for solaris x64
Oracle Database	11.2.0.2 for solaris x64

Install Solaris 10 64-bit O/S:

Install Solaris 10 64-bit Operating System on all the RAC nodes of your setup ( Here two nodes ).

Network Configuration for Node1:

eth0(e1000g0)
Primary Network Interface	e1000g0
Hostname	racnode1
Dynamic IP configuration (DHCP)	OFF
IP Address	192.168.15.100
System Part of Subnet	Yes
NetMask(Prefix)	255.255.255.0
Enable IPv6	No
Default Route	Yes
Router IP Address	192.168.15.1

eth1(e1000g1)
Secondary Network Interface	e1000g1
Hostname	racnode1-priv
Dynamic IP configuration (DHCP)	OFF
IP Address	192.168.16.100
System Part of Subnet	Yes
NetMask(Prefix)	255.255.255.0
Enable IPv6	No
Default Route	No

No
Default Route	No

Network Configuration for Node2:

eth0(e1000g0)
Primary Network Interface	e1000g0
Hostname	racnode2
Dynamic IP configuration (DHCP)	OFF
IP Address	192.168.15.101
System Part of Subnet	Yes
NetMask(Prefix)	255.255.255.0
Enable IPv6	No
Default Route	Yes
Router IP Address	192.168.15.1

eth1(e1000g1)
Secondary Network Interface	e1000g1
Hostname	racnode2-priv
Dynamic IP configuration (DHCP)	OFF
IP Address	192.168.16.101
System Part of Subnet	Yes
NetMask(Prefix)	255.255.255.0
Enable IPv6	No
Default Route	No

For more information about Solaris Operating System and its installation/configuration, please visit the below mentioned link:http://docs.oracle.com/cd/E19253-01/index.html

Install Openfiler:

Openfiler is a free browser-based network storage management utility that supports file-based Network Attached Storage (NAS) and block-based Storage Area Networking (SAN) in a single framework. Openfiler supports CIFS, NFS, HTTP/DAV, FTP, iSCSI technology.

Install Openfiler for configuring Shared-storage.

Network Configuration for Openfiler:

eth0
Dynamic IP configuration (DHCP)	OFF
Host Name	openfiler
IP Address	192.168.15.50
NetMask(Prefix)	255.255.255.0
Enable IPv6	No
Activate on boot	Yes
Default Gateway Address	192.168.15.1

eth1
Dynamic IP configuration (DHCP)	OFF
IP Address	192.168.16.50
NetMask(Prefix)	255.255.255.0
Enable IPv6	No
Activate on boot	Yes

For accessing openfiler storage:
https://192.168.15.50:446
username -- openfiler
password -- password

For more information about the installation of openfiler, please visit the following link : www.openfiler.com/learn/how-to/graphical-installation

Network Configuration:

Network Hardware Requirements:

Each node must have at least two network interfaces — one for the public network and one for the private network.
Public interface names must be the same for all nodes. If the public interface on one node uses the network adapter e1000g0, then you must configure e1000g0 as the public interface on all nodes.
The network adapter for the public interface must support TCP/IP.
For the private network, the endpoints of all designated interconnect interfaces must be completely reachable on the network.

IP Address Requirements:

A public IP address for each node
A virtual IP address for each node
Three single client access name (SCAN) addresses for the cluster.

Note :For the purpose of this article, i have not used GNS and DNS. So i will use one SCAN IP Address.

Note :Perform the below mentioned network configuration tasks on both Oracle RAC nodes in the cluster.

Hostname Configuration (as root user):

bash-3.00# vi /etc/hostname.e1000g0

Output:
Node1 -- racnode1
Node2 -- racnode2

If the hostame is not set then edit the file properly.

bash-3.00# vi /etc/hostname.e1000g1

Output:
Node1 -- racnode1-priv
Node2 -- racnode2-priv

If the hostame is not set then edit the file properly.

IP Address Configuration (as root user):

bash-3.00# ifconfig -a

If the IP Addresses are not configured then configure them by using the command:

bash-3.00# ifconfig e1000gXs plumb ip_address/subnet up

Edit the /etc/hosts file (as root user):

Give details of Public IPs, Private IPs, Virtual IPs, Scan IP and Openfiler IPs.

In our Oracle RAC One Node configuration, we will use the following network settings:

Node1
/etc/hosts
#::1 localhost
127.0.0.1	localhost
#Public IPs
192.168.15.100	racnode1.mmm.com	racenode1
192.168.15.101	racnode2.mmm.com	racenode2
#Private IPs
192.168.16.100	racenode1-priv
192.168.16.101	racenode2-priv
#Virtual IPs
192.168.15.110	racnode1-vip.mmm.com	racenode1-vip
192.168.15.111	racnode2-vip.mmm.com	racenode2-vip
#SCAN IP
192.168.15.150	rac-cluster-scan.mmm.com	rac-cluster-scan
#Openfiler IPs
192.168.15.50	openfiler.mmm.com	openfiler
192.168.16.50	openfiler-priv

Node2
/etc/hosts
#::1 localhost
127.0.0.1	localhost
#Public IPs
192.168.15.100	racnode1.mmm.com	racenode1
192.168.15.101	racnode2.mmm.com	racenode2
#Private IPs
192.168.16.100	racenode1-priv
192.168.16.101	racenode2-priv
#Virtual IPs
192.168.15.110	racnode1-vip.mmm.com	racenode1-vip
192.168.15.111	racnode2-vip.mmm.com	racenode2-vip
#SCAN IP
192.168.15.150	rac-cluster-scan.mmm.com	rac-cluster-scan
#Openfiler IPs
192.168.15.50	openfiler.mmm.com	openfiler
192.168.16.50	openfiler-priv

Edit the "/etc/hosts" (as root user) file for giving the etries like above:

bash-3.00# vi /etc/hosts

Verify Network Connectivity:

Verify the network connectivity by using the "ping" command to test the connection between the nodes.

Node 1 (as root user):

bash-3.00# ping racnode1
bash-3.00# ping racnode1-priv
bash-3.00# ping racnode2
bash-3.00# ping racnode2-priv
bash-3.00# ping openfiler
bash-3.00# ping openfiler-priv

Node 2 (as root user):

bash-3.00# ping racnode1
bash-3.00# ping racnode1-priv
bash-3.00# ping racnode2
bash-3.00# ping racnode2-priv
bash-3.00# ping openfiler
bash-3.00# ping openfiler-priv

Openfiler (as root user):

bash-3.00# ping racnode1
bash-3.00# ping racnode1-priv
bash-3.00# ping racnode2
bash-3.00# ping racnode2-priv
bash-3.00# ping openfiler
bash-3.00# ping openfiler-priv

Hardware Configuration:

Minimum Hardware Requirements:

At least 2 GB of RAM for Oracle Cluster installations.
At least 1024 x 768 display resolution, so that OUI displays correctly.
1 GB of space in the /tmp directory.
6.5 GB of space for the Oracle Grid Infrastructure for a Cluster home (Grid home) and at least 4 GB of available disk space for the Oracle Database home directory.
Swap space equivalent to the multiple of the available RAM.

Available RAM Swap Space Required

Between 2 GB and 16 GB Equal to the size of RAM

More than 16 GB 16 GB

Node 1 (as root user):

Checking RAM Size:
bash-3.00# /usr/sbin/prtconf | grep "Memory size"

Checking SWAP Size:
bash-3.00# /usr/sbin/swap -s

Checking /tmp Space:
bash-3.00# df -kh

Node 2 (as root user):

Checking RAM Size:
bash-3.00# /usr/sbin/prtconf | grep "Memory size"

Checking SWAP Size:
bash-3.00# /usr/sbin/swap -s

Checking /tmp Space:
bash-3.00# df -kh

Synchronize time on ALL Nodes:

We should ensure that the date and time settings on all nodes are set as closely as possible to the same date and time.Time may be kept in sync with NTP or by using Oracle Cluster Time Synchronization Service (ctssd).
Note:For the purpose of this guide i will not use NTP. So i will disable NTP on all the RAC Nodes.

Disable NTP Service:

Node 1 (as root user):

bash-3.00# /usr/sbin/svcadm disable ntp

Node 2 (as root user):

bash-3.00# /usr/sbin/svcadm disable ntp

For setting time on the nodes use the command:
bash-3.0.0 date -u new_date_and_time

Automatic SSH Configuration During Installation:

To install Oracle software, SSH connectivity should be set up between all cluster member nodes. OUI uses the ssh and scp commands during installation to run remote commands on and copy files to the other cluster nodes. We must configure SSH so that these commands do not prompt for a password.

create SSH soft links:

By default, OUI searches for SSH public keys in the directory "/usr/local/etc/" and "ssh-keygen" binaries in "/usr/local/bin". However, on Oracle Solaris, SSH public keys typically are located in the path "/etc/ssh", and "ssh-keygen" binaries are located in the path "/usr/bin". To ensure that OUI can set up SSH, use the following command to create soft links:

Node 1 (as root user):

bash-3.00# mkdir -p /usr/local/etc
bash-3.00# mkdir -p /usr/local/bin
bash-3.00# ln -s /etc/ssh /usr/local/etc
bash-3.00# ln -s /usr/bin /usr/local/bin

Node 2 (as root user):

bash-3.00# mkdir -p /usr/local/etc
bash-3.00# mkdir -p /usr/local/bin
bash-3.00# ln -s /etc/ssh /usr/local/etc
bash-3.00# ln -s /usr/bin /usr/local/bin

Set SSH LoginGraceTime to unlimited:

Edit the SSH daemon configuration file "/etc/ssh/sshd_config" on all cluster nodes to set the timeout wait to unlimited: "LoginGraceTime 0"

Node 1 (as root user):

bash-3.00# vi /etc/ssh/sshd_config
LoginGraceTime 0

Node 2 (as root user):

bash-3.00# vi /etc/ssh/sshd_config
LoginGraceTime 0

Check Required Packages:

List of Required Packages:

SUNWarc
SUNWbtool
SUNWcsl
SUNWhea
SUNWlibC
SUNWlibm
SUNWlibms
SUNWsprot
SUNWtoo
SUNWi1of
SUNWi1cs
SUNWi15cs
SUNWxwfnt
SUNxwplt
SUNWmfrun
SUNWxwplr
SUNWxwdv
SUNWgcc
SUNWuiu8
SUNWpool
SUNWpoolr

Node 1 (as root user):

bash-3.00# pkginfo -i pkg_name

If the package(s) are not installed, then mount the O/S disc and install the package(s).

bash-3.00# pkgadd -d . pkg_name

Node 2 (as root user):

bash-3.00# pkginfo -i pkg_name

If the package(s) are not installed, then mount the O/S disc and install the package(s).

bash-3.00# pkgadd -d . pkg_name

Creation of Users and Groups:

For the purpose of this guide, i will create only two groups. Oracle Inventory group (oinstall), and a single group (dba) as the OSDBA, OSASM and OSDBA for Oracle ASM groups.
For the purpose of this guide, i will create two users namely GRID(Grid Infra Owner) and ORACLE(Oracle Software Owner).

bash-3.00# /usr/sbin/groupadd -g 1000 oinstall
bash-3.00# /usr/sbin/groupadd -g 1031 dba

bash-3.00# /usr/sbin/useradd –u 1100 –g oinstall –G dba –d /export/home/grid grid
bash-3.00# /usr/sbin/useradd –u 1101 –g oinstall –G dba –d /export/home/oracle oracle

bash-3.00# id grid
bash-3.00# id oracle
bash-3.00# passwd grid
bash-3.00# passwd oracle

bash-3.00# mkdir /export/home/grid
bash-3.00# chmod –R 775 /export/home/grid
bash-3.00# chown -R grid:oinstall /export/home/grid

bash-3.00# mkdir /export/home/oracle
bash-3.00# chmod –R 775 /export/home/oracle
bash-3.00# chown -R oracle:oinstall /export/home/oracle

Configure Kernel Parameters:

Verify UDP and TCP Kernel Parameters:

UDP/TCP Parameters and their Recomended Values:

Parameter	Value
udp_xmit_hiwat	65535
udp_recv_hiwat	65535
tcp_smallest_anon_port	9000
tcp_largest_anon_port	65500
udp_smallest_anon_port	9000
udp_largest_anon_port	65500

Node 1 (as root user):

bash-3.00# /usr/sbin/ndd /dev/udp udp_xmit_hiwat
bash-3.00# /usr/sbin/ndd /dev/udp udp_recv_hiwat
bash-3.00# /usr/sbin/ndd /dev/tcp tcp_smallest_anon_port tcp_largest_anon_port
bash-3.00# /usr/sbin/ndd /dev/udp udp_smallest_anon_port udp_largest_anon_port

For setting these values, do the following:

bash-3.00# /usr/sbin/ndd -set /dev/udp udp_xmit_hiwat 65536
bash-3.00# /usr/sbin/ndd -set /dev/udp udp_recv_hiwat 65536
bash-3.00# /usr/sbin/ndd -set /dev/tcp tcp_smallest_anon_port 9000
bash-3.00# /usr/sbin/ndd -set /dev/tcp tcp_largest_anon_port 65500
bash-3.00# /usr/sbin/ndd -set /dev/udp udp_smallest_anon_port 9000
bash-3.00# /usr/sbin/ndd -set /dev/udp udp_largest_anon_port 65500

To set the UDP/TCP values for when the system restarts, the ndd commands have to be included in a system startup script. The following script in "/etc/rc2.d/S99ndd" sets the parameters:

bash-3.00# vi /etc/rc2.d/s99ndd
/usr/sbin/ndd -set /dev/udp udp_xmit_hiwat 65536
/usr/sbin/ndd -set /dev/udp udp_recv_hiwat 65536
/usr/sbin/ndd -set /dev/tcp tcp_smallest_anon_port 9000
/usr/sbin/ndd -set /dev/tcp tcp_largest_anon_port 65500
/usr/sbin/ndd -set /dev/udp udp_smallest_anon_port 9000
/usr/sbin/ndd -set /dev/udp udp_largest_anon_port 65500

Node 2 (as root user):

For setting these values, do the following:

To set the UDP/TCP values for when the system restarts, the ndd commands have to be included in a system startup script. The following script in "/etc/rc2.d/S99ndd" sets the parameters:

Set Maximum user processes:

Edit the "/etc/system" file of all the nodes:

bash-3.00# vi /etc/system
set maxusers=16384

Creation of User Project:

Node 1 and 2 (as root user):

If you've performed a default installation, it is likely that the only kernel parameter you need to alter is "max-shm-memory" to meet the minimum installation requirements.

For GRID User:

To create user project, issue the following command:

bash-3.00# projadd grid

Append the following line to the "/etc/user_attr" file:
grid::::project=grid

To check the current value, issue the following command:

bash-3.00# prctl -n project.max-shm-memory -i project grid project: 100: grid

Note:To reset this value, make sure at least one session is logged in as the "grid" user, then from the root user issue the following commands.

To dynamically reset the value, issue the following command:

bash-3.00# prctl -n project.max-shm-memory -v 4gb -r -i project grid

Make changes to the "/etc/project" file so that the value is persistent between reboots, issue the following command:

bash-3.00# projmod -s -K "project.max-shm-memory=(priv,4gb,deny)" grid
bash-3.00# cat /etc/project

Similarrly repeat the above for oracle user.

Reboot your RAC Nodes before attempting to install Oracle binaries.

Configure Shell Limits:

Oracle recommends that we set shell limits and system configuration parameters as described in this section.

Recommended Shell Limits for Oracle Solaris Systems:

Shell Limit	Recommended Value
TIME	-1 (Unlimited)
FILE	-1 (Unlimited)
DATA	Minimum value: 1048576
STACK	Minimum value: 32768
NOFILES	Minimum value: 1024
VMEMORY	Minimum value: 4194304

To see the shell limit of "GRID" user, issue the following command:

bash-3.00$ ulimit -a

To change the shell limit of "GRID" user, issue the following command:

bash-3.00$ ulimit -parameter_name new_val

To see the shell limit of "ORACLE" user, issue the following command:

bash-3.00$ ulimit -a

To change the shell limit of "ORACLE" user, issue the following command:

bash-3.00$ ulimit -parameter_name new_val

Create Oracle Binaries Directory:

To create the Grid Infrastructure home directory and Oracle Database directory , enter the following commands as the root user:

bash-3.00# mkdir -p /u01/app/11.2.0/grid
bash-3.00# mkdir -p /u01/app/grid
bash-3.00# mkdir -p /u01/app/oracle

bash-3.00# chown grid:oinstall /u01/app/11.2.0/grid
bash-3.00# chown grid:oinstall /u01/app/grid
bash-3.00# chown -R grid:oinstall /u01

bash-3.00# chown oracle:oinstall /u01/app/oracle
bash-3.00# chmod -R 775 /u01/

Do this on both the nodes.

Configure iSCSI Volumes using Openfiler:

Perform the following configuration task on the storage server (openfiler).

Openfiler administration is performed using the Openfiler Storage Control Center - a browser based tool over an https connection on port 446.

Accessing the Openfiler Storage control Center:

https://openfiler:446

Username : openfiler
Password : password

Link for configuration of iSCSI Volumes using Openfiler

For more information about Openfiler, visit the following link: www.openfiler.com

Connect to iSCSI-Target with iSCSI Initiator in Solaris:

iSCSI Packages Required for Solaris 10:

SUNWiscsir - Sun iSCSI Device Driver (root)
SUNWiscsitgtr - Sun iSCSI Target (Root)
SUNWiscsitgtu - Sun iSCSI Target (Usr)
SUNWiscsiu - Sun iSCSI Management Utilities (usr)

bash-3.00# pkginfo -i pkg_name

If the package(s) are not installed, then mount the installer disk and install the above mentioned packages.

bash-3.00# pkgadd -d pkg_name

Configure and Enable iSCSI Target Discovery:

Run the following to view the hard-disk devices:

Run the following from the nodes to discover all available iSCSI LUNs.

bash-3.00# iscsiadm add discovery-address 192.168.16.50:3260
bash-3.00# iscsiadm modify discovery --sendtargets enable
bash-3.00# devfsadm -i iscsi
bash-3.00# format

after running "iscsiadm" command, all the devices are discovered on both the nodes.

Partition and Label the LUNs:

Now that the new iSCSI LUNs have been successfully discovered, the next step is to create new partitions on the LUNs.

For partitioning , labeling and giving volname to the LUNs , use the "FORMAT" command which is described in the mentioned link below:

Link for Partitioning and Labeling LUNs

Installation of Grid Infrastructure:

Mount the Grid Installer Disc:

I have created a directory for the grid infrastructure software and copied the setup files in that directory.

Note:The installation will be performed from one of the nodes, for the purpose of this guide i will do the installation from Node 1.

Node 1 (as root user):

bash-3.00# mkdir /softs
bash-3.00# chmod -R 775 /softs/
bash-3.00# chown -R grid:oinstall /softs/

Copy the setup files in the above created directory.

Link for Grid Infrastructure Installation

Configure GRID User Environment:

Node 1 (as grid user):

Create the "grid_profile" file with the entries similar to the following:
export ORACLE_HOME=/u01/app/11.2.0/grid
export ORACLE_SID=+ASM1
export LD_LIBRARY_PATH=$ORACLE_HOME/lib
export PATH=$PATH:$ORACLE_HOME/bin
umask 022

(As grid user)bash-3.00$ chmod +x grid_profile
bash-3.00$ . grid_profile
bash-3.00$ echo $ORACLE_HOME

Node 2 (as grid user):

Create the "grid_profile" file with the entries similar to the following:
export ORACLE_HOME=/u01/app/11.2.0/grid
export ORACLE_SID=+ASM2
export LD_LIBRARY_PATH=$ORACLE_HOME/lib
export PATH=$PATH:$ORACLE_HOME/bin
umask 022

(As grid user)bash-3.00$ chmod +x grid_profile
bash-3.00$ . grid_profile
bash-3.00$ echo $ORACLE_HOME

For all the screenshots, please visit the link::: http://www.sensehaze.com/index.php/oracle-database/87-real-application-cluster/104-rac11g-1node-solaris

Verify Oracle Clusterware Installation:

After installing Oracle Grid Infrastructure, we should run several test commands to verify whether the installation was successful or not.

Run the following commands on both the nodes of the cluster as the 'grid' user.

Link for verification of Oracle Clusterware Installation

Creation of ASM Disk Groups for Data and FRA:

Run ASM Configuration Assistant (asmca) as the 'grid' user from one of the nodes in the cluster to create the additional ASM disk groups which will be used to create the RAC database. For the purpose of this article i will configure ASM Disks from Node 1.

I will create additional ASM disk groups using the ASM Configuration Assistant (asmca), one for DATA and other for FRA.

First, we will have to add new disk discovery string in the path. For doing so connect to the ASM instance from one of the nodes and add the new disk-discovery-string in the path.

Node 1 (as grid user):

Connect to your ASM instance and run the following query:
SQL> alter system set asm_diskstring='/dev/crs','/dev/data','/dev/fra'

Link for creation of ASM Diskgroups

Installation of Oracle Database Software for RAC One Node:

We will perform the Oracle Database software installation from Node 1. The Oracle Database software will be installed on both the nodes by the OUI using SSH.

Node 1 (as root user):

bash-3.00# xhost +

Link for Installation of Oracle Database Software for RAC One Node

Configure ORACLE User Environment:

Node 1 (as oracle user):

Create the "db_profile" file with the entries similar to the following:
export ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1
export LD_LIBRARY_PATH=$ORACLE_HOME/lib
export PATH=$PATH:$ORACLE_HOME/bin
umask 022

(As oracle user)bash-3.00$ chmod +x db_profile
bash-3.00$ . db_profile
bash-3.00$ echo $ORACLE_HOME

Node 2 (as oracle user):

(As oracle user)bash-3.00$ chmod +x db_profile
bash-3.00$ . db_profile
bash-3.00$ echo $ORACLE_HOME

Create Cluster Database:

The database creation process will be performed by one of the RAC Nodes. In this guide we will use racnode1 for database creation.

Use the DBCA utility to create the cluster database.

Node 1 (as root user):

bash-3.00# xhost +

Link for Creation of Cluster Database

Connect to the Database:

As oracle user:

bash-3.00$ sqlplus sys/sys@racdb as sysdba

Check RAC One Node Status:

As oracle user:

(Node1)bash-3.00$ srvctl config database -d racdb

(Node2)bash-3.00$ srvctl config database -d racdb

Congrats! This finishes Oracle RAC One Node Installation on Solaris 10.

Oracle Remote Diagnostics Agent (RDA) utility

2012-01-10T08:20:00.000-08:00

Oracle Remote Diagnostics Agent (RDA) utility:::

In this article we are going to learn how to generate Oracle Remote Diagnostics Agent (RDA) Report.

Overview:

This article is a comprehensive guide for the generation of Oracle Remote Diagnostics Agent (RDA) Report.

Please do keep in mind that, this article should not be considered a substitution of the official guide from Oracle (http://www.oracle.com).

RDA (Remote Diagnostics Agent) utility and its documentation can be downloaded from Oracle Support (Metalink) website (Doc ID: 314422.1) .

Steps and Commands:

	UNIX / LINUX	WINDOWS
Unzip Files	use Unix/Linux utility	use any Windows utility
Instructions	README_Unix.txt/README_Linux.txt	README_Windows.txt
Verify Installation	rda.sh -cv	rda.cmd -cv
Run Setup	rda.sh -S or rda.pl -S	rda.cmd -S or rda.pl -S
Run RDA	rda.sh -v or rda.pl -v	rda.cmd -v
To view RDA	Open RDA_INDEX.htm from the RDA output directory

Connection to Database:

Open command prompt.

cmd> set ORACLE_SID=mydb
cmd> sqlplus / as sysdba

And you will be connected to the database.

For all the screenshots, please visit the following link:: http://www.sensehaze.com/mydata/resources_section/perf_tune/rda/index.php

Oracle Remote Diagnostic Agent (RDA) Report Generation:

Note: I am generating RDA Report on Windows for this article.

Unzip Files:

Unzip the downloaded RDA Utility to a directory ( Here E:/rda ).

Read Instructions:

Go to the directory, where we have unzipped the files and we can read the instructions given in the "Readme_O/S.txt" file.

Verify Installation:

Open command prompt and navigate to the RDA directory.

cmd> rda.cmd -cv

Run Setup:

Open command prompt and navigate to the RDA directory.

cmd> rda.cmd -S

The script continues on for many more pages as part of the configuration. Choose the options according to your Report need.

Run RDA:

Open command prompt and navigate to the RDA directory.

cmd> rda.cmd -v

View RDA Report:

Open "RDA__index.htm" from the RDA output directory to view the report.

Our RDA Report has been generated.

For all the screenshots, please visit the following link:: http://www.sensehaze.com/mydata/resources_section/perf_tune/rda/index.php

Upgrade Oracle Database 11g R1 to Oracle Database 11g R2

2012-01-04T06:25:00.000-08:00

Upgrade Oracle Database 11g R1 to Oracle Database 11g R2::

In this article we are going to learn how to Upgrade Oracle Database 11g R1 (11.1.0.7.0) to Oracle Database 11g R2 (11.2.0.1.0).

Overview:

This article is a comprehensive guide for the Upgradation of Oracle Database 11g R1 (11.1.0.7.0) to Oracle Database 11g R2 (11.2.0.1.0).

Please do keep in mind that, this article should not be considered a substitution of the official installation guide and release note from Oracle (http://www.oracle.com).

The below mentioned link can be used to download the official guide for the Upgradation of Oracle Database 11g R1 (11.1.0.7.0) to Oracle Database 11g R2 (11.2.0.1.0).

http://docs.oracle.com/cd/B28359_01/install.111/b32305/toc.htm

Objective of the Article:

By the time we finish this article, we should be able to understand the following:

(1)Installation of oracle database (11.1.0.7.0) x64 on Windows 64bit

(2)Configuration of Oracle Net listener(http://download.oracle.com/docs/cd/E11882_01/network.112/e10836/listenercfg.htm

(3)Installation of oracle database (11.2.0.1.0) x64 on Windows 64bit

(4)Upgradation of Oracle Database 11g R1 (11.1.0.7.0) to Oracle Database 11g R2 (11.2.0.1.0).

Names and Values Used:

	Database	Target Database
Name	mydb	mydb
Version	11.1.0.7.0	11.2.0.1.0
Oracle Home	E:\app\admin\product\11.1.0\db_1	E:\app\admin\product\11.2.0\db_1

For all the screenshots, please visit the website::: upgradation of oracle database from 11g R1 to 11g R2

Download Oracle Database Software:

First we have to download the required Oracle Database software packages from the Oracle Technology Network (OTN) or Oracle Edelivery Site and then extract the Oracle Database software packages.

Download the Oracle Database 11g Release 2 (11.2.0.1.0) Software for Windows x64 Operating System Environment.

Link for downloading oracle Database Software Package::
http://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html

Installation of Oracle Database:

New Oracle Home (11.2.0.1.0) -- E:\app\admin\product\11.2.0\db_1

Go to the extracted folder of Oracle Database Software package downloaded in the previous step. Go inside the “database” named directory and you will find “setup.exe” there.

Launch “setup.exe” to begin your installation.

Install Oracle Database 11.2.0.1.0 with "Software Only" option. You can follow the below mentioned link to install the software:
Installation of Oracle Database 11g R2 on Windows

Start 11.1.0.7 database:

Open command prompt.

cmd> set ORACLE_SID=mydb
cmd> sqlplus / as sysdba

And you will be connected to the database.

For all the screenshots, please visit the website::: upgradation of oracle database from 11g R1 to 11g R2

Listener Creation:

Stop the "old listener" and run "netca" from the "new home".

Open command prompt and run “netca” from the new home

Copy tnsnames.ora from old home to new home and make necessary changes if required, or we can create it here also.

If you want to create new "tnsnames" file then , run "netca" again.

Open command prompt and type "netca" .
Select "Local Net Service Name Configuration" and click "Next".

Run utlu112i.sql:

Copy the "utlu112i.sql" from new "Oracle_Home" to any "temprary directory" or to the "old Oracle_home". I copied the "utlu112i.sql" to the old home.

Connect to the database and run "utlu112i.sql" from the old home to check whether all the prereqs have matched.

Adjust the warnings / errors shown by Pre-Upgrade Information tool.

Upgrade from 11.1.0.7.0 to 11.2.0.1.0:

Execute the "DBUA" from new "Oracle_Home" (11.2.0.1.0).

cmd> dbua

For all the screenshots, please visit the website::: upgradation of oracle database from 11g R1 to 11g R2

Connection to Database:

Open command prompt.

cmd> set ORACLE_SID=mydb
cmd> sqlplus / as sysdba

And you will be connected to the database.

Congrats Our database is upgraded.

For all the screenshots, please visit the website::: upgradation of oracle database from 11g R1 to 11g R2

Oracle Database 11gR1 64bit installation on Windows7 x64

2012-01-04T06:15:00.000-08:00

Oracle Database 11gR1 64bit installation on Windows7 x64::

In this article we are going to learn how to install oracle database 11gR1 64 bit (11.1.0.7.0) on Windows 7.

Download Oracle Database Software:

First we have to download the required Oracle Database software packages from the Oracle Technology Network (OTN) or Oracle Edelivery Site and then extract the Oracle Database Software packages.

Download the Oracle Database 11g Release 1 (11.1.0.7.0) Software for Windows x64 Operating System Environment.

Link for downloading oracle Database Software Package::
http://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html

Installation of Oracle Database:

Go to the extracted folder of Oracle Database Software package downloaded in the previous step. Go inside the “database” named directory and you will find “setup.exe” there.

Launch “setup.exe” to begin your installation.

For all the screenshots , Please visit the link::: http://www.sensehaze.com/mydata/resources_section/installation/win_1117_64/index.php

Listener Creation:

Open command prompt and type “netca” as shown in the below screen:

Type the command “netca”.

Database Creation:

Type "dbca" on the command prompt:

Local Net Service Name Configuration:

Open command prompt and type "netca" .

Select "Local Net Service Name Configuration" and click "Next".

For all the screenshots , Please visit the link::: http://www.sensehaze.com/mydata/resources_section/installation/win_1117_64/index.php

Using SRVCTL for Administration of RAC Database

2011-12-24T06:03:00.000-08:00

Using SRVCTL for Administration of RAC Database :::

Overview:

This article is a comprehensive guide for Using SRVCTL for Administration of RAC Database.
The Server Control (SRVCTL) utility is installed on each node by default. We can use SRVCTL to start and stop the database and instances, manage configuration information, and to move or remove instances and services. We can also use SRVCTL to add services. SRVCTL also manages configuration information.

http://download.oracle.com/docs/cd/B19306_01/rac.102/b14197/srvctladmin.htm

Objective of the Article:

By the time we finish this article, we should be able to understand the following:

(1)Basic idea of Server Control (SRVCTL) utility.

(2)The use of Server Control (SRVCTL) utility for managing RAC Database.

Values and parameters used in the article:

Parameter	Node1	Node2
Hostname	RAC1	RAC2
Instance Name	RACDB1	RACDB2
RAC Database Name	RACDB

Summary of SRVCTL commands:

Command	Description
srvctl add	Adds the node applications, database, database instance, ASM instance, or service.
srvctl remove	Removes the node applications, database, database instance, ASM instance, or service.
srvctl config	Lists the configuration for the node applications, database, ASM instance, or service.
srvctl enable	Enables the database, database instance, ASM instance, or service.
srvctl disable	Disables the database, database instance, ASM instance, or service.
srvctl start	Starts the node applications, database, database instance, ASM instance, or service.
srvctl stop	Stops the node applications, database, database instance, ASM instance, or service.
srvctl modify	Modifies the node applications, database, database instance, or service configuration.
srvctl relocate	Relocates the service from one instance to another.
srvctl status	Obtains the status of the node applications, database, database instance, ASM instance, or service.
srvctl getenv	Displays the environment variable in the configuration for the node applications, database, database instance, or service.

SRVCTL Command Syntax and Options:

SRVCTL commands, objects, and options are case sensitive. Database, instance, and service names are case insensitive and case preserving. SRVCTL interprets the following command syntax:

command_prompt> srvctl command object [options]

In SRVCTL syntax:

srvctl is the command to start the SRVCTL utility.
command is a verb such as start, stop, or remove.
object is an object or target on which SRVCTL performs the command, such as database or instance.
options extend the use of a preceding command combination to include additional parameters for the command.

For all the screenshots, please visit the link::: http://www.sensehaze.com/mydata/resources_section/rac/srvctl/index.php

SRVCTL Command Examples:

Obtaining Command-Line Help for SRVCTL:

For Obtaining Command-Line Help for SRVCTL, from command prompt(terminal) type:

[oracle@rac1 ] srvctl -h

Obtaining version of SRVCTL:

For Obtaining version of SRVCTL, from command prompt(terminal) type:

[oracle@rac1 ] srvctl -v

Display configuration for our RAC database:

For displaying various configuration for our RAC database, from command prompt(terminal) type:

For configuration of database

[oracle@rac1 ] srvctl config database -d racdb

For configuration of services

[oracle@rac1 ] srvctl config service -d racdb

For configuration of nodeapps

[oracle@rac1 ] srvctl config nodeapps -n rac1

[oracle@rac1 ] srvctl config nodeapps -n rac2

For configuration of ASM

[oracle@rac1 ] srvctl config asm -n rac1

[oracle@rac1 ] srvctl config asm -n rac2

For configuration of listener

[oracle@rac1 ] srvctl config listener -n rac1

[oracle@rac1 ] srvctl config nodeapps -n rac2

SRVCTL enable option:

For enabling database/instance etc, of our RAC database, from command prompt(terminal) type:

For enabling database:

[oracle@rac1 ] srvctl enable database -d racdb

For enabling instance:

[oracle@rac1 ] srvctl enable instance -d racdb -i racdb1

[oracle@rac1 ] srvctl enable instance -d racdb -i racdb2

SRVCTL disable option:

For disabling database/instance etc, of our RAC database, from command prompt(terminal) type:

For disabling database:

[oracle@rac1 ] srvctl disable database -d racdb

[oracle@rac1 ] srvctl enable database -d racdb

For dsabling instance:

[oracle@rac1 ] srvctl disable instance -d racdb -i racdb1

[oracle@rac1 ] srvctl disable instance -d racdb -i racdb2

SRVCTL start option:

For starting database:

[oracle@rac1 ] srvctl start database -d racdb

For starting an instance:

[oracle@rac1 ] srvctl start instance -d racdb -i racdb1

For starting nodeapps:

[oracle@rac1 ] srvctl start nodeapps -n rac1

[oracle@rac1 ] srvctl start nodeapps -n rac2

For starting ASM:

[oracle@rac1 ] srvctl start asm -n rac1

[oracle@rac1 ] srvctl start asm -n rac2

For starting listener:

[oracle@rac1 ] srvctl start listener -n rac1

[oracle@rac1 ] srvctl start listener -n rac2

SRVCTL stop option:

For stopping database:

[oracle@rac1 ] srvctl stop database -d racdb

For stopping instance:

[oracle@rac1 ] srvctl stop instance -d racdb -i racdb1

SRVCTL status option:

For status of database:

[oracle@rac1 ] srvctl status database -d racdb

For status of instance(s):

[oracle@rac1 ] srvctl status instance -d racdb -i "racdb1,racdb2"

[oracle@rac1 ] srvctl status instance -d racdb -i racdb1

For status of service(s):

[oracle@rac1 ] srvctl status service -d racdb -s racdb_srvc

For all the screenshots, please visit the link::: http://www.sensehaze.com/mydata/resources_section/rac/srvctl/index.php

Data Guard Command-Line Interface (DGMGRL)

2011-12-16T22:29:00.000-08:00

In this article we are going to learn, Data Guard Command-Line Interface (DGMGRL).

Overview:

This article is a comprehensive guide for the use of Data Guard Command-Line Interface (DGMGRL). The Data Guard command-line interface (DGMGRL) enables us to manage a Data Guard broker configuration and its databases directly from the command line.
Data Guard Broker eliminates the need for the complex commands that are needed during role transitions – such as, switchover between a primary and a standby database.

http://docs.oracle.com/cd/E11882_01/server.112/e17023/dgmgrl.htm

Objective of the Article:

By the time we finish this article, we should be able to understand the following:

(1)How to utilize Data Guard Command Line Interface (DGMGRL).

(2)Performing switchover by DGMGRL utility.

Names and Parameter Values Used:

	Node1 (Primary)	Node2 (Standby)
Machine Name	DG1	DG2
IP Address	192.168.1.100	192.168.1.101
Oracle Database Version	11g Ent. R2(11.2.0.1)- 64 bit	11g Ent. R2(11.2.0.1)- 64 bit
DB Service Name	orcl	stdby
Oracle Software Owner	O/S User – oracle	O/S User – oracle

Prerequisites for Data Guard Broker Configuration:

We have to set initialization parameter DG_BROKER_START to a value of TRUE on both databases (primary and standby) so that Data Guard Broker background process (DMON) would start automatically whenever a Data Guard configuration was successfully implemented.

For setting "DG_BROKER_START" parameter to "TRUE", connect to the database and fire the below command (Do these from both the Nodes).
Do these from node 1:

[oracle@dg1 ~]export ORACLE_SID=orcl
[oracle@dg1 ~]sqlplus sys/sys@orcl as sysdba

SQL> select name , db_unique_name , database_role from v$database ;

SQL> show parameter dg_broker_start ;

If the output shows "FALSE", then we have to set it to "TRUE".

SQL> alter system set dg_broker_start = TRUE ;

Similarly do these activities from the second node (node2).

[oracle@dg2 ~]sqlplus sys/sys@stdby as sysdba

SQL> select name , db_unique_name , database_role from v$database ;

SQL> show parameter dg_broker_start ;

If the output shows "FALSE", then we have to set it to "TRUE".

SQL> alter system set dg_broker_start = TRUE ;

We must have SYSDBA privileges to use the Data Guard command-line interface. So do not include "AS SYSDBA" on the CONNECT command because SYSDBA is the default setting for this command.

Data Guard Broker configuration:

Start the Data Guard Command-Line Interface:

From the primary node (node1), open the terminal and connect to "DGMGRL" as the "SYS" user. As shown below:

[oracle@dg1 ~]dgmgrl
Then we will get the dgmgrl prompt. For connecting to the database, type:
DGMGRL> connect sys
Then we will be asked for password, Enter the correct password, then we will get connected to the database.

Create Data Guard Broker configuration for the primary database:

For creating Data Guard Broker configuration for the primary database (orcl), we will use "CREATE CONFIGURATION" command to initialize a Data Guard Broker configuration named "DG_orcl".
For doing so, type the following inside the DGMGRL prompt:

DGMGRL> CREATE CONFIGURATION 'DG_orcl' AS PRIMARY DATABASE IS orcl CONNECT IDENTIFIER IS orcl;

For all the screenshots , please visit the link::: http://www.sensehaze.com/mydata/resources_section/dataguard/dgmgrl/index.php

For confirming its creation, type "SHOW CONFIGURATION" in the "DGMGRL" prompt.

DGMGRL> SHOW CONFIGURATION ;

Add standby database(s) to the Data Guard Broker configuration:

To add a standby database to the current configuration, we will use "ADD DATABASE" command.
For doing so, type the following inside the DGMGRL prompt:

DGMGRL> ADD DATABASE 'stdby' AS CONNECT IDENTIFIER IS stdby;

For verifying the configuration, type "SHOW CONFIGURATION" in the "DGMGRL" prompt.

DGMGRL> SHOW CONFIGURATION ;

Enable the Data Guard Broker configuration:

For enabling Data Guard Broker configuration, issue the "ENABLE CONFIGURATION" command to activate the configuration.

Verify the successful activation of the primary and standby database(s) by using "SHOW DATABASE" command.

Perform a Switchover using Data Guard Broker:

Once all the above activities are completed successfully , we can perform siwtchover from DGMGRL prompt by issuing only one command "SWITCHOVER TO target_standby_database ;".
DGMGRL> SWITCHOVER to stdby ;

After execution of the above command, our primary database should be "stdby"(Node2) and our standby database should be "orcl"(Node1). Lets verify it by connecting to the databases and querying the view "V$DATABASE" on all the nodes.

SQL> select name , db_unique_name , database from v$database ;

To see whether logfiles are being transmitting or not, lets switch logfile. For doing logfile switch, type the below from primary database (node2):

SQL> alter system switch logfile;
SQL> archive log list ;

On the standby database (node1) check archive log list status.
SQL> archive log list ;

For all the screenshots , please visit the link::: http://www.sensehaze.com/mydata/resources_section/dataguard/dgmgrl/index.php

Perform a Revertback to original Primary Database:

We can Perform a Revertback to original Primary Database from DGMGRL prompt by issuing only one command "SWITCHOVER TO target_database ;".
DGMGRL> SWITCHOVER to orcl ;

After execution of the above command, our primary database should be "orcl"(Node1) again and our standby database should be "stdby"(Node2). Lets verify it by connecting to the databases and querying the view "V$DATABASE" on all the nodes.

SQL> select name , db_unique_name , database from v$database ;

To see whether logfiles are being transmitting or not, lets switch logfile. For doing logfile switch, type the below from primary database (node1):

SQL> alter system switch logfile;
SQL> archive log list ;

On the standby database (node2) check archive log list status.
SQL> archive log list ;

Convert Standby Database:

We can convert a physical standby database to a snapshot standby database, or revert the snapshot standby database back to a physical standby database byusing DGMGRL utility.

We are going to convert "Physical Standby Database(Node2-stdby)" to "Snapshot Standby Database" by using "DGMGRL" utility.
DGMGRL> CONVERT DATABASE stdby TO SNAPSHOT STANDBY ;

Similarly we can convert the snapshot standby database to physical standby database.

For all the screenshots , please visit the link::: http://www.sensehaze.com/mydata/resources_section/dataguard/dgmgrl/index.php

Available RAM	Swap Space Required
Between 2 GB and 16 GB	Equal to the size of RAM
More than 16 GB	16 GB