Oracle Database 10g R2 installation on RHEL5 x86

Overview:

This article is a comprehensive guide for the installation of Oracle Database 10g Release 2 (10.2.0.1.0) 32-bit on Redhat Enterprise Linux 5 (RHEL5) 32-bit Operating System Environment.

The official documentation for installation of Oracle Database 10g R2 32bit on Linux can be downloaded from the below mentioned link:
http://docs.oracle.com/cd/B19306_01/install.102/b15660/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 (10.2.0.1.0) x86 on Redhat Enterprise Linux 5 (RHEL5) x86.

(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 10g (10.2.0.1.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 Redhat Enterprise Linux-5 x86:

Install Redhat Enterprise Linux 5 x86 on your machine.

For More information about RHEL5 installation visit the below site::

Redhat Enterprise Linux 5 Installation.

Download Oracle Database Software:

We first 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 10g Release 2 (10.2.0.1.0) Software for Linux x86 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

To determine the RAM size, enter the following command:

[root@redhat1 ~]# 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 8 GB	Equal to the size of the RAM
More than 8 GB	0.75 times the size of RAM

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

[root@redhat1 ~]# 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 400 MB 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@redhat1 ~]# df -h /tmp

If there is less than 400 MB 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):

[root@redhat1 ~]# vim /etc/fstab

Go to the row containig tmpfs and replace "defaults" with "rw,size=1200m". (or the size you want).

N.B:After doing this we have to reboot the machine so that resized tmp value takes effect.

The above discussed method is for RHEL, for increasing tmpfs of other flavour of Linux O/S please visit the vendor's website.

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

Installation Type	Minimum Requirement for Software Files (GB)
Enterprise Edition	1.5
Standard Edition	1.5
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@redhat1 ~]# df -h

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

 For all the screenshots , please visit the link::: http://www.sensehaze.com 

Package Requirements Check:

After the installation of RHEL5 x86, the next task is to install all packages required by Oracle Database 10g R2 x86. 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 10g Release 2 (10.2) x86 on RHEL-5 x86:

• binutils-2.17.50.0.6
• compat-db-4.2.52
• compat-libstdc++-33-3.2.3
• compat-gcc-34-3.4.6
• compat-gcc-34-c++-3.4.6
• gcc-4.1.2
• gcc-c++-4.1.2
• glibc-2.5-24
• glibc-common-2.5
• glibc-devel-2.5
• glibc-headers-2.5
• libstdc++-4.1.2
• libstdc++-devel-4.1.2
• libaio-0.3.106
• libaio-devel-0.3.106
• libXp-1.0.0-
• make-3.81
• openmotif-2.3.0
• setarch-2.0
• sysstat-7.0.2

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

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

[root@redhat1 ~]# rpm -q package_name

e.g:  [root@redhat1 ~]# rpm –q compat-db-4.2.52-5.1.i386.rpm 

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

[root@redhat1 ~]# rpm -ivh package_name 

N.B: To use ODBC, you must also install the additional ODBC RPMs.

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

 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...

1. To determine whether "oinstall" group exists, type the following command:
   [root@redhat1 ~]# more /etc/oraInst.loc
   If the output shows oinstall group then the group exists and need not to be created.
   .
2. To determine whether "dba" group exists, type the following command:
   [root@redhat1 ~]#grep dba /etc/group
   If the output shows dba group then the group exists and need not to be created.
   .
3. To determine whether "oracle" user exists, type the following command:
   [root@redhat1 ~]#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=500(oracle) gid=500(oinstall) groups=501(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@redhat1 ~]#usermod -g oinstall -G dba oracle
   .
4. If the user or the required groups doesn't exist then create them as mentioned below:
   [root@redhat1 ~]# groupadd -g 501 oinstall
   [root@redhat1 ~]# groupadd -g 502 dba
   [root@redhat1 ~]# useradd -m -u 501 -g oinstall -G dba oracle
   Now check the status of "oracle" user.
   [root@redhat1 ~]# id oracle
   The output should be similar to following, indicating "oinstall" as primary and "dba" as secondary group.
   uid=500(oracle) gid=500(oinstall) groups=501(dba).
   Now set the password of "oracle" user.
   [root@redhat1 ~]# passwd oracle
   and input a password for "oracle" user.
5. 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@redhat1 ~]# 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@redhat1 ~]# 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.file-max	65536
kernel.shmall	2097152
kernel.shmmax	2147483648
kernel.shmmni	4096
kernel.sem	250 32000 100 128
net.ipv4.ip_local_port_range	1024 65000
net.core.rmem_default	262144
net.core.rmem_max	262144
net.core.wmem_default	262144
net.core.wmem_max	262144

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@redhat1 ~]# sysctl -p

 For all the screenshots , please visit the link::: http://www.sensehaze.com 

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

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

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

Edit the /etc/pam.d/login file and add following lines:

session required /lib/security/pam_limits.so
session required pam_limits.so

"Disable secure linux" and "Firewall" also.

Creation of Required Directories:

The next step is to create 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@redhat1 ~]# mkdir -p /u01/app/oracle
[root@redhat1 ~]# chown -R oracle:oinstall /u01/app/oracle
[root@redhat1 ~]# chmod -R 775 /u01/app/oracle

 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@redhat1 ~]# mkdir -p /oracle_soft
[root@redhat1 ~]# chown -R oracle:oinstall /oracle_soft/
[root@redhat1 ~]# chmod -R 775 /oracle_soft/

 Copy the installation files to the above created directory.

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@redhat1 ~]# su - oracle
[oracle@redhat1 ~]$ 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 "xclok" 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@redhat1 ~]# 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@redhat1 ~]$ export DISPLAY=IP_REMOTE_MACHINE:0.0 

Installation of Oracle Database:

For RHEL 5:Modify "database/install/oraparam.ini" file and add "redhat-5" to "Certified Versions" section.

After the above activity, start Oracle Universal Installer (OUI) and install Oracle Database as follows:

[root@redhat1 ~]# su - oracle

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

[oracle@redhat1 ~]$cd /oracle_soft/
[oracle@redhat1 ~]$ ./runInstaller

For all the screenshots , please visit the link::: http://www.sensehaze.com  

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

export ORACLE_BASE=/u01/app/oracle
export ORACLE_HOME=/u01/app/oracle/product/10.2.0/db_1
export PATH=$PATH:$HOME/bin:$ORACLE_HOME/bin

[oracle@redhat1 ~]$ 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.

[oracle@redhat1 ~]$ . ~/.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.

This completes setting up of Oracle User Environment.

Listener Creation:

Open command prompt(terminal) & type “netca”

Database Creation:

Open command prompt and type "dbca"

Connect to the Database:

Open command prompt(terminal).

[oracle@redhat1 ~]$ export ORACLE_SID=mydb

[oracle@redhat1 ~]$ sqlplus / as sysdba

And you will be connected to the database.

For all the screenshots , please visit the link::: http://www.sensehaze.com

Deleting a Database by using DBCA

Overview:

This article is a comprehensive guide for Deleting a Database by using DBCA.

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

Objective of the Article:

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

---How to delete a database by using DBCA?

 for complete screenshot of the steps please visit the below link:: http://www.sensehaze.com/mydata/resources_section/installation/del_db/index.php

Installation and creation of Database:

For Installation and creation of Database, please visit the below mentioned link:

Installation and creation of Database on windows

Deleting a database using DBCA:

Open command prompt and type "dbca"

Select the option "Delete a Database" and Click on "Next.

Select the Database we want to delete (here -- mydb) and enter the credentials:
username ---- sys
Password --- our_sys_password
and Click on "Finish",  

Click on "yes" to confirm. 

This finishes database deletion procedure.

for complete screenshot of the steps please visit the below link:: http://www.sensehaze.com/mydata/resources_section/installation/del_db/index.php

Restore RMAN full backup to different server with different directory structure

Restore RMAN full backup to different server with same database name but different directory structure::


In this article we are going to learn, how to restore RMAN full backup to a different server with same database name but different directory structure.



Overview:

This article is a comprehensive guide for restoring RMAN full backup to a different server with same database name but different directory structure.

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 Techniques.

http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmrecov.htm#i1007814

Names used in this article:

Name	Value
Database Name	mydb
Backup Folder on Node1	c:\rman_bck
Backup Folder on Node2	c:\rman_bck
Database (Datafile/Controlfile/redolog) Folder on Node1	ORACLE_BASE\oradata\mydb
Database (Datafile/Controlfile/redolog) Folder on Node2	ORACLE_BASE\oradata\mydbtest

 Connect to the database:

Open command prompt and type the below mentioned:

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

Create initialization parameter file (pfile).

sql>create pfile from spfile ;

Take Full Backup of Database using RMAN:

Open command prompt and type the below mentioned:

cmd> rman target /

We can configure the backup location (if not configured earlier). For configuring backup location type the following command:

RMAN> configure channel device type disk format 'C:\rman_bck\mydb_%U' ;

For taking backup of the database, fire the below mentioned command:

RMAN> backup database plus archivelog ;

  For the screenshots of the procedure please visit the link::: http://www.sensehaze.com

Copy the required files to the other node:

Copy the below mentioned files to the other node:

--The backup pieces generated using RMAN.

--The initalization parameter file( created above).

--The password file( We can create it also on the other node).

Create database directory structure on other node:

Create "oradata/mydbtest" directory on the other node ( for storing controlfiles,datafiles,redo logfiles ). Also create Archive Destination Directory.

Create Service/instance on other node:

Note:This step needs to be performed only on Windows O/S.

Create a service( Here in my case my datbase name -- mydb ).For creating service use "oradim" utility. As mentioned below:

cmd> oradim -new -sid mydb -intpwd sys -startmode manual

 After creating the service, change its startmode to automatic. For doing so go to "windows services" and change its startmode to automatic.

Edit PFILE on the other node:

Edit the PFILE and change the location of control_files/audit_file_dest as per the new directory structure on the other node.

Start the database in nomount mode on other node:

Open command prompt and type the below mentioned commands:

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

Start database with PFILE:

sql> startup nomount pfile='full_path_of_pfile' ;

Invoke RMAN on other node:

Open command prompt and type the below mentioned:

cmd> rman target /

Restore Controlfile:

Restore the controlfile from the backup pieces as mentioned below:

RMAN> restore controlfile from 'full_path_control_file_bck_piece' ;

Mount the Database:

After restoring the controlfile from the backuppieces mount the database :

RMAN> alter database mount ;

Rename the Redologfiles:

After mounting the database, Rename the Redologfiles,so that they can be created in new locations when the database is opened with resetlogs option, For renaming the redologs open a new command prompt and connect to the database from that prompt, as mentioned below:

On the second Node (Node2)

SQL> alter database rename file 'redo_file_loc_first_node\redo01.log' to 'redo_file_loc_second_node\redo01.log';

SQL> alter database rename file 'redo_file_loc_first_node\redo02.log' to 'redo_file_loc_second_node\redo02.log';
.....................

SQL> alter database rename file 'redo_file_loc_first_node\redoN.log' to 'redo_file_loc_second_node\redoN.log';

  For the screenshots of the procedure please visit the link::: http://www.sensehaze.com

Get the Datafile Info of Node 1:

Connect to the database of Node 1 and query the "DBA_DATA_FILES" for datafiles info, as mentioned below:

SQL> select file_id , file_name from dba_data_files ;

Restore and Recover the Database:

After collecting datafile information of Node 1, Now restore the datafiles to new locations and recover ( On Node2 ), as mentioned below:

RMAN> run {
set newname for datafile 1 to 'datafile_loc_node2\system01.dbf' ;
set newname for datafile 2 to 'datafile_loc_node2\sysaux01.dbf' ;
set newname for datafile 3 to 'datafile_loc_node2\undotbs01.dbf' ;
set newname for datafile 4 to 'datafile_loc_node2\user01.dbf' ;
set newname for datafile 5 to 'datafile_loc_node2\tools.dbf' ;
................ //mention all the datafiles

restore database ;
switch datafile all ;
recover database ;
}

If it show error ("media recovery requesting unknown archived log") that means, it requires the new archivelogs, copy the new archivelogs from node1 to node2 and rerurn the above command "recover database". (We can ignore this error).

Open the Database with Resetlogs:

After that, open the database with resetlogs options. As mentioned below:

RMAN> alter database open resetlogs;

Connect to the database & create spfile:

After that, Connect to the database and create spfile. As mentioned below:

cmd> sqlplus / as sysdba
SQL> create spfile from pfile='pfile_location';

This finishes restoring RMAN full backup to a different server with same database name but different directory structure.

Restore RMAN full backup to different server with similar directory structure but changed backup location

Restore RMAN full backup to different server with same database name and similar directory structure but changed backup location:


In this article we are going to learn, how to restore RMAN full backup to a different server with same database name and similar directory structure but changed backup location.




 Overview:

This article is a comprehensive guide for restoring RMAN full backup to a different server with same database name and similar directory structure but changed backup location.

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 Techniques.

http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmrecov.htm#i1007814

Names used in this article:

Name	Value
Database Name	mydb
Backup Folder on Node1	c:\rman_bck
Backup Folder on Node2	c:\rman_bck1

Objective of the Article:

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

(1)How to take full backup of database using RMAN.

(2)How to restore RMAN full backup to different server with same database name and similar directory structure but changed backup location.

Connect to the database:

Open command prompt and type the below mentioned:

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

Create initialization parameter file (pfile).

sql>create pfile from spfile ;

 For all the screenshots visit the following link::: http://www.sensehaze.com

Take Full Backup of Database using RMAN:

Open command prompt and type the below mentioned:

cmd> rman target /

We can configure the backup location (if not configured earlier). For configuring backup location type the following command:

RMAN> configure channel device type disk format 'C:\rman_bck\mydb_%U' ;

For taking backup of the database, fire the below mentioned command:

RMAN> backup database plus archivelog ;

Copy the required files to the other node:

Copy the below mentioned files to the other node:

--The backup pieces generated using RMAN.

--The initalization parameter file( created above).

--The password file( We can create it also on the other node).

Create similar directory structure on other node:

Create "oradata/mydb" directory on the other node ( for storing controlfiles,datafiles,redo logfiles ). Also create Archive Destination Directory.

Create Service/instance on other node:

Note:This step needs to be performed only on Windows O/S.

Create a service( Here in my case my datbase name -- mydb ).For creating service use "oradim" utility. As mentioned below:

cmd> oradim -new -sid mydb -intpwd sys -startmode manual

Start the database in nomount mode on other node:

Open command prompt and type the below mentioned commands:

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

sql> startup nomount pfile='full_path_of_pfile' ;

 For all the screenshots visit the following link:::   http://www.sensehaze.com

 Invoke RMAN on other node:

Open command prompt and type the below mentioned:

cmd> rman target /

Restore Controlfile:

Restore the controlfile from the backup pieces as mentioned below:

RMAN> restore controlfile from 'full_path_control_file_bck_piece' ;

Mount the Database:

After restoring the controlfile from the backuppieces mount the database :

RMAN> alter database mount ;

Crosscheck Backup:

After mounting the database, crosscheck the bakcup, as mentioned below:

RMAN> crosscheck backup ;

Delete Expired Backups:

After running crosscheck, run "delete noprompt expired", as mentioned below:

Note : Be sure we really moved the backup files in the other location, otherwise after entering "delete noprompt expired", these files are lost and we will not able to execute a full restore.

RMAN> delete noprompt expired backup ;

Catalog the Backuppieces:

After running "delete noprompt expired", catalog all the backuppieces, as mentioned below:

RMAN> catalog backuppiece 'full_path_bck_piece_1' ;

RMAN> catalog backuppiece 'full_path_bck_piece_2' ;

RMAN> catalog backuppiece 'full_path_bck_piece_3' ;

RMAN> catalog backuppiece 'full_path_bck_piece_n' ;

Restore Database:

After catalogging all the backuppieces, run restore database command, as mentioned below:

RMAN> restore database ;

Recover Database:

After restoring the database, recover it as mentioned below:

RMAN> recover database ;

If it show error ("media recovery requesting unknown archived log") that means, it requires the new archivelogs, copy the new archivelogs from node1 to node2 and rerurn the above command "recover database". (We can ignore this error).

Open the Database with Resetlogs:

After that, open the database with resetlogs options. As mentioned below:

RMAN> alter database open resetlogs;

Connect to the database & create spfile:

After that, Connect to the database and create spfile. As mentioned below:

cmd> sqlplus / as sysdba
SQL> create spfile from pfile='pfile_location';

This finishes restoring RMAN full backup to a different server with same database name and similar directory structure but changed backup location.

 For all the screenshots visit the following link   :::  http://www.sensehaze.com

Restore RMAN full backup to different server with same database name and similar directory structure

In this article we are going to learn, how to restore RMAN full backup to a different server with same database name and similar directory structure.


Overview:

This article is a comprehensive guide for restoring RMAN full backup to a different server with same database name and similar directory structure.

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 Techniques.

http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmrecov.htm#i1007814

Names used in this article:

Name	Value
Database Name	mydb
Backup Folder	c:\rman_bck

Connect to the database:

Open command prompt and type the below mentioned:

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

Create initialization parameter file (pfile).

sql>create pfile from spfile ;

Take Full Backup of Database using RMAN:

Open command prompt and type the below mentioned:

cmd> rman target /

We can configure the backup location (if not configured earlier). For configuring backup location type the following command:

RMAN> configure channel device type disk format 'C:\rman_bck\mydb_%U' ;

For taking backup of the database, fire the below mentioned command:

RMAN> backup database plus archivelog ;

The above activity will take some time, depending upon the database size.

For the complete screenshot of the activities plesae visit the followong link::: http://www.sensehaze.com/

Copy the required files to the other node:

Note:Make sure all rman backup files from Node1 are in the same location(s) in the new server(Node2) as the source server(Node1) (same path names and directory structure ).

Copy the below mentioned files to the other node:

--The backup pieces generated using RMAN.

--The insitalization parameter file( created above).

--The password file( We can create it also on the other node).

Create similar directory structure on other node:

Create "oradata/mydb" directory on the other node ( for storing controlfiles,datafiles,redo logfiles ). Also create Archive Destination Directory.

 For the complete screenshot of the activities plesae visit the followong link::: http://www.sensehaze.com/

Create Service/instance on other node:

Note:This step needs to be performed only on Windows O/S.

Create a service( Here in my case my datbase name -- mydb ).For creating service use "oradim" utility. As mentioned below:

cmd> oradim -new -sid mydb -intpwd sys -startmode manual

After creating the service, change its startmode to automatic. For doing so go to "windows services" and change its properties.  

Start the database in nomount mode on other node:

Open command prompt and type the below mentioned:

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

sql> startup nomount pfile='full_path_of_pfile' ;

 For the complete screenshot of the activities plesae visit the followong link::: http://www.sensehaze.com/

Invoke Rman on other node:

Open command prompt and type the below mentioned:

cmd> rman target /

Restore the controlfile from the backup pieces as mentioned below:

RMAN> restore controlfile from 'full_path_control_file_bck_piece' ;

After restoring the controlfile from the backup pieces mount the database :

RMAN> alter database mount ;

After mounting the database, restore it as mentioned below:

RMAN> restore database ;

After restoring the database, recover it as mentioned below:

RMAN> recover database ;

If it show error ("media recovery requesting unknown archived log") that means, it requires the new archivelogs ,copy the new archivelogs from node1 to node2.

We can ignore the error.
For not encountering this error we can use "until" option with the above command.

After that, open the database with resetlogs options. As mentioned below:

RMAN> alter database open resetlogs;

After that, Connect to the database and create spfile. As mentioned below:

cmd> sqlplus / as sysdba
SQL> create spfile from pfile='pfile_location';

For the complete screenshot of the activities plesae visit the followong link::: http://www.sensehaze.com/