Configuring HP Serviceguard Toolkit for Oracle Data Guard

For each table space identified in the previous query, add a new temporary file to the standby

database. The following example adds a new temporary file called TEMP1 with size and

reuse characteristics that match the primary database temporary files:

SQL> ALTER TABLESPACE TEMP1 ADD TEMPFILE

2> “/arch1/standby/temp01.dbf”

3> SIZE 40M REUSE;

c. Start Redo Apply.

On the standby database, issue the following command to start Redo Apply:

SQL> ALTER DATABASE RECOVER MANAGED STANDBY

DATABASE DISCONNECT FROM SESSION;

This statement automatically mounts the database. Also, the statement includes the

DISCONNECT FROM SESSION option so that Redo Apply runs in a background session.

d. Test archival operations to the physical standby database.

The transmission of redo data to the remote standby location does not occur until after a log

switch. A log switch occurs by default when an online redo log file becomes full. To force a log

switch so that redo data is transmitted immediately, use the following ALTER SYSTEM statement

on the primary database. For example:

SQL> ALTER SYSTEM SWITCH LOGFILE;

7. Verify that the physical standby database is performing properly:

To see that redo data is being received on the standby database, you should first identify the

existing archived redo log files on the standby database, force a log switch and archive a few

online redo log files on the primary database, and then check the standby database again. The

following steps show how to perform these tasks.

a. Identify the existing archived redo log files.

On the standby database, query the V$ARCHIVED_LOG view to identify existing files in the

archived redo log. For example:

SQL> SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME

2 FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;

b. Force a log switch to archive the current online redo log file.

On the primary database, issue the ALTER SYSTEM ARCHIVE LOG CURRENT statement to

force a log switch and archive the current online redo log file group:

SQL> ALTER SYSTEM ARCHIVE LOG CURRENT;

c. Verify that 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#;

d. Verify new archived redo log files were applied.

On the standby database, query the V$ARCHIVED_LOG view to verify the archived redo log

files were applied.

SQL> SELECT SEQUENCE#, APPLIED FROM V$ARCHIVED_LOG

ORDER BY SEQUENCE#;