Performing Oracle User-Managed Database Recoveries - OCP: Oracle Database 12c Administrator Certified Professional - page 61

e xeRCiSe 2.1 (continued)
'c:\oracle\oradata\orclnew\REDO01.LOG';
SQL>alter database rename file 'c:\oracle\oradata\orcl\REDO02.LOG' to
'c:\oracle\oradata\orclnew\REDO02.LOG';
SQL>alter database rename file 'c:\oracle\oradata\orcl\REDO03.LOG' to
'c:\oracle\oradata\orclnew\REDO03.LOG';
SQL>alter database rename file 'c:\oracle\oradata\orcl\SYSAUX01.DBF' to
'c:\oracle\oradata\orclnew\SYSAUX01.DBF';
SQL>alter database rename file 'c:\oracle\oradata\orcl\ SYSTEM 01.DBF' to
'c:\oracle\oradata\orclnew\ SYSTEM 01.DBF';
SQL>alter database rename file 'c:\oracle\oradata\orcl\TEMP01.DBF' to
'c:\oracle\oradata\orclnew\TEMP01.DBF';
SQL>alter database rename file 'c:\oracle\oradata\orcl\ UNDO TBS01.DBF' to
'c:\oracle\oradata\orclnew\ UNDO TBS01.DBF';
SQL>alter database rename file 'c:\oracle\oradata\orcl\USERS01.DBF' to
'c:\oracle\oradata\orclnew\USERS01.DBF';
5. Now that the files are copied into place, you can start up the database:
SQL> alter database open
Database opened.
That's it. You have recovered your database! Query to your heart's delight!
Recovering in NOARChivelOG Mode
Because of its limitations, you might ask yourself whether anyone really uses a database
in NOARCHIVELOG mode. The answer is yes.
The main benefit to running in NOARCHIVELOG mode is that you are not generating
archived redo logs. Archived redo logs require more space (sometimes a lot more
space). Often development or test databases do not require online backups or point-
in-time recovery, so running them in NOARCHIVELOG mode might make sense. Most
large shops will run all databases in ARCHIVELOG mode because of the added flexibil-
ity it provides.