Oracle Clusterware and
Oracle Real Application Clusters Pre-Installation Procedures
Chapter 2,"Pre-Installation Tasks"
Chapter 3,"Configuring Oracle Clusterware and Oracle Database Storage"
Configuring Oracle Clusterware and Oracle Databaase Storage
Tasks :
1,Reviewing Storage Options for Oracle Clusterware,Database,and Recovery Files
2,Configuring Storage for Oracle Clusterware Files on a Supported Shared Files System
3,Configuring Storage for Oracle Clusterware Files On Raw Devices
4,Choosing a storage Options for Oracle Database Files
5,Configuring Disks for Automatic Storage Management
6,Configuring Database File Storage on Raw Devices
Overview of Oracle Clusterware Storage Options:
There are two ways of storing Oracle Clusterware files.
A supported shared File System:
OCFS,The cluster file system Oracle provides for the Linux community.
NFS(Network File System),A file-level protocol that enables access and sharing of files.
Raw Partitions:Raw partitions are disk partitions that are not mounted and written to
using the Linux file system,but instead are accessed directly by the
application.
Overview of Oracle Database and Recovery File Options:
There are three ways of storing Oracle Database and recovery files:
ASM:ASM is an integrated,high-performance database file system and disk manager for Oracle files.
A supported shared file system:
OCFS
NFS
Raw partitions: database files only,A raw partition is required for each database file.
Oracle Clusterware files:
Oracle Cluster Registry(OCR)
a mirrored OCR file(optional)
the Oracle Clusterware voting disk
addtional voting disk files(optional)
Oracle Database files:
data files
control files
redo log files
the server parameter file
the password file
Oracle Database recovery files:
OCR and Voting Disk 和 Oracle Clusterware 之间是什么关系？？？？？
===========================================================================================
File Type Supported
-----------------------------------------------------
OCR and Oracle
Storage Option Voting Disk Clusterware Database Recovery
-------------------------------------------------------------------------------------------
ASM NO NO YES YES
-------------------------------------------------------------------------------------------
OCFS YES NO YES YES
-------------------------------------------------------------------------------------------
Local storage NO YES NO NO
-------------------------------------------------------------------------------------------
NFS file system YES YES YES YES
Note:Requires a certified NAS device
-------------------------------------------------------------------------------------------
Shared raw partitions YES NO YES NO
-------------------------------------------------------------------------------------------
Oracle recommends that you choose ASM as the storage option for database and recovery files.
You cannot use ASM to store Oracle Clusterware files,because these files must be accessible before
any Oracle instance starts.
If you do not have a storage option that provides external file redundance,then you must configure
at least three voting disk areas to provide voting disk redundancy.
Binding the Partitions to Raw Devices:
# /usr/bin/raw -qa
/dev/raw/raw1 /dev/sdb1
Specify an unused raw device for each partition.
#chown root:oinstall /dev/raw/rawn
#chmod 640 /dev/raw/rawn
# /sbin/service rawdevices restart
Configuring Disks for ASM
Identifying Storage Requirements for ASM
Using an Existing ASM Disk Group
Configuring Disk for ASM with ASMLIB
Configuring Database File Storage on ASM and Raw Devices
You can run ASM using ASMLIB,or run ASM using raw partitions.
If you choose to enable automated backups and you do not have a shared file system available,
then you must choose ASM for recovery file storage.
=============================================================================================
Redundancy Minimum Number Database Recovery Both File
Level of Disks Files files Types
---------------------------------------------------------------------------------------------
External 1 1.15GB 2.3GB 3.45GB
---------------------------------------------------------------------------------------------
Normal 2 2.3GB 4.6GB 6.9GB
---------------------------------------------------------------------------------------------
High 3 3.45GB 6.9GB 10.35GB
---------------------------------------------------------------------------------------------
Additional disk space requirements:(MB)
15 + (2*number_of_disks)+(126*number_of_Automatic_Storage_Management_instances)
eg:
15 + (2*3) + (126*4) = 525 (MB)
SELECT NAME,TYPE,TOTAL_MB,FREE_MB FROM V$ASM_DISKGROUP;
ASMLIB: Automatic Storage Management Library driver
ASMLIB simplifies the configuration and management of the disk devices that you want to use
with ASM.
A disk that is configured for use with ASM is known as a candidate disk.
For improved performance and easier administration,Oracle recommends that you use the ASMLIB
driver instead of raw devices to configure ASM disks.
Configuring Database File Storge on Raw Devices:
Database File Restrictions for Logical Volume Manager (LVM) on Linux
Identifying Required Raw Partitions for Database Files
Creating Required Raw Partitions for Database Files on IDE,SCSI,or RAID Devides
Binding Partitions to Raw Devides for Database Files
Create the Database Configuration Assistant Raw Devices Mapping File
Identifying Required Raw Partitions for Database Files:
Table 3-3 lists the number and size of the raw partitions that you must configure for database files.
Table 3-3 Raw Partitions Required for Database Files on Linux
============================================================================================
Partition Size
Number (MB) Purpose
--------------------------------------------------------------------------------------------
1 500 SYSTEM tablespace
--------------------------------------------------------------------------------------------
1 300+(Number of SYSAUX tablespace
instances*250)
--------------------------------------------------------------------------------------------
1 500 UNDOTBSn tablespace(One tablespace for
each instance)
--------------------------------------------------------------------------------------------
1 250 TEMP tablespace
--------------------------------------------------------------------------------------------
1 160 EXAMPLE tablespace
--------------------------------------------------------------------------------------------
1 120 USERS tablespace
--------------------------------------------------------------------------------------------
2*number of 120 Two online redo log files for each instance
instances
--------------------------------------------------------------------------------------------
2 110 First and second control files
--------------------------------------------------------------------------------------------
1 5 Server parameter file(SPFILE)
--------------------------------------------------------------------------------------------
1 5 Password file
--------------------------------------------------------------------------------------------
If you prefer to use manual undo management,instead of automatic undo management,then,instead
of the UNDOTBSn raw devices ,you must create a single rollback segment tablespace (RBS)
raw device that is at least 500 MB in size.
********Binding Partitions to Raw Devices for Database Files*******
After you have created the required partitions for database files,you must bind the
partitions to raw devices on every node.
Create the Database Configuration Assistant Raw Devices Mapping File:
To allow Database Configuration Assistant to identify the appropriate raw device for each
database file ,you must create a raw device mapping file,as follows:
1,set the ORACLE_BASE
2,Create a database file subdirectory under the Oracle base directory and set the
appropriate owner,group,and permissions on it:
# mkdir -p $ORACLE_BASE/oradata/dbname
# chown -R oracle:oinstall $ORACLE_BASE/oradata
# chmod -R 775 $ORACLE_BASE/oradata
3,Change directory to the $ORACLE_BASE/oradata/dbname directory.
4,Editor the dbname_raw.conf file.
eg:
system=/dev/raw/raw1
sysaux=/dev/raw/raw2
example=/dev/raw/raw3
users=/dev/raw/raw4
temp=/dev/raw/raw5
undotbs1=/dev/raw/raw6
undotbs2=/dev/raw/raw7
redo1_1=/dev/raw/raw8
redo1_2=/dev/raw/raw9
redo2_1=/dev/raw/raw10
red02_2=/dev/raw/raw11
control1=/dev/raw/raw12
control2=/dev/raw/raw13
spfile=/dev/raw/raw14
pwdfile=/dev/raw/raw15
5,Save the file,and note the file name that you specified.
6,If you are using raw devices for database storage,then set the DBCA_RAW_CONFIG environment
variable to specify the full path to the raw device mapping file:
Bourne,Bash,or Korn shell:
$ DBCA_RAW_CONFIG=$ORACLE_BASE/oradata/dbname/dbname_raw.conf
$ export DBCA_RAW_CONFIG
C shell:
$ setenv DBCA_RAW_CONFIG=$ORACLE_BASE/oradata/dbname/dbname_raw.conf
