cheers I saw that, but we seem to have the opposite issue. The backupset created is *larger *than the setsize specified. (and we're on 9.2.0.7). On Tue, Mar 29, 2011 at 5:07 PM, Michael Dinh <mdinh@xxxxxxxxx> wrote: > BUG * **[ID 265249.1]*? > > > > *Applies To* > > Oracle Server - Enterprise Edition - Version: 9.0.1.4 to 9.2.0.4 > This problem can occur on any platform. > > *Symptoms*** > > > RMAN-03013: command type: backup > RMAN-06183: datafile or datafilecopy larger than SETSIZE > > *Cause*** > > Bug:3242806 RMAN-06183: DATAFILE LARGER THAN SETSIZE: ALTHOUGH MAXSETSIZE > IS > > DATAFILE SIZE > > *Fix*** > > This is Bug 3242806 closed as duplicate of hidden bug 3248809 > > WORKAROUND: > ----------- > 1) Use MAXPIECESIZE instead if MAXSETSIZE > 2) Use FILESPERSET > > 3) Calcualte MAXSETSIZE as follows : > > The problem is with somewere in comparision of MAXSETSIZE specification > (with number of blocks). > > The workaround is to specify "MAXSETSIZE" of higher value. > For example, if you want maximum backupset size as 10GB, then specify > it as > > '10GB * /1024'. > > If your db_block_size is 8k, then for a 10GB backupset > size, MAXSETSIZE must be configured to 80GB as a workaround. This will > create a maximum backupset size of 10GB. > > [image: Show Related Information] *Related* > > > > > > Michael Dinh > > > > NOTICE OF CONFIDENTIALITY - This material is intended for the use of the > individual or entity to which it is addressed, and may contain information > that is privileged, confidential and exempt from disclosure under applicable > laws. BE FURTHER ADVISED THAT THIS EMAIL MAY CONTAIN PROTECTED HEALTH > INFORMATION (PHI). BY ACCEPTING THIS MESSAGE, YOU ACKNOWLEDGE THE FOREGOING, > AND AGREE AS FOLLOWS: YOU AGREE TO NOT DISCLOSE TO ANY THIRD PARTY ANY PHI > CONTAINED HEREIN, EXCEPT AS EXPRESSLY PERMITTED AND ONLY TO THE EXTENT > NECESSARY TO PERFORM YOUR OBLIGATIONS RELATING TO THE RECEIPT OF THIS > MESSAGE. If the reader of this email (and attachments) is not the intended > recipient, you are hereby notified that any dissemination, distribution or > copying of this communication is strictly prohibited. Please notify the > sender of the error and delete the e-mail you received. Thank you. > > *From:* oracle-l-bounce@xxxxxxxxxxxxx [mailto: > oracle-l-bounce@xxxxxxxxxxxxx] *On Behalf Of *Niall Litchfield > *Sent:* Tuesday, March 29, 2011 8:54 AM > *To:* ORACLE-L > *Subject:* MAXSETSIZE > > > > Asked internally here. I don't have an answer. 9.2.0.7 db being backed up > from the standby. > > > > Does anyone know why the rman command below manages to generate a 270gb > backupset. > > > > backup maxsetsize=50G database TAG='TAG1' plus archivelog TAG='TAG2'; > > > > -- > Niall Litchfield > Oracle DBA > http://www.orawin.info > -- Niall Litchfield Oracle DBA http://www.orawin.info