Subscribe to Posts by Email

Subscriber Count

    696

Disclaimer

All information is offered in good faith and in the hope that it may be of use for educational purpose and for Database community purpose, but is not guaranteed to be correct, up to date or suitable for any particular purpose. db.geeksinsight.com accepts no liability in respect of this information or its use. This site is independent of and does not represent Oracle Corporation in any way. Oracle does not officially sponsor, approve, or endorse this site or its content and if notify any such I am happy to remove. Product and company names mentioned in this website may be the trademarks of their respective owners and published here for informational purpose only. This is my personal blog. The views expressed on these pages are mine and learnt from other blogs and bloggers and to enhance and support the DBA community and this web blog does not represent the thoughts, intentions, plans or strategies of my current employer nor the Oracle and its affiliates or any other companies. And this website does not offer or take profit for providing these content and this is purely non-profit and for educational purpose only. If you see any issues with Content and copy write issues, I am happy to remove if you notify me. Contact Geek DBA Team, via geeksinsights@gmail.com

Pages

Undo backup optimization in 11g

Another little feature in 11g is undo backup optimization.

Prior to Oracle 11g, RMAN always backed up all UNDO with a full backup, including UNDO for committed blocks.

However in 11g, RMAN is able to skip the UNDO information for those blocks that are already committed and exceeded undo_retnention threshold.

This optimization brings in 11g to skip those undo blocks that are not needed for recovery operation. This allows backup of undo TS should be quicker and save some storage.

Further, there is a bug or behavior change that,

Bug 6399468: UNDO OPTIMIZATION
====> Undo optimization was changed from 'all undo not needed' to 'undo not in use older than 1 hour' ====> Undo optimization was changed from 'all undo not needed' to 'undo not in use older than 1 hour'
In unpublished bug , the Undo optimization was changed from 'all undo not needed' to 'undo not in use older than 1 hour'.

You can test the UNDO backup optimization by
1) Take a backup of UNDO TS via RMAN, note down the size
2) Do a massive transaction
3) Commit
4) Sleep for certain seconds
5) Take a backup of UNDO TS again, node down the size -, you might see here that UNDO TS size is not reduced
6) This is due to the bug mentioned above, where undo will only skip the changes that done past 1 hour. So lets try again

1) Take a backup of UNDO TS via RMAN, note down the size
2) Do a massive transaction
3) Commit
4) Sleep for certain seconds using dbms_lock.sleep(3600); --> 1 Hour
5) Take a backup of UNDO TS again, node down the size of backup --> now you may see the reduced size of file from the Step 1 above.
6) Your backup optimization is working.

-Thanks
Geek DBA

Comments are closed.