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-04062: timestamp of procedure has been changed

Problem Description In the database I have created one procedure named a as below. create or replace procedure a(a number) as begin insert into t1 values(1); commit; end; / Now after creating database link using remote database machine whenever I access this procedure "A" it executes successfully and I get value "1" in table t1. Like below in example where orastdby_m is the database link, shaik is the schema name and value 1 is the argument value though argument value is not used in the procedure. SQL> exec shaik.a@orastdby_m(1); PL/SQL procedure successfully completed. Now in the source database machine I changed the procedure as below. Though you can change anything like any literal; adding space or remove space. I changed value to be inserted from 1 to 2. create or replace procedure a(a number) as begin insert into t1 values(2); commit; end; / Now in the other database whenever I execute the procedure using database link it throws error ORA-04062. But subseq...
Read more

ORA-00939: too many arguments -when case arguments exceed 255

Problem Description In all Oracle 10.1g and oracle 10.2.0.1, 10.2.0.2, 10.2.0.3 whenever there is more than 255 arguments inside CASE statements then following error is returned. ORA-00939: too many arguments for function But surprisingly on Oracle 9.2 database the same code does not return any error. Cause of the Problem As we see the same code return error in 10g but it is well on 9.2. In fact this is problem of oracle 9.2 that it does not return any error. It should return error if there is more than 255 arguments inside CASE statements. In oracle 9.2 this is bug number 2909927 and this bug is fixed in oracle 10.1 and 10.2. That's why in 10.2 and 10.1 error returns if arguments exceed 255. Up to Oracle 10.2.0.3 and earlier version, the arguments of CASE statement is limit to 255 and it does not support exceed over 255 and hence error return if it exceed. However in Oracle 10.2.0.4 and later the arguments limit of CASE statement has increased to 32767. Solution of the Problem Opt...
Read more

ORA-31655: no data or metadata objects selected for job

Problem Description You are going to do data pump export operation in order to export objects based on filtering via EXCLUDE or INCLUDE parameter of expdp. In this example you wanted tables 'ACCOUNT_GROUP','ADDRESS','AREA_GROUP' and all the tables starting with word CV(like 'CV', 'CV_EXPERIENCE', 'CV_EDUCATION' etc) Your parameter file is like below. userid=smilebd/a directory=d dumpfile=b.dmp include =TABLE:"IN('ACCOUNT_GROUP','ADDRESS','AREA_GROUP')" include =TABLE:"LIKE 'CV%' " And you invoke expdp as expdp parfile=d:\parfile.txt from command line. But it fails with below message on my windows PC. C:\>expdp parfile=d:\parfile.txt Export: Release 10.1.0.4.2 - Production on Thursday, 29 January, 2009 14:53 Copyright (c) 2003, Oracle. All rights reserved. Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Produc tion With the Partitioning, OLAP and Data Mining ...
Read more