Primary Database Changes That Require Manual Intervention at a Physical Standby

Most structural changes made to a primary database are automatically propagated through redo data to a physical standby database. Table 9-1 lists primary database structural and configuration changes which require manual intervention at a physical standby database.

1. Add a datafile or create a tablespace
No action is required if the STANDBY_FILE_MANAGEMENT database initialization parameter is set to AUTO. If this parameter is set to MANUAL, the new datafile must be copied to the physical standby database.

2.Drop or delete a tablespace or datafile
Delete datafile from primary and physical standby database after the redo data containing the DROP or DELETE command is applied to the physical standby.

3.
Use transportable tablespaces
Move tablespace between the primary and the physical standby database.

4. Rename a datafile
Rename the datafile on the physical standby database.

5. Add or drop a redo log file group
Evaluate the configuration of the redo log and standby redo log on the physical standby database and adjust as necessary.

6.Perform a DML or DDL operation using the NOLOGGING or UNRECOVERABLE clause
Copy the datafile containing the unlogged changes to the physical standby database.

7.Grant or revoke administrative privileges or change the password of a user who has administrative privileges
If the REMOTE_LOGIN_PASSWORDFILE initialization parameter is set to SHARED or EXCLUSIVE, replace the password file on the physical standby database with a fresh copy of the password file from the primary database.

8.Reset the TDE master encryption key
Replace the database encryption wallet on the physical standby database with a fresh copy of the database encryption wallet from the primary database.

9.Change initialization parameters
Evaluate whether a corresponding change must be made to the initialization parameters on the physical standby database.

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/9599/viewspace-473008/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/9599/viewspace-473008/