This chapter summarizes the SQL and SQL*Plus statements that are useful for performing operations on standby databases in a Data Guard environment. This chapter includes the following topics:
This chapter contains only the syntax and a brief summary of particular SQL statements. You must refer to the.Oracle Database SQL Reference for complete syntax and descriptions about these and other SQL statements
See Chapter 13 for a list of initialization parameters that you can set and dynamically update using the ALTER SYSTEM SET
statement.
Table 15-1 describes ALTER DATABASE
statements that are relevant to Data Guard.
Table 15-1 ALTER DATABASE Statements Used in Data Guard Environments
ALTER DATABASE Statement | Description |
---|---|
|
Adds one or more online redo log file groups or standby redo log file groups to the specified thread, making the log files available to the instance to which the thread is assigned. See Section 8.3.5 for an example of this statement. |
|
Adds new members to existing online redo log file groups or standby redo log file groups. See Section 5.7.3.2 for an example of this statement. |
|
This statement is for logical standby databases only. Use it to enable full supplemental logging before you create a logical standby database. This is necessary because supplemental logging is the source of change to a logical standby database. To implement full supplemental logging, you must specify either the See Oracle Database SQL Reference for more information. |
|
Note: On logical standby databases, you issue the See Section 7.2.1 and Section 7.3.1 for examples of this statement. |
|
Creates a control file to be used to maintain a physical or a logical standby database. Issue this statement on the primary database. See Section 3.2.2 for an example of this statement. |
|
Drops all members of an online redo log file group or standby redo log file group. See Section 8.3.5 for an example of this statement. |
|
Drops one or more online redo log file members or standby redo log file members. |
|
The primary database must be mounted but not open when you issue this statement. See Section 3.1.1 for an example of this statement. |
|
Mounts a standby database, allowing the standby instance to receive redo data from the primary instance. |
|
Opens a previously started and mounted database:
See Section x.x for an example of this statement. |
|
This statement is for logical standby databases only. It prepares the primary database and the logical standby database for a switchover by building the LogMiner dictionary before the switchover takes place. After the dictionary build has completed, issue the See Section 7.3.1 for examples of this statements. |
|
This statement starts and controls Redo Apply on physical standby databases. You can use the Note: Several clauses and keywords were deprecated and are supported for backward compatibility only. See Oracle Database SQL Reference for more information about these clauses. |
|
The |
|
The Include See Step 4 in Section 7.2.2 for examples. |
|
See Section 5.8.4 for an example of this statement. |
|
Instructs log apply services to continue applying changes to the physical standby database until you issue the command to convert the database to a logical standby database. See Section 4.2.4.1 for more information. |
|
Resets the target recovery incarnation for the database from the current incarnation to a different incarnation. |
|
Use this clause to specify the level of protection for the data in your Data Guard configuration. You specify this clause from the primary database, which must be mounted but not open. |
|
This statement is for logical standby databases only.It starts SQL Apply on a logical standby database. See Section 6.4.1 for examples of this statement. |
This statement is for logical standby databases only.Use the |
|
Performs a failover. The standby database must be mounted before it can be activated with this statement. Note: Do not use the
|
Table 15-2 describes an ALTER SESSION
statement that is relevant to Data Guard.
Table 15-2 ALTER SESSION Statement Used in Data Guard Environments
ALTER SESSION Statement | Description |
---|---|
|
This statement is for logical standby databases only. This statement allows privileged users to turn the database guard on and off for the current session. See Section 7.3.2 for an example of this statement. |