RMAN Restore and Recovery - Oracle RMAN for Absolute Beginners - page 189

You can select from V$LOGFILE to verify that the online redo log names are correct:

SQL> select member from v$logfile;

Here is the output for this example:

/ora01/oraredo/DEVDB/redo01a.rdo
/ora01/oraredo/DEVDB/redo02a.rdo
/ora01/oraredo/DEVDB/redo03a.rdo
/ora01/oraredo/DEVDB/redo01b.rdo
/ora01/oraredo/DEVDB/redo02b.rdo
/ora01/oraredo/DEVDB/redo03b.rdo

Make sure the directories exist on the new server that will contain the online redo logs. For this example, here is
the mkdir command:

$ mkdir -p /ora01/oraredo/DEVDB

Step 14. Open the Database
You must open the database with the OPEN RESETLOGS command (because there are no redo logs, and they must be
re-created at this point):

SQL> alter database open resetlogs;

If successful, you should see this message:

Statement processed

■ Keep in mind that all the passwords from the newly restored copy are as they were in the source database.
you may want to change the passwords in a replicated database, especially if it was copied from production.

Note

Step 15. Add the Temp File
When you start your database, Oracle will automatically try to add any missing temp files to the database. Oracle
won't be able to do this if the directory structure on the destination server is different from that of the source server.
In this scenario, you will have to add any missing temp files manually. To do this, first take offline the temporary
tablespace temp file. The file definition from the originating database is taken offline like so:

SQL> alter database tempfile '/u01/dbfile/O12C/temp01.dbf' offline;
SQL> alter database tempfile '/u01/dbfile/O12C/temp01.dbf' drop;

Next, add a temporary tablespace file to the TEMP tablespace that matches the directory structure of the
destination database server:

SQL> alter tablespace temp add tempfile '/ora01/dbfile/DEVDB/temp01.dbf'
size 100m;

You can run the REPORT SCHEMA command to verify that all files are in the correct locations.