28/10/2001
But, in general terms, any import followed by manual re-entry of lost records is going to be a good deal easier (and cheaper) to perform than an equivalent incomplete recovery. Whats more, in 9i, it is possible to combine export/import with Log Miner to guarantee total data recovery for the affected table. Thats because in 9i you can include supplemental log groups for a table which, despite the name, simply means that a transaction against a table causes the Primary Key (or any other nominated columns) to be included in the redo stream for that transaction. Therefore, the possibility now arises of recovering a table from import, and then mining the Logs for all transactions that affected the table after the time of the relevant export. Using the Primary Key information stored in the Logs, those transactions can then be re-applied to the freshly-imported table without trouble. Unfortunately, this approach cant work in anything earlier than 9i, because in those earlier versions, the redo stream identifies all records affected by transactions only by their rowids and when you run import, you can pretty well guarantee that every recovered row has a brand new row id, thus rendering the redo stream inapplicable to that tables recovered data. Nevertheless, using Log Miner, you can get a reasonable idea of what transactions (and how many of them) hit the affected table, and thus be more precise about what transactions need to be repeated, albeit manually. Export has other uses, of course such as being able to logically clone a database without too much drama, and without requiring the original database to be closed down in the process (which a true clone really requires). It also allows a database to be transferred to a completely different Operating System (Unix to NT, for example), provided the dump file is ftpd to the new machine in binary mode. No physical backup can pull that one off. Finally, being a logical backup of the database, it allows distribution of databases or parts thereof to third parties, without them having to worry about exactly how, physically, the database should be configured. In summary, if youre relying on export as your only method of backup, you want your head tested. Conversely, any DBA not performing regular exports because s/he thinks the physical backup is sufficient is just asking for trouble (or miraculously has Users that never make mistakes). Exports complement physical backups, and a decent DBA would be wise to do both.
28/10/2001
Page 2 of 2