2. Query the standby database:
SQL> SELECT NAME, UNRECOVERABLE_CHANGE# FROM V$DATAFILE;
6 rows selected.
3. Compare the query results of the primary and standby databases.
Compare the value of the UNRECOVERABLE_CHANGE# column in both query results. If the value of the UNRECOVERABLE_CHANGE# column in the primary database is greater than the same column inthe standby database, then the datafile needs to be copied from the primary site to the standby site.
In this example, the value of the UNRECOVERABLE_CHANGE# in the primary database for theusers01.dbf datafile is greater, so you need to copy the users01.dbf datafile to the standby site.
On the primary site, back up the datafile you need to copy to the standby site. Issue the followingSQL statements:
SQL> ALTER TABLESPACE users BEGIN BACKUP;
% cp users01.dbf /backup
SQL> ALTER TABLESPACE system END BACKUP;
Copy the datafile to the standby database.
Copy the datafile that contains the missing redo data from the primary site to location on the physicalstandby site where files related to recovery are stored.
On the standby database, restart Redo Apply.
Issue the following SQL statement:
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROMSESSION;
You might get the following error messages (possibly in the alert log) when you try to restart Redo Apply:
ORA-00308: cannot open archived log 'standby1'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/oracle/dbs/stdby/tbs_1.dbf'
If you get the ORA-00308 error and Redo Apply does not terminate automatically, you can cancel