RMAN 1.1 Types of Failure

Statement Failures

1. When a program attempts to enter invalid data into an Oracle Table.
2. Long data insertion job or data import job to fail midway between there is no more room to put the data in.
3. Proper privileges to perform a task.

User process Failure

1. abnormal disconnect or performing a terminal program error and losing the session connection.
2. DBA not much work to do here.
3. BG process rollback the uncommitted transaction  changes to the data and releases the locks.

Instance Failure

1. Your database comes down such as Hardware , a power failure and an emergency shutdown procedure.
2. An instance shutdown when the key Oracle bg process such as PMON shutdown because of an error condition.
3. Check Alert log and trace files.
4. Just restarting the Database instance using by STARTUP Command.
5. The database was clearly shutdown and the database files aren’t synchronized.
6. Oracle will perform an automatic instance or crash recovery at this point.
7. Automatically perform a rollback uncommitted transactions by using the data from undo segments and roll forward committed changes it in the online redo logs.
8. Don’t need to any sort of backup when restarting the database.

Network Failure

1. Net listener, NIC and network connection has failed.
2. DBA must configure the multiple network cards.

User Error

1. Wrongly deleting  data from table and dropping a table you can use FLASHBACK feature.
2. If the transactions not completed yet, rollback statement.
3. Oracle LOGMINER also comes on handy situation like this.

Media Failure

1. It occur when you lose a disk or a disk  controller fails.
2. Examples of media failure  i) Head crash II) File corruption III)Overwriting or deleting of a datafile.
3. Any one of the multiplexed control files are deleted or lost because of disk failure you must restore the missing control file from an existing control file.
4. Datafiles, undo table space is deleted or lost because of a disk failure.If you lose one of these files, the instance may shutdown or may not sutdown in such case

         sql> shutdown abort;           Then

         sql>startup mount

          Restore the datafiles and recover it.

1.         An entire redo log group lost. if you have atleast one member of the redo log group , your database instance can continue to operating normally.
2. Restore the log file by copying one of  the other members of the same group.