Troubeshoot Oracle standby DB

8.3.1.2.2 Recovering From Errors
To correct the problems described in Section 8.3.1.2.1, perform the following steps:
1. Create the raw slice on the standby database and assign permissions to the Oracle
user.
2. Query the V$DATAFILE view. For example:
    SELECT NAME FROM V$DATAFILE;
NAME
-------------------------------------------------------------------------------
-
/u01/MILLER/MTS/system01.dbf
/u01/MILLER/MTS/undotbs01.dbf
Managing Primary Database Events That Affect the Standby Database
Managing a Physical Standby Database 8-9
/u01/MILLER/MTS/sysaux01.dbf
/u01/MILLER/MTS/users01.dbf
/u01/MILLER/MTS/mts.dbf
/dev/raw/raw100
/u01/app/oracle/product/10.1.0/dbs/UNNAMED00007
SQL - ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT=MANUAL;
SQL - ALTER DATABASE CREATE DATAFILE
           '/u01/app/oracle/product/10.1.0/dbs/UNNAMED00007'
           AS
           '/dev/raw/raw101';

3. In the standby alert log you should see information similar to the following:
    Fri Apr 8 10:09:30 2005
    alter database create datafile
    '/dev/raw/raw101' as '/dev/raw/raw101'
    Fri Apr 8 10:09:30 2005
    Completed: alter database create datafile
    '/dev/raw/raw101' a
4. On the standby database, set STANDBY_FILE_MANAGEMENT to AUTO and restart
    Redo Apply:
    SQL - ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT=AUTO;
    SQL - RECOVER MANAGED STANDBY DATABASE DISCONNECT;
    At this point Redo Apply uses the new raw device datafile and recovery continues.

om tyo - area wajib comment :)