Traditional Logical Backup

We don't consider the Logical backup as main backup since it doesn't support Recovery.

Advantages of Logical Backup:

·         Logical backups are more useful in case of schema refreshes

·         Logical backups are useful in case of database upgradations as well as migrations

·         Logical backups are platform independent

·         Logical backups are more useful in case of DB-Reorg, Schema Re-Org and Table Re-Org

·         Files generated by Logical backup are Dump file and Log File

·         Dump file is partial binary and partial text in nature. Dump file contains metadata as well as Business data. Business data will be in encrypted format

·         Log file is a text file which shows the progress of the job.  Log file contains messages as well as error messages that are encountered during the progress of the job. By default a user can take backup of his own objects.

·         If a user wants to take backup of entire database, he must have exp_full_database  role. In the same way in order to import full database he must have imp_full_database role

·         In order to invoke exp and imp utilities, Database should be up and running

·         If you don't specify Dump file name, by default oracle creates a dumpfile with name expdat.dmp

·         If you specify same name for the dump file, simply it overwrites the  existing file

·         By default Traditional logical backup is conventional, which means it will go through the SGA processing layer  by specifying Direct=Y

·         During import sometimes we get undo related errors. To overcome this specify commit=Y
Commit=Y inserts array of records into the database and then commits

·         To suppress the DDL related errors(Eg: Object EMP is already available) during import, we can specify ignore=Y