8.3 Managing Primary Database Events That Affect the Standby Database
8.3 管理主库能影响备库的事件To prevent possible problems, you must be aware of events on the primary database that affect a standby database and learn how to respond to them. This section describes these events and the recommended responses to these events.
In some cases, the events or changes that occur on a primary database are automatically propagated through redo data to the standby database and thus require no extra action on the standby database. In other cases, you might need to perform maintenance tasks on the standby database.
Table 8-1 indicates whether or not a change made on the primary database requires additional intervention by the database administrator (DBA) to be propagated to the standby database. It also briefly describes how to respond to these events. Detailed descriptions of the responses are described in the section references provided.
The following events are automatically administered by redo transport services and Redo Apply, and therefore require no intervention by the database administrator:
A SQL ALTER DATABASE statement is issued with the ENABLE THREAD or DISABLE THREAD clause.
The status of a tablespace changes (changes to read/write or read-only, placed online or taken offline).
A datafile is added or tablespace is created when the STANDBY_FILE_MANAGEMENT initialization parameter is set to AUTO.
Table 8-1 Actions Required on a Standby Database After Changes to a Primary Database
| Reference | Change Made on Primary Database | Action Required on Standby Database |
|---|---|---|
| Section 8.3.1 |
Add a datafile or create a tablespace 添加文件或创建表空间 |
If you did not set the STANDBY_FILE_MANAGEMENT initialization parameter to AUTO, you must copy the new datafile to the standby database. 如果STANDBY_FILE_MANAGEMENT初始化参数没有设置为AUTO，那么你必须将新的数据文件拷贝到备库 |
| Section 8.3.2 |
Drop or delete a tablespace or datafile 删除表空间或数据文件 |
Delete datafiles from primary and standby databases after the archived redo log file containing the DROP or DELETE command was applied. 从主库删除数据文件，备库机会应用包含DROP或者DELETE命令的归档重做日志来应用 |
| Section 8.3.3 |
Use transportable tablespaces 使用传输表空间 |
Move tablespaces between the primary and standby databases. 在主备库之间移动表空间 |
| Section 8.3.4 |
Rename a datafile 重命名一个数据文件 |
Rename the datafile on the standby database. 在备库重命令数据文件 |
| Section 8.3.5 |
Add or drop redo log files 添加或删除重做日志文件爱你 |
Synchronize changes on the standby database. 在备库上同步改变 |
| Section 8.3.6 |
Perform a DML or DDL operation using the NOLOGGING or UNRECOVERABLE clause 使用NOLOGGING 或者UNRECOVERABLE 执行DML或者DDL操作， |
Send the datafile containing the unlogged changes to the standby database. 向备库发送包含没有日志记录的文件 |
| Chapter 13 |
Change initialization parameters 改变初始化参数 |
Dynamically change the standby parameters or shut down the standby database and update the initialization parameter file. 动态的改变备用的参数或者关闭备库，再更新初始化参数文件 |
8.3.1 Adding a Datafile or Creating a Tablespace
8.3.1添加一个数据文件或者创建一个表空间The initialization parameter, STANDBY_FILE_MANAGEMENT, enables you to control whether or not adding a datafile to the primary database is automatically propagated to the standby database, as follows:
STANDBY_FILE_MANAGEMENT初始化参数文件，能使用控制是否在添加数据文件到主库自动传播到备库，如下：
If you set the STANDBY_FILE_MANAGEMENT initialization parameter in the standby database server parameter file (SPFILE) to AUTO, any new datafiles created on the primary database are automatically created on the standby database as well.
如果STANDBY_