Hey, did you catch that redirect? The Toad World URL is now community.toadworld.com. Don't worry -- you'll still find all the same great content here (and more on the way). We're just in the process of giving our Toad World site some well-deserved love. Stay tuned for some more updates coming this way.
Meanwhile, enjoy community.toadworld.com.
To maintain the standby database, the standby database must be mounted and put into standby recovery mode. As redo logs are archived at the primary site, these logs must be transferred to the remote site and applied to the standby database.
To maintain your standby database in recovery mode, perform the following procedures:
ALTER DATABASE MOUNT STANDBY DATABASE [EXCLUSIVE/PARALLEL]
RECOVER [FROM 'location'] STANDBY DATABASE
As the archived logs are generated at the primary site, you must continually transfer and apply them to the standby database. Also, you can only apply logs to the standby database that have been archived on the primary database.
Note that there are administrative operations on the primary database which make changes to the primary database's control file. These changes need to be propagated to the standby database's control file. In this case it is necessary to refresh the standby database's control file from the primary database's modified control file.
To refresh your standby database's control file, perform the following procedures:
ALTER DATABASE CREATE STANDBY CONTROL FILE AS 'filename'
ALTER SYSTEM ARCHIVE LOG CURRENT
If you use the CREATE CONTROLFILE command on the primary database to change the maximum number of data files, instances, or redo logfile groups, the physical size of the control file changes and then you must refresh the standby database control file.