On the primary database, issue the ALTER SYSTEM SWITCH LOGFILE statement to force a log switch and archive the current online redo log file group:

SQL> ALTER SYSTEM SWITCH LOGFILE;

Step 3 Verify the new redo data was archived on the standby database.

On the standby database, query the V$ARCHIVED_LOG view to verify the redo data was received and archived on the standby database:

SQL> SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME

2> FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;

SEQUENCE# FIRST_TIME NEXT_TIME

---------- ------------------ ------------------

8 11-JUL-02 17:50:45 11-JUL-02 17:50:53

9 11-JUL-02 17:50:53 11-JUL-02 17:50:58

10 11-JUL-02 17:50:58 11-JUL-02 17:51:03

11 11-JUL-02 17:51:03 11-JUL-02 18:34:11

4 rows selected.

The archived redo log files are now available to be applied to the physical standby database.

Step 4 Verify new archived redo log files were applied.

On the standby database, query the V$ARCHIVED_LOGview to verify the archived redo log files were applied.

SQL> SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG

2 ORDER BY SEQUENCE#;

SEQUENCE# APP

--------- ---

8 YES

9 YES

10 YES

11 YES

4 rows selected.

See Section 5.9.1, "Monitoring Log File Archival Information"andSection 8.5.4, "Monitoring Log Apply Services on Physical Standby Databases"to verify redotransport services and log apply services are working correctly.

?

3.3 Post-Creation Steps

At this point, the physical standby database is running and can provide the maximum performance level of data protection. The following list describes additional preparations you can take on the physical standby database:

■ Upgrade the data protection mode

The Data Guard configuration is initially set up in the maximum performance mode (the default). SeeSection 5.6for information about the data protection modes and how to upgrade or downgrade the current protection mode.

■ Enable Flashback Database

Flashback Database removes the need to re-create the primary database after a failover. Flashback Database enables you to return a database to its state at a time in the recent past much faster than traditional point-in-time recovery, because it does not require restoring datafiles from backup nor the extensive application of redo data. You can enable Flashback Database on the primary database, the standby database, or both. SeeSection 12.4andSection 12.5for scenarios showing how to use Flashback Database in a Data Guard environment. Also, seeOracle Database Backup and Recovery Advanced User's Guidefor more information about Flashback Database.?

If you wish to failover to this standby database, you should use the following command to manually register the archivelog for recovery:
ALTER DATABASE REGISTER LOGFILE '/u01/app/oracle/arch1/boston/1_33_802470095.arc';