Home » RDBMS Server » Server Administration » Is ASM a solution to a large recovery area (11.2.0.1 SE RH 7.1)
Is ASM a solution to a large recovery area [message #645023] Mon, 23 November 2015 21:20 Go to previous message
juniordbanewbie
Messages: 250
Registered: April 2014
Senior Member
Dear all,

currently I have a system in which all the files are scattered across different filesystem/partitions,
from the OS, the mount point is as follow
[root@chicago-db ~]# df -h
Filesystem                         Size  Used Avail Use% Mounted on
/dev/mapper/rhel_chicago--db-root   22G  3.3G   19G  16% /
devtmpfs                            16G     0   16G   0% /dev
tmpfs                               16G     0   16G   0% /dev/shm
tmpfs                               16G   25M   16G   1% /run
tmpfs                               16G     0   16G   0% /sys/fs/cgroup
/dev/sdd                           355G  301G   36G  90% /u01
/dev/sdg                           355G  161G  176G  48% /u05
/dev/sde                           355G  303G   34G  91% /u02
/dev/sdb                           355G  303G   34G  90% /u04
/dev/sdf                           355G  309G   28G  92% /u03
/dev/sdh                           837G  483G  312G  61% /import2
/dev/sdc                          1008G   89M  957G   1% /import
/dev/sda1                          497M  120M  378M  24% /boot



from the db, the breakdown of database file size is as follow:

SYS@camden>SELECT substr(file_name,1,4), sum(bytes)/1024/1024/1024 size_in_g FROM dba_data_files GROUP BY ROLLUP(substr(file_name,1,4)) ORDER BY sum(bytes)/1024/1024/1024;

SUBS  SIZE_IN_G                                                                 
---- ----------                                                                 
/u05 40.2929688                                                                 
/u01 249.622993                                                                 
/u04 278.001892                                                                 
/u02 278.322205                                                                 
/u03 283.998962                                                                 
     1130.23902



conclusion recovery area for database should be about at least twice the size of current database file size which means recovery area should be about 2260 GB

if it is not possible to have a filesystem of 2260 GB, I guess the only solution is to have ASM
from http://docs.oracle.com/cd/E11882_01/server.112/e18951/asmcon.htm#OSTMG94059


Quote:

If you omit the failure group specification, then Oracle ASM automatically places each disk into its own failure group, except for disk groups containing disks on Oracle Exadata cells.

Normal redundancy disk groups require at least two failure groups. High redundancy disk groups require at least three failure groups. Disk groups with external redundancy do not use failure groups.


My interpretation of the above is as follow:

normal redundancy disk group can have 3 or even more disks because it state at least. so for external redundancy we can have as many disk as possible right?

So all I need to do is as follow

if each partition can only be 355G, about 7 disk 2260/355 are required, then I need to partition and configure the Disk Devices to Use the Oracle Automatic Storage Management Library Driver according to http://docs.oracle.com/cd/E11882_01/install.112/e47689/oraclerestart.htm#CHDFEDHB

install Oracle Grid Infrastructure for a Standalone Server 11.2.0.4 (Binaries for ASM) from p13390677_112040_Linux-x86-64_3of7.zip

Create the Diskgroup FRA


Migrate the existing flash recovery to FRA

Right?

Is there any other issues we have?

thanks and many thanks

[Updated on: Mon, 23 November 2015 22:11]

Report message to a moderator

 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: How we can check all DB Link connections.
Next Topic: Startup a remote database fails with invalid username
Goto Forum:
  


Current Time: Thu Apr 25 03:35:14 CDT 2024