Backing Up Oracle - Computing at Cornell

8.3.2 Complete recovery
Next, we created the following RMAN command file and executed it:
Unfortunately, RMAN was not able to take to datafile online after the
successful restore and recover. We had to execute exactly the same
command in a SQL*Plus session, and it worked fine:
Finally, user user1 was able to select all rows from its table.
Our database oslo on an AIX system failed, because of a handling error with
SAN zoning and the AIX lost access to that disk device. We had a file system
/u02/oradata on that drive and some datafiles, an archivelog destination and a
control file in this file system. The database was running in ARCHIVELOG mode
and an incomplete backup, started by cron, which was running just before
that happened. We had to recover the database to a most current state. To
achieve that, we performed following steps:
We edited the initoslo.ora file in the $ORACLE_HOME/dbs directory:
- We changed the log_archive_dest_2 to /u03/oradata/oslo/arch instead
of /u02/oradata/oslo/arch.
- We changed the control_files parameter. Originally, we had control
files in /u01/oradata/oslo, /u02/oradata/oslo and /u03/oradata/oslo - we
simply removed the string containing the /u02/oradata/oslo.
We created a new directory for the second log archive destination by the
command mkdir -p /u03/oradata/oslo/arch.
110 Backing Up Oracle using Tivoli Storage Management