Standby Database: Support by BRARCHIVE 

In the standby database scenario, transfer of the offline redo log files from the primary to the standby instance can be controlled by the SAP utility BRARCHIVE. This is possible, since BRARCHIVE is able to copy offline redo log files to a hard disk.

A BRARCHIVE process runs on the primary host. It copies the offline redo log files to a mounted directory, which represents the archive directory (usually saparch ) on the standby host. The copy process runs through the network, BRARCHIVE must therefore be used with the verify option ( -w ).

A BRARCHIVE process also runs on the standby host. This process waits for the offline redo log files created in the mounted archive directory. If a redo log file was copied completely, BRARCHIVE assumes the task of importing these redo entries into the standby instance (option -m|- modify ), backing up the redo log file and deleting it if necessary.
BRARCHIVE therefore initiates the recovery process of the standby database, in which the offline redo log files are processed individually.

Importing the redo entries can be delayed by a few minutes (the delay is specified in the option -m <Delay(Minutes)> ). If a logical error occurs in the primary instance (for example, accidental deletion of a table), it is possible to prevent this error from being imported in the standby instance.
The offline redo log files are imported with the following ORACLE command: RECOVER STANDBY DATABASE ;

See: -m|-modify

To import the redo log files, the DB user (usually SYSTEM ) must have the SYSDBA authorization.

When redo entries are imported in which a structural change of the primary database is recorded, the BRARCHIVE process is terminated with the following ORACLE errors:

ORA-01670: new datafile <file_id> needed for standby database recovery

ORA-01157: cannot identify data file <file_id> - file not found

ORA-01110: data file <file_id> : ‘ <file_name> ‘

The structural change now needs to be incorporated manually in the standby database. To do this, you can use the command
ALTER DATABASE CREATE DATAFILE ‘<file_name>‘;
BRARCHIVE can then be started again.