Database Crashes During Hot Backup

There can be many reasons for the database to crash during a hot backupa power ou
tage or rebooting of the server, for example. If these were to happen during a h
ot backup, chances are that tablespace would be left in backup mode. In that cas
e you must manually recover the files involved, and the recovery operation would
end the backup of tablespace. It's important to check the status of the files a
s soon as you restart the instance and end the backup for the tablespace if it's
in backup mode.
select a.name,b.status from v$datafile a, v$backup b
where a.file#=b.file# and b.status='ACTIVE';
or
select a.tablespace_name,a.file_name,b.status from dba_data_files a,
v$backup b
where a.file_id=b.file# and b.status='ACTIVE';
This statement lists files with ACTIVE status. If the file is in ACTIVE state, t
he corresponding tablespace is in backup mode. The second statement gives the ta
blespace name also, but this can't be used unless the database is open. You need
to end the backup mode of the tablespace with the following command:
alter tablespace tablespace_name end backup;
Logical Export
Export is the single most versatile utility available to perform a backup of the
database, de-fragment the database, and port the database or individual objects
from one operating system to another operating system.