Merged Incremental Strategy creates backups larger than expected
(Doc ID 413265.1)
Last updated on FEBRUARY 13, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 10.1.0.2 to 10.2.0.4 [Release 10.1 to 10.2]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
This problem can occur on any platform.
Symptoms
Using the script below to run an incremental level 2 backup, the output file is larger than expected. The backups total size was 500G when it should be less then 35G for this customers database.
RMAN> run {
allocate channel t1 type disk;
allocate channel t2 type disk;
allocate channel t3 type disk;
allocate channel t4 type disk;
allocate channel t5 type disk;
allocate channel t6 type disk;
allocate channel t7 type disk;
allocate channel t8 type disk;
recover copy of database with tag 'MERGE_PROD' until time 'sysdate - 10';
backup incremental level 2 tag 'MERGE_PROD' for recover of copy database skip offline skip inaccessible ;
release channel t1;
release channel t2;
release channel t3;
release channel t4;
release channel t5;
release channel t6;
release channel t7;
release channel t8;
}
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |