When I get the hot RMAN backup using the following commands.
BACKUP DATABASE PLUS ARCHIVELOG;
BACKUP CURRENT CONTROLFILE;
I was expecting to see that the rman backup would be smaller since it
is copying the used blocks for the database. Should I shrink the
tables before the backup ?
You've neglected to consider that you're adding the archivelogs to the
mix; a BACKUP DATABASE should likely be smaller than the actual
database, but adding in the archivelogs expands that size
considerably.
David Fitzjarrell
>...but adding in the archivelogs expands that size
> considerably.
.. especially if there are lots of archived logs to backup *before* the
database backup.
-----
échangez opinions et commentaires dans les forums de discussion.
http://www.usenetgratuit.com/
I really appreciate the comments on adding the achivelog in the
backupset.
What are your thoughts about shrinking the tables before the backup ?
I can't see that such an act would benefit you in terms of the backup
size. A shrink will only take away unused space (that above the HWM),
not free space located below the high water mark, so you might save a
few blocks of space per table, but it likely won't be appreciable.
I can't recommend it, but others may have differing opinions.
David Fitzjarrell
Why?
If you don't have the space to back-up buy disks.
--
Sybrand Bakker
Senior Oracle DBA
Use compression in 10g
.......
We run Oracle 9iR2,10gR1/2 on RH4/RH3 and Solaris 10 (Sparc)
remove NSPAM to email
I agree with your recommendation, however, if you refer to shrink in
sense of "ALTER TABLE ... SHRINK ...", then it does free space below HWM .
Best regards
Maxim