Backupset compression differs from 10gR2 to 11gR2
Kev82FrSep 26 2012 — edited Sep 26 2012Hi,
I recently perform migration of my database from 10.2.0.4 to 11.2.0.3.
My problem is that my backupset compression ratio has changed and I haven't have enough disk space for bigger backupset.
For example :
Full backup of input size of 2.45T gave me backupset of 379.30G (10.2.0.4)
And now backup of input size 2.72T give me backupset of 525.31G (11.2.0.3)
Since the database is in 11gR2, there a new parameter in rman :
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE;
I changed it to :
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD FALSE;
But I don't know if I'll get smaller backupset with that (oracle documentation says that it can be)
What about ? :
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE '10.2' OPTIMIZE FOR LOAD FALSE;
Has someone experienced this problem ?
In this link : http://gavinsoorma.com/2009/12/11g-release-2-rman-backup-compression/
the dba tell that using 'BASIC' compression algorithm is the same as the compression in 10g, but that's not what's happening in my backups..
Any idea ?
B.Regards