I do not like to use logical backups for my main backup and recovery methodology. However, logical backups are useful for alternative recovery techiques. When someone accidentally drops a table, restoring the table from a dump file could be easier than performing a point-in-time restore from your physical backups. Oracle 9i made this a moot point with the ability to recover a dropped table with the FLASHBACK TABLE command. And Oracle 10g has made many more capabilities available with its variety of Flashback options.
In Oracle 10g, I do not see a need for logical backups, with one exception. If you might need to restore your data to a different platform, then a logical backup can help you out. For instance, you might be running your database on a high-end Unix server. Your company might have a disaster plan in place where the databases would run in a separate facility, possibly in a different city, in the event of a catastrophic failure which makes your current location unusable. To save money on this contigency plan, your company may have purchased a cheaper Linux server. In this case, it might be a good idea to create a logical backup and ship it off to your disaster recovery site. Outside of that special case, I prefer to use RMAN for all of my backup and recovery needs.
Dig Deeper on Oracle database backup and recovery
Related Q&A from Brian Peasland
Oracle expert Brian Peasland answers one reader's question about common pitfalls when connecting Oracle to outside programs. Continue Reading
One reader asks expert Brian Peasland a question about datafile sizes with the Oracle RMAN duplicate 10g command. Continue Reading
Managing parent table-child table relations in Oracle SQL environments is key to efficient programming. Continue Reading