Database Size versus Backup Size

Is there a formuly I can use, to calculate the amount of backup space I will need ?
We have a backup script, for backing up to disk - I copy and paste the main body of the script below. My would like to be able to estimate how much backup space we need, as the database grows.
connect target
run
change archivelog all crosscheck;
backup database
include current controlfile
format '/backup/rman/oraadmin/DBF_%d_%p_%s.RMan'
filesperset 4
tag = 'Full_DB_Backup';
sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
run
# Backup Archived Logs
backup archivelog all
format '/backup/rman/oraadmin/ARC_%d_%p_%s.RMan'
filesperset 16
delete input;
run
#* Copy Current Control File to Backup Location
copy current controlfile to '/backup/rman/oraadmin/ControlFile.Ctl';
}

use this script -
column dummy noprint
column pct_used format 999.9 heading "%|Used"
column name format a16 heading "Tablespace Name"
column Kbytes format 999,999,999 heading "KBytes"
column used format 999,999,999 heading "Used"
column free format 999,999,999 heading "Free"
column largest format 999,999,999 heading "Largest"
break on report
compute sum of kbytes on report
compute sum of free on report
compute sum of used on report
select nvl(b.tablespace_name,
nvl(a.tablespace_name,'UNKOWN')) name,
kbytes_alloc kbytes,
kbytes_alloc-nvl(kbytes_free,0) used,
nvl(kbytes_free,0) free,
((kbytes_alloc-nvl(kbytes_free,0))/
kbytes_alloc)*100 pct_used,
nvl(largest,0) largest
from ( select sum(bytes)/1024 Kbytes_free,
max(bytes)/1024 largest,
tablespace_name
from sys.dba_free_space
group by tablespace_name ) a,
( select sum(bytes)/1024 Kbytes_alloc,
tablespace_name
from sys.dba_data_files
group by tablespace_name
UNION
select sum(bytes)/1024 kbytes_alloc, tablespace_name
from sys.dba_temp_files
group by tablespace_name )b
where a.tablespace_name (+) = b.tablespace_name;
Message was edited by:
jittu13

Similar Messages

  • Difference in DB size and backup size

    Hi,
    I work on a backup/recovery product and in that I am into testing of SAP HANA backup/recovery using my third party backup tool.
    I have 4node(3+1) HANA setup with a total of 1.5TB RAM. I have created a DB of 1TB DB. I use this for testing backup performance of DB. As for backup persistent data is taken from the disk storage (shared in case of multi node setup) I want to know the size of DB on disks. When I use the following command to check the size of DB "select sum(allocated_page_size) from M_CONVERTER_STATISTICS" I get a size of around 950-970GB, which I feel is correct. But when I take backup of the same DB the backup size will be around 2TB. My log is in "OVERWRITE" state, so logs have some data as a duplicate copy is also ruled out.
    Request you to help me understand the reason for this difference in DB size on disk and in backup.
    Thanks,
    Prasanna

    My best guess is that MAX_SIZE is the total number of extents used for any purpose, whereas MAX_SORT_SIZE is the total number of extents ever used for sorting.
    Consider that temporary segments can be used for things other than sorting. Some examples are temporary LOB handling, backing storage for temporary tables, hashing, merging bitmaps, etc.
    Hope that helps,
    -Mark

  • Backup Size always = 2.0 GB

    Does anyone have the issue that in Storage & Backup, where it says, "Backup Size" the backup size is ALWAYS = 2GB, even though "Next Backup Size" & my phone listed under "Backups" is listed as 3.8GB. Anyone else have this issue?

    Its probably from past backups.
    I believe that where it says "Backup Size", its referring to the last backup you did on your phone.
    "next backup size" is greater because you increased the data on your phone since then.
    I had it off on my phone but just turned it on to check.
    It says Backup Size 0 bytes, and Next backup size 2.3GB.
    Hope that clears up your problem
    Edit: You can also just delete your old backup or overwrite the existing one to save space.

  • To calculate the size of backup for a particular database in RMAN catalog

    Hi ALL,
    Could you please guide me how I can calculate the size of backup data for a particular database in Recovery Catalog, if I am using Tapes as my backup media for recovery catalog.
    Regards
    Harpreet Singh

    Hi,
    I am not Up to the mark of your question ..
    If you see the V$log you can get it.. Size of the redo logs can be determined either by examining the file system size or by reading the BYTES column on the V$LOG view. Then Check the number of redo Logs avaialble checked whether they are mirrored or etc., Combining the two figures we have a total redo log data at peak in one day. This is the amount of data that any backup facility or storage of Archive Redo Logs would have to take into account. This figure should be mitigated against the fact that manual switching of redo logs means that not all archived redo logs will be the full size.
    - Pavan Kumar N

  • Estimate database backup size

    Hi All,
    AIX 5.3
    oracle 10.2.0.3
    I have production database of 80 GB. I want to take a cold backup during the upgrade process. Now i want to know database backup size. so we can free space from some mount point accordingly.
    Is there any way to estimate database backup size?
    Thanks,
    Vishal

    Question: how did you establish that your database is actually 80G?
    Is that 80G of data in the database, or is it the sum of all data files, temp tablespace files, undo tablespace files, redo logs, oracle binary software files, control files, etc?
    If you intend to do an upgrade of the software, my recommendation is to shut the database down and do a full copy of:
    1) your entire oracle product tree (usually /oracle/product), including ORACLE_HOME.
    2) your entire 'oradata' structure which (should) include all of your Oracle database data files and all other associated files.

  • Database size and backups

    I have deleted a large number of records from a database which accounted for much of the space being used as it was not needed at this time. When I take a backup of the database will the size of the db I then restore from this backup be reduced or should
    I shrink the database first. Didn't want to have to perform a shrink operation if not necessary as I've seen posts that it affects performance.
    Thanks
    Robert

    If you have deleted chunks of data and take the backup the size of the backup will be reduced. However if you want to release the unused space from the running database(with out backup and restore), you could do a shrink
    Have a look at this link
    http://dba.stackexchange.com/questions/28360/sql-server-database-size-didnt-decrease-after-deleting-large-number-of-rows
    from
    the above link
    I've blogged about this where I admonished folks to "Don't
    touch that shrink button!" but sometimes... Sometimes you need to. 
    Satheesh
    My Blog |
    How to ask questions in technical forum

  • Estimating the backup size for full database backup?

    How to estimate the backup file size for the following backup command?
    Oracle 10g R2 on HPUX
    BACKUP INCREMENTAL LEVEL 0 DATABASE;
    Thank you,
    Smith

    Depends on the number of used blocks, block size etc. You could probably get a rough formula for backup size based on the contents of dba_tab_statistics (subtract empty_blocks), dba_ind_statistics etc.

  • Different full backup size of identical databases

    Hello,
    I am on Oracle 10GR2.
    I have 1 database instance with size approximately 50GB. Today I created second instance with RMAN duplication process from the first instance. So now I have two similar DB instances with same size 50GB.
    What is strange to me is size of FULL LEVEL0 backups of these databases.
    Backup size of original database has approximately 22 GB, backup size of second (duplicated) instance has 7GB.
    Can you explain me why? Or what should I do with original database to have same small backup size.
    Executed RMAN command for backup is: BACKUP INCREMENTAL LEVEL 0 DATABASE PLUS ARCHIVELOG;
    Thank you

    select sum(bytes)/1024/1024/1024 GB from dba_segments;
    This select gives me 6,79 GB in both instances.
    I did not used UNTIL TIME for duplication.
    RMAN settings is same for both instances and I don't use any compression
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default

  • Database size versus table data size

    I ran the below query that queries all tables in the database and the total size for reserved space is 17GB. The database size is 294GB. Why is there such a big difference in size. I would expect the database to be a little bigger but not 277GB bigger.
    DECLARE @TableName VARCHAR(100)    --For storing values in the cursor
    --Cursor to get the name of all user tables from the sysobjects listing
    DECLARE tableCursor CURSOR FOR  
    select [name] from dbo.sysobjects  where  OBJECTPROPERTY(id, N'IsUserTable') = 1 FOR READ ONLY
    --A procedure level temp table to store the results
    CREATE TABLE #TempTable (     tableName varchar(100),     numberofRows varchar(100),     reservedSize varchar(50),     dataSize varchar(50),     indexSize varchar(50),    
    unusedSize varchar(50) )
    --Open the cursor
    OPEN tableCursor
    --Get the first table name from the cursor
    FETCH NEXT FROM tableCursor INTO @TableName
    --Loop until the cursor was not able to fetch
    WHILE (@@Fetch_Status >= 0) BEGIN     
    --Dump the results of the sp_spaceused query to the temp table     
    INSERT  #TempTable         
    EXEC sp_spaceused @TableName     
    --Get the next table name     
    FETCH NEXT FROM tableCursor INTO @TableName END
    --Get rid of the cursor
    CLOSE tableCursor
    DEALLOCATE tableCursor
    --Select all records so we can use the reults
    SELECT *  FROM #TempTable
    order by 2
    --Final cleanup!
    DROP TABLE #TempTable
    Alan

    Hi anaylor,
    According to your description, the database size is larger than sum of tables sizes. There could be a number of reasons , for example,
    • There may have the large transaction, or a lot of data in the database but it has been removed in some process.
    • Indexes/constraints are being stored in other files.
    •Last database cleanup (including table deletion, record deletion) did not affect any disk reclamation.
    •The initial size of the database is large.
    • Have you calculate unused spaces? Databases usually trade space for speeding and allocating huge amounts of disk space ahead of time, to avoid allocation at transaction time. Space freed by delete may be reused or not due to speed reasons.
    Hope it can help.
    Regards,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • Big increase in backup size after upgrade

    Hello
    I've upgraded my database from 10.2.0.4 SE on win2003-SP2 to 11.2.0.1.0 SE on win2008-R2-SP1 64-bit, by doing exp/imp
    The databasefiles size sums up to about 150gb on each server
    But when I do a normal RMAN database backup of the datafiles on the new database (backup device type disk database;) I get a backupset that is 78 gb in size .
    On the old database the backup size was only 36 gb
    The data in the two database is about the same, and I dont believe I'm using compression on  any of the database backups. I've listet the RMAN  paramaters below
    Can anybody tell me why I'm seeing this huge increase in backup size?
    Best regards
    Klaus Mogensen
    10g RMAN parameter settings:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   'C:\backup\vtrack\backupset\ora_df_%Y_%M_%D_%T_%t_s%s_s%p.bkp';
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\SNCFVTRACK.ORA'; # default
    11g RMAN parameter settings:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'E:\ORACLE\PRODUCT\11.2.0\DBHOME_1\DATABASE\SNCFVTRACK.ORA'; # default

    This is why,
    Your 10g channel device configuration:
    CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1
    Your 11g channel device configuration:
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    Your 10g backups were being compressed, the 11g are not.

  • Backup size is increased after resync catalog

    Hi everyone,
    I have describe my problem, if anyone have a solution please provide me.
    Rman catalog database version : 10.2.0.1.0, OS : red hat linux
    Target database version : 10.2.0.5.0, OS : solaris 10
    rman catalog database space is full, then i move my example tablespace to another location, but i forgot to change the ownership of new file.
    And I have no backup of my rman catalog database. so i offline the datafile first for opening the rman catalog database after opening the database I have offline the whole example tablespace and this tablespace cannot contain any thing related the catalog.
    after that I used the command : crosscheck archivelog all;
    DELETE EXPIRED ARCHIVELOG ALL
    then i run the command : CROSSCHECK BACKUP;
    DELETE EXPIRED BACKUP;
    then i run the command : report obsolete;
    delete obsolete;
    then i run the command : RESYNC CATALOG;
    then i run the command : change archivelog all validate;
    after doing all the thing when I am taking a backup of archive log by using following command :
    run {allocate channel c1 device type disk format '/appl2/prodback_rman/prod_fullbackup/ARCH_%d_%s.bak';
    backup archivelog all;
    before performing all the above thing my archive backup of whole day is around 5gb but after the above thing my archive backup of one day is around : 126gb
    and my level0 backup is alright after and before the above thing and the size is around : 139gb
    the script for the full backup is :
    run {allocate channel c1 device type disk format '/appl2/prodback_rman/prod_fullbackup/FULL_%d_%s_%c.bak';
    backup incremental level 0 database skip offline;
    after that I have perform the incremental level 1 backup by using the following script :
    run {allocate channel c1 device type disk format '/appl2/prodback_rman/prod_fullbackup/INC1_%d_%s_%c.bak';
    backup incremental level 1 database;
    before the above activity the size of incremental backup is around : 4.5gb but after performing the above activity the incremental backup size is around : 120gb
    it is very critical for me, if any one have the solution please provide me as early as possible.
    Thanks & Regards
    Rakesh Kumar

    Hi Hemant K Chitale,
    you said that I am using the COMPRESSED BACKUPSETs till 22-Jan, so I am posting
    the rman configuration here that is used before all this happening and same
    configuration is used right now.
    but before resync catalog the archivelog is generated only one location then I used to archive log
    dest for archive log generation then after 5 month I will resync my catalog. may be it is the
    reason.
    because there are no compressed backupset is defined in the rman configuration.
    RMAN> show all;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/appl2/prodback_rman/prod_fullbackup/ctrl_%F';
    CONFIGURE DEVICE TYPE DISK PARALLELISM 2;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT '/appl2/prodback_rman/prod_fullbackup/prod_%d_%s_%c.bak', '/appl2/prodback_rman/usb/prod_%d_%s_%c.bak';
    CONFIGURE MAXSETSIZE TO 20 G;
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/appl2/prodback_rman/prod_fullbackup/snapcf_PROD.f';
    Archive log generation log on the daily basis.
    SQL> select trunc(COMPLETION_TIME,'DD') Day, thread#,
    round(sum(BLOCKS*BLOCK_SIZE)/1048576) MB,
    count(*) Archives_Generated from v$archived_log
    group by trunc(COMPLETION_TIME,'DD'),thread# order by 1;
    DAY THREAD# MB ARCHIVES_GENERATED
    04-FEB-13 1 2776 37
    05-FEB-13 1 16767 220
    06-FEB-13 1 16545 216
    07-FEB-13 1 15772 208
    08-FEB-13 1 15056 198
    09-FEB-13 1 18486 244
    10-FEB-13 1 17591 232
    11-FEB-13 1 18163 238
    12-FEB-13 1 15062 198
    13-FEB-13 1 26383 342
    14-FEB-13 1 36279 462
    DAY THREAD# MB ARCHIVES_GENERATED
    15-FEB-13 1 34010 432
    16-FEB-13 1 32230 413
    17-FEB-13 1 31904 408
    18-FEB-13 1 33448 426
    19-FEB-13 1 34639 444
    20-FEB-13 1 36684 468
    21-FEB-13 1 27547 352
    right know the archive log backup size by rman is around 19gb per day.
    so tell me how we reduce the size of my archive log backup according to
    my rman configuration and how can i reduce the archive log generation on
    my production server on daily basis.
    Thanks & Regards
    Rakesh Kumar

  • Image size versus dimension

    I am just trying to get my head around image size versus dimension and an answer to my following question may solve it once and for all!    I save a jpg say at 1000 pixels wide and at 100 ppi at file quality 10.  But if I save the same file at 1000 pixels wide and again at 100 ppi but this time at quality 5 - what is happening to the file?   I have the same number of pixels in the photo but what is the quality slider actually doing?
    Many thanks
    Sue

    21st century or not, if you are talking about file integrity, nothing beats an EPS. Although as stated previously, EPS has definitely fallen out of popularity, partly I think due to cross-platform issues -- i.e., PC's inability to deal with them (talk about archaic) and partly due to hosting applications current ability to accept native files. EPSs are totally encapsulated, totally lossless, and totally impervious to hosting software interference -- which TIFFs, JPEGs, nor PSDs can boast. Basically, WYSIWYG.
    And yes, there actually are instances where you DO just re-save files -- usually in an attempt to clean up corrupt or problematic files -- but not just for the sake of re-saving. I agree, nobody does that. I was just making a point.
    I'm not advocating JPEGs and by no means do I advocate the constant re-saving of them. But I will not discount them as fodder or relegate them strictly to the internet! They are simply another tool in the toolbox. I do agree with you that saving as JPEG should be the last step in the production process. In addition, a full-bodied backup should be kept in reserve (be it TIFF, PSD, or heaven forbid, EPS).
    My original point was to address Sue's question of "Image versus Dimension" in JPEG format. My point with you is that JPEGs definitely have a place and some advantages when a balance of quality versus file size/storage space is an issue. It is ridiculous to simply discount JPEG to the web. Although I would not use it for a high-end brochure or an annual report, I wouldn't hesitate for a second to use JPEG for newsprint, high-end copying and some direct imaging. It is a sound format if applied properly based on the end usage. But by no means is it an end-all format. And, I think I work in the same world as you.

  • DB read_only backup size increase

    Hi Experts,
    Have below 3 queries. Kindly enough throw some light
    1) I have 1 database which is read_only. tlog backup size daily fluctuates how this is possible please...
    2)another question related to another problem
    backupset table of 1 database shows 65 MB full readonly database backup(named: abcd)  daily. here i am somply taking backup from litespeed.
    when i run backup database abcd to disk="c:\abcd.bak" with copy_only,checksum,init (in read only mode) it shows size of 57 MB only. Why there's gap as database is in read_only mode.
    3) buffercount and maxtransfersize are safe if i have x64bit machine and 100 GB RAM. restore verify completed successfully.
    Regards
    Manish

    1) Why are you taking a backup of a read only database every day ?
    Since nothing is changing just stick with the backup you already have. As for fluctuations you may be taking a backup that's added on the latest backup so it'll increase over time.
    2) There is no direct correspondence between size in BAK and MDF/LDF. You could have compressed tables or compressed backup, empty space etc etc
    3) Changing buffercount and maxtransfersize are safe to change. But first measure for what you gain from changing them since increasing them will have a higher impact on cpu time.
    Here are some benchmarks on those:
    http://www.mssqltips.com/sqlservertip/2539/options-to-improve-sql-server-backup-performance/
    "If there's nothing wrong with me, maybe there's something wrong with the universe!"

  • RMAN backup with smallest backup size

    Oralce 11g2 on Redhat 5. The diskspace is our tightest resource, and we want to an incremental backup with level0 on Sunday and level 1 every week days and Saturday. I am to use the comamnds to do the job--Sunday
    backup incremental level 0 tag 'level_0' database plus archivelog;
    --Other days
    backup incremental level 1 database plus archivelog delete all input;I do not think this is the best practice nor produce smallest backup files.
    What are you comments and opinions. Thanks

    Pavan, Thank you for reply. Here are the info requested
    what is size of DB ??
    ~250GB, including UNDO and TEMP. It is a dev database and not very big. But we have total 800GB disk space. After setting some housekeeoing folders, and allow some space for data growth, it leaves 180GB for flash_recovery_area.
    what would be max size of archive logs generated per day ??
    Variable from less than 1 GB to 12 GB
    Are you taking backups to tape or Disk ??
    Disk. In the 180GB flash_recovery_area, Current backup size is 152GB. If a backup fails to delete obsolete files, the next backup will fill the flash_recovery_area.
    Provide the Rman configuration information ??
    RMAN> show all;
    RMAN configuration parameters for database with db_unique_name TDEV2 are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F';
    CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/snapcf_tdev2.f'; # default

  • Finding correct backup size in sap level

    Hi All...
                 I want to know the successfull backup size in sap level can any one help me out in finding the correct path in detail log in db12 tcode.

    Hi,
    Are you using brbackup? If yes, go to DB12 -> Overview of database backups -> click on the backup log ID -> Detail log -> and look for "total size" and you'll see something like:
    BR0061I 63 files found for backup, total size 1165346.688 MB
    Thanks,
    Nicholas Chang

Maybe you are looking for

  • How Do I Find the Full URL for Linking to Messages in the Forum

    What is the best way to find the URL that links directly to a message I've posted in the forum? When I receive an e-mail notifying me that a reply has been posted in a thread I'm subscribe to, there is a link to that reply in a format similar to http

  • How to call the 'DETAIL' function in ALV for a program?

    Dear Friends, I have a prf_tree (TYPE REF TO cl_gui_alv_tree), and I added below codes to add an new button for displaying the detail record, it works fine: CALL METHOD prf_toolbar->add_button     EXPORTING       fcode     = prf_tree->mc_fc_detail   

  • Ensure that master data is unique across R/3 source systems within BW

    Hello all, I have an issue and don't have any clues for it. I wait for your suggestions , please. Problem:   we must ensure that master data (represented by Info objects) is unique across R/3 source systems within BW Thank you.

  • Mute button wont become unchecked

    Hi. my mute button on my mac mini will not become unchecked. so the sound is not working:(! please help!

  • How to unassign(delete assign) Organization Unit to User?

    How to <b>Unassign Organization Unit to User</b>? Is there any furnction module to do this ? <b>What are the function modules to update org unit of the user & to update the attributes of the user</b>? Update org unit means we have to delete & recreat