Databases Reference
In-Depth Information
/dev/sda1 124M 34M 85M 29% /boot
/dev/mapper/VGExaDb-LVDbOra1
99G 69G 25G 74% /u01
tmpfs 81G 224M 81G 1% /dev/shm
x.y.z.38:/dwbackup1
25T 22T 2.8T 89% /dwbackup1
The IP address has been masked to protect the innocent.
2.
Make this file system owned by oradb (or the user who owns the Oracle software):
# chown oradb:dba /dwbackup1
3.
In step 9, use this syntax instead:
SQL> alter system set db_recovery_file_dest_size = 5520G;
System altered.
SQL> alter system set db_recovery_file_dest = '/dwbackup1';
System altered.
4.
Follow steps 10 and beyond.
Option C: Using an External NFS Mount Point, but Not as an FRA
This solution is exactly the same as the previous option, except that there is no FRA. So do not execute step 9. Since
there is no FRA, you have to let RMAN know the location where the backup should be placed, as shown below:
RMAN> run {
2> allocate channel c1 type disk format '/dwbackup1/%u.rmb';
3> allocate channel c2 type disk format '/dwbackup1/%u.rmb';
4> allocate channel c3 type disk format '/dwbackup1/%u.rmb';
5> allocate channel c4 type disk format '/dwbackup1/%u.rmb';
6> allocate channel c5 type disk format '/dwbackup1/%u.rmb';
7> allocate channel c6 type disk format '/dwbackup1/%u.rmb';
8> allocate channel c7 type disk format '/dwbackup1/%u.rmb';
9> allocate channel c8 type disk format '/dwbackup1/%u.rmb';
10> backup database;
11> }
Setting RMAN Buffer Size
Problem
The default size and number of input and output buffers are usually adequate for regular Oracle databases, but
they may be inadequate for Exadata due to the higher performance numbers. You need to set up the correct buffer
parameters or at least confirm that their values are set.
