Settting maximum Size of Backup Set or Backup Piece

Some older operating system limits the size of individual files. In that case if your datafile size is 10G stored in raw device and your operating system supports only 4GB files on the file system then it is not possible to take backup of the image copy to the file system.

The CONFIGURE MAXSETSIZE command limits the size of backup sets created on file system on a specific channel. If I use 100M then maximum backup set size will be 100M per channel.

You can also control the size of a backup set piece or the entire backup itself with the MAXPIECESIZE parameter.

If your database size is 330M and you set MAXPIECESIZE to 100M then it will be divided in 4 backup pieces containing 100M, 100M, 100M and 30M.

An example:
--------------
RMAN> run{
2> ALLOcate CHANNEL a DEVICE TYPE DISK MAXPIECESIZE 100M;
3> backup database;
4> }

released channel: ORA_DISK_1
allocated channel: a
channel a: sid=155 devtype=DISK

Starting backup at 11-MAY-08
channel a: starting full datafile backupset
channel a: specifying datafile(s) in backupset
input datafile fno=00001 name=/oradata2/data1/dbase/system01.dbf
input datafile fno=00003 name=/oradata2/data1/dbase/sysaux01.dbf
input datafile fno=00002 name=/oradata2/data1/dbase/undotbs01.dbf
input datafile fno=00004 name=/oradata2/data1/dbase/users01.dbf
input datafile fno=00005 name=/oradata2/data.dbf
input datafile fno=00006 name=/oradata2/data1/data02.dbf
input datafile fno=00007 name=/oradata2/6.dbf
channel a: starting piece 1 at 11-MAY-08
channel a: finished piece 1 at 11-MAY-08
piece handle=/oradata2/flash_recovery_area/DBASE/backupset/2008_05_11/o1_mf_nnndf_TAG20080511T051131_42fg23tw_.bkp tag=TAG20080511T051131 comment=NONE
channel a: starting piece 2 at 11-MAY-08
channel a: finished piece 2 at 11-MAY-08
piece handle=/oradata2/flash_recovery_area/DBASE/backupset/2008_05_11/o1_mf_nnndf_TAG20080511T051131_42fg2wvy_.bkp tag=TAG20080511T051131 comment=NONE
channel a: starting piece 3 at 11-MAY-08
channel a: finished piece 3 at 11-MAY-08
piece handle=/oradata2/flash_recovery_area/DBASE/backupset/2008_05_11/o1_mf_nnndf_TAG20080511T051131_42fg3cx4_.bkp tag=TAG20080511T051131 comment=NONE
channel a: starting piece 4 at 11-MAY-08
channel a: finished piece 4 at 11-MAY-08
piece handle=/oradata2/flash_recovery_area/DBASE/backupset/2008_05_11/o1_mf_nnndf_TAG20080511T051131_42fg3tyc_.bkp tag=TAG20080511T051131 comment=NONE
channel a: starting piece 5 at 11-MAY-08
channel a: finished piece 5 at 11-MAY-08
piece handle=/oradata2/flash_recovery_area/DBASE/backupset/2008_05_11/o1_mf_nnndf_TAG20080511T051131_42fg4b0f_.bkp tag=TAG20080511T051131 comment=NONE
channel a: starting piece 6 at 11-MAY-08
channel a: finished piece 6 at 11-MAY-08
piece handle=/oradata2/flash_recovery_area/DBASE/backupset/2008_05_11/o1_mf_nnndf_TAG20080511T051131_42fg4s1m_.bkp tag=TAG20080511T051131 comment=NONE
channel a: backup set complete, elapsed time: 00:01:33
channel a: starting full datafile backupset
channel a: specifying datafile(s) in backupset
including current control file in backupset
including current SPFILE in backupset
channel a: starting piece 1 at 11-MAY-08
channel a: finished piece 1 at 11-MAY-08
piece handle=/oradata2/flash_recovery_area/DBASE/backupset/2008_05_11/o1_mf_ncsnf_TAG20080511T051131_42fg50l4_.bkp tag=TAG20080511T051131 comment=NONE
channel a: backup set complete, elapsed time: 00:00:01
Finished backup at 11-MAY-08
released channel: a


SQL> !du -sh /oradata2/flash_recovery_area/DBASE/backupset/2008_05_11/o1_mf_nnndf_TAG20080511T051131_42fg23tw_.bkp
100M /oradata2/flash_recovery_area/DBASE/backupset/2008_05_11/o1_mf_nnndf_TAG20080511T051131_42fg23tw_.bkp

SQL> !du -sh /oradata2/flash_recovery_area/DBASE/backupset/2008_05_11/o1_mf_nnndf_TAG20080511T051131_42fg2wvy_.bkp
100M /oradata2/flash_recovery_area/DBASE/backupset/2008_05_11/o1_mf_nnndf_TAG20080511T051131_42fg2wvy_.bkp

SQL> !du -sh /oradata2/flash_recovery_area/DBASE/backupset/2008_05_11/o1_mf_nnndf_TAG20080511T051131_42fg3cx4_.bkp
100M /oradata2/flash_recovery_area/DBASE/backupset/2008_05_11/o1_mf_nnndf_TAG20080511T051131_42fg3cx4_.bkp

Comments

Post a Comment

Popular posts from this blog

ORA-00923: FROM keyword not found where expected

Problem Symptom While performing a simple select statement it fails with error ORA-00923: FROM keyword not found where expected like below. SQL> select 48*1024*1024*1024 decimal from dual; select 48*1024*1024*1024 decimal from dual * ERROR at line 1: ORA-00923: FROM keyword not found where expected Cause of the problem The ORA-00923 can be caused by two different reasons. 1)Oracle itself expect FROM keyword in the position but it could not find any. Like below, SQL> select 48*1024 om dual; select 48*1024 om dual * ERROR at line 1: ORA-00923: FROM keyword not found where expected As no from keyword found so error arises. Oracle expected from in place of keyword dual. 2)The secong cause can sometimes mislead you. Like in case of SQL> select 48*1024*1024*1024 decimal from dual; select 48*1024*1024*1024 decimal from dual * ERROR at line 1: ORA-00923: FROM keyword not found where exp
Read more

How to make partitioning in Oracle more Quickly

As the table size grows and full table scans happens more frequently then there is no alternative than partitioning in oracle. Partition greatly enhance performance of a query. I will start my partitioning system simply with an example. In my database the following query took 30~35 seconds to complete. After partitioning the performance increased amazingly and it then took only 1 second. My query was, SELECT DISTINCT fs.type, fs.id , fs.pid, fs.cid , fs.cr_id, fs.created_date FROM summary fs where fs.id in (select fa.id from forms fa where fa.sar in (select la.sar from login la where la.login_id=1 and fa.created_date BETWEEN to_date('1-MAY-2008') AND to_date('21-SEP-2008') and fs.created_date BETWEEN to_date('1-MAY-2008') AND to_date('21-SEP-2008') ) )and mode=0; After seeing above query I decide to make range partition on column created_date both in summary table and forms table. Below is the list of procedur
Read more

Copy files between Unix and Windows with rcp

There are many third party tools by which you can copy files between windows and unix machine. Some common tools are winscp, SSHSecureShellClient etc. Instead of using any third party tool, you can use original unix and windows built-in tool to do the task. The RCP (Remote CoPy) is a standard UNIX tool and a Microsoft Windows 2000 tool that copies files/folder to and from computer running the RCP service. Before you can use the RCP tool from a Windows-based computer you must do something in your UNIX computer. you must turn on the RCP service and update the security files to allow the Windows-based computer to connect to your unix machine over this service. The following steps will help you. Step 01: Turn on RCP service on UNIX Host Turn on the RCP service on unix machine by using inetd: 1. Log on as root. 2. Edit the file /etc/Inetd.conf. 3. Uncomment the lines that start with shell and that start with exec. 4. Save the file. 5. Use ps -ef |grep inetd and determine inetd service p
Read more