Grid infra 11gR2 installation help required

Question

sir
i have some problem.do not know how to solve it?
i need to install grid infrastructure advanced installation.
scenario and question:
i have a raw(74GB) device under ASM on 192.168.1.13.but how to put it into the cluster its not under OCFS2,what to do(under OEL5.4)?
and in another machine(with ip 192.168.1.30) i want to load 11gR2 grid as well as 11gR2 db but how to qualify it to the cluster-aware ASM-ocfs2 disk??i had a a partition /dev/sda3 as LVM group with two mounted partion /ASM1 and /ASM2 as empty ext3 in this machine.what to do?
regards

Answer 1

I guess this will help-- http://blog.ronnyegner-consulting.de/2009/09/14/oracle-11g-release-2-install-guide-%e2%80%93-grid-infrastructure-installation/
-- http://husnusensoy.wordpress.com/2009/10/30/how-to-install-oracle-11g-release-2-on-oel-5-4-on-virtualbox-installing-grid-infrastructure/
To identify the storage requirements for using Automatic Storage Management, you must determine the number of devices and the amount of free disk space that you require. To complete this task:
1.     Determine whether you want to use Automatic Storage Management for Oracle Database files, recovery files, or both.
Note:
You do not have to use the same storage mechanism for , Oracle Database files, and recovery files. You can use a file system for one file type and Automatic Storage Management for the other.
If you choose to enable automated backups and you do not have a shared file system available, then you must choose Automatic Storage Management for recovery file storage.
If you plan to enable automated backups during the installation, then you can choose Automatic Storage Management as the storage mechanism for recovery files by specifying an Automatic Storage Management disk group for the fast recovery area. Depending on how you choose to create a database during the installation, you have the following options:
o     If you select an installation method that runs Oracle Automatic Storage Management Configuration Assistant in interactive mode, then you can decide whether you want to use the same Automatic Storage Management disk group for database files and recovery files, or you can choose to use different disk groups for each file type. Ideally, you should create separate Automatic Storage Management disk groups for data files and for recovery files.
The same choice is available to you if you use Oracle Database Configuration Assistant after the installation to create a database.
o     If you select an installation type that runs Oracle Automatic Storage Management Configuration Assistant in silent or response file mode, then you must use the same Automatic Storage Management disk group for data files and recovery files.
2.     Choose the Automatic Storage Management redundancy level that you want to use for each Automatic Storage Management disk group that you create.
The redundancy level that you choose for the Automatic Storage Management disk group determines how Automatic Storage Management mirrors files in the disk group and determines the number of disks and amount of disk space that you require, as follows:
o     External redundancy
This option does not allow Automatic Storage Management to mirror the contents of the disk group. Oracle recommends that you select this redundancy level either when the disk group contains devices, such as RAID devices, that provide their own data protection or when the database does not require an uninterrupted access to data.
o     Normal redundancy
To optimize performance and reliability in a normal redundancy disk group, Automatic Storage Management uses two-way mirroring for data files and three-way mirroring for control files, by default. In addition, you can choose the mirroring characteristics for individual files in a disk group. Alternatively, you can use two-way mirroring or no mirroring.
A normal redundancy disk group requires a minimum of two failure groups (or two disk devices) if you are using two-way mirroring. The effective disk space in a normal redundancy disk group is half the sum of the disk space in all of its devices.
For most installations, Oracle recommends that you use normal redundancy disk groups.
o     High redundancy
The contents of the disk group are three-way mirrored by default. To create a disk group with high redundancy, you must specify at least three failure groups (a minimum of 3 devices).
Although high-redundancy disk groups provide a high level of data protection, you must consider the higher cost of additional storage devices before deciding to use this redundancy level.
3.     Determine the total amount of disk space that you require for the database files and recovery files.
If an Automatic Storage Management instance is already running on the system, then you can use an existing disk group to meet these storage requirements. If necessary, you can add disks to an existing disk group during the installation.
Use the following table to determine the minimum number of disks and the minimum disk space requirements for the installation:
Redundancy Level     Minimum Number of Disks     Data Files     Recovery Files     Both File Types
External     1     1.8 GB     3.6 GB     5.4 GB
Normal     2     3.6 GB     7.2 GB     10.8 GB
High     3     5.4 GB     10.8 GB     16.2 GB
4.     Optionally, identify failure groups for the Automatic Storage Management disk group devices.
If you intend to use a normal or high redundancy disk group, then you can further protect the database against hardware failure by associating a set of disk devices in a custom failure group. By default, each device comprises its failure group. However, if two disk devices in a normal redundancy disk group are attached to the same SCSI controller, then the disk group becomes unavailable if the controller fails. The controller in this example is a single point of failure.
To avoid failures of this type, you can use two SCSI controllers, each with two disks, and define a failure group for the disks attached to each controller. This configuration would enable the disk group to tolerate the failure of one SCSI controller.
Note:
If you define custom failure groups, then you must specify a minimum of two failure groups for normal redundancy disk groups and three failure groups for high redundancy disk groups.
5.     If you are sure that a suitable disk group does not exist on the system, then install or identify appropriate disk devices to add to a new disk group. Apply the following guidelines when identifying appropriate disk devices:
o     The disk devices must be owned by the user performing the grid installation.
o     All the devices in an Automatic Storage Management disk group should be the same size and have the same performance characteristics.
o     Do not specify multiple partitions on a single physical disk as a disk group device. Automatic Storage Management expects each disk group device to be on a separate physical disk.
o     Oracle does not recommend the use of a logical volume as a device in Automatic Storage Management because the logical volume is capable of hiding the physical disk architecture which prevents Automatic Storage Management from optimizing I/O across physical devices.