1. Shut down the database by issuing the SHUTDOWN ABORT command.
2. Restore the most recent database backup to a different location.
3. Edit the parameter file to indicate the new location of the control file.
4. Start an Oracle instance using the restored backup files and edited parameter file and mount the database by issuing the STARTUP MOUNT PFILE=INITSID.ORA command. Note: do not open the database at this point.
5. Update the control file with the new file location by issuing the ALTER DATABASE RENAME FILE <FILENAME> TO <FILENAME>; command.
6. The location for all restored datafiles and online redo log files must be updated in the control file. To check the information about the file location change, use the data dictionary view V$DATAFILE, which shows all datafile information recorded in the control file.
7. Repeat step 5 until all the necessary file locations are changed.
8. Open the database by issuing the ALTER DATABASE OPEN; command.

Any database backup that is not consistent is an inconsistent backup. A backup made when the database is open is inconsistent, as is a backup made after an instance failure or SHUTDOWN ABORT command. When a database is restored from an inconsistent backup, Oracle Database must perform media recovery before the database can be opened, applying any pending changes from the redo logs.
Note: RMAN does not permit you to make inconsistent backups when the database is in NOARCHIVELOG mode. If you employ user-managed backup techniques for a NOARCHIVELOG database, then you must not make inconsistent backups of this database.
If the database runs in ARCHIVELOG mode, and you back up the archived redo logs and datafiles, inconsistent backups can be the foundation for a sound backup and recovery strategy. Inconsistent backups offer superior availability because you do not have to shut down the database to make backups that fully protect the database.