4
Using Oracle9i Data Guard Manager

This chapter shows how to use Oracle9i Data Guard Manager to create, manage, and monitor a Data Guard configuration.

This chapter contains the following sections:

• Section 4.1, "Starting Data Guard Manager"

• Section 4.2, "Creating a Configuration"

• Section 4.3, "Connecting to a Configuration"

• Section 4.4, "Enabling the Configuration, Sites, and Resources"

• Section 4.5, "Performing Routine Maintenance"

• Section 4.6, "Performing a Manual Switchover Outside of Data Guard Manager"

• Section 4.7, "Monitoring a Data Guard Configuration"

4.1 Starting Data Guard Manager

Start Data Guard Manager through the Oracle Enterprise Manager Console by taking the following steps.

Step 1 Start Oracle Management Server.

Start the Oracle Management Server from the command-line prompt by entering the oemctl start oms command.

Step 2 Launch the Oracle Enterprise Manager Console.

Launch Oracle Enterprise Manager at the command-line prompt by entering the oemapp console command. When the Enterprise Manager Console login dialog displays, you must select Login to the Oracle Management Server. Do not select Launch standalone, because Data Guard Manager will not be available from the Enterprise Manager Console if you select this option.

Step 3 Start the Intelligent Agent on the primary and standby nodes.

The Intelligent Agent must be running for Data Guard Manager to execute jobs and monitor events. Follow the directions in the Oracle Intelligent Agent User's Guide to configure and use the Intelligent Agent on the primary and standby nodes.

Step 4 Discover the primary and standby nodes.

Run the Enterprise Manager Discovery wizard, also referred to as Discovery wizard to discover the primary and standby nodes and gain access to the databases that you want to configure and administer with Data Guard Manager. To invoke the Discovery wizard from the Enterprise Manager Console menu bar, select: Navigator > Discover Nodes

Follow the directions in the Discovery wizard. When finished, all discovered nodes and databases are displayed in the Enterprise Manager navigator tree:

• On the primary node, the wizard discovers the primary database that you want to configure and administer with Data Guard Manager.

• On the standby node, the wizard discovers the following:
  • If you discover a standby node on which a standby database exists, the wizard gains access to the standby database and displays it in the Enterprise Manager navigator tree. When you run the Create Configuration wizard to create a configuration, you can have Data Guard Manager automatically add the existing standby database to the configuration.

  • If you discover a standby node on which a standby database does not exist, the wizard finds the Oracle home where you have installed the Oracle9i Enterprise Edition. When you run the Create Configuration wizard to create a configuration, you can select this Oracle home as the location in which you want Data Guard Manager to create a new standby database.

Step 5 Set Preferred Credentials on the primary and standby nodes.

You must set Preferred Credentials on both the primary and standby nodes to ensure Data Guard Manager can run Enterprise Manager jobs to create the configuration. To set Preferred Credentials from the Enterprise Manager Console menu bar, select: Configuration > Preferences > Preferred Credentials

Although setting Preferred Credentials for the databases is not required, you might want to set Preferred Credentials for the primary database and for the standby database if you are adding an existing standby database resource.

Step 6 Start Data Guard Manager.

You can start Data Guard Manager from the Enterprise Manager Console or at the command-line prompt:

• To start Data Guard Manager from the Enterprise Manager Console, use either of the following methods:
  • From the Tools menu in the Oracle Enterprise Manager Console, choose Database Applications > Data Guard Manager.

  • From the Database Applications drawer in the Oracle Enterprise Manager Console, move the cursor over the icons and select the Data Guard Manager icon.

  Figure 4-1 shows both methods of starting Data Guard Manager from the Enterprise Manager Console.

Figure 4-1 Starting Data Guard Manager

Text description of the illustration oemlaunch.gif

• To start Data Guard Manager from the command-line prompt, enter the oemapp dataguard command.

When launched, Data Guard Manager displays the informational page shown in Figure 4-2.

Figure 4-2 Oracle Data Guard Manager Main Window

Text description of the illustration dgwelcome.gif

On this page, you can:

• Click Quick Tour to call up the Data Guard Manager quick tour for an easy-to-follow product tour covering concepts and basic product operation.

• Click Help to display the Welcome to Oracle Data Guard Manager help topic. Once in the help system, you can use the Contents page or Help Search page to locate help topics of interest.

• Right-click Data Guard Configurations in the tree view to start the Create Configuration Wizard (described in Section 4.2).

4.2 Creating a Configuration

Creating a configuration is the first thing you must do before you can manage and monitor sites and resources. Data Guard Manager provides the Create Configuration wizard to create a configuration that includes a primary database and one standby database. To start the Create Configuration wizard, right-click Data Guard Configurations in the tree view and choose Create Configuration Wizard.

The wizard takes you through the following steps.

1. Ensure the Data Guard environment is set up properly.

2. Provide a configuration name.

3. Choose a primary database.

4. Choose how you want to add a standby database:
   • Import an existing standby database

   • Create a new standby database

5. Verify the information you supplied to the wizard and make changes, if necessary.

The following steps create a configuration in which a new standby database is created. It shows how to have the wizard use Oracle Recovery Manager (RMAN) to copy datafiles from the primary database to create the standby database.

Step 1 Ensure the Data Guard environment is set up properly.

Before the Create Configuration wizard steps you through the process of creating a Data Guard configuration, you must ensure some basic configuration requirements have been met on the primary and standby nodes.

When you click Details on the wizard welcome page shown in Figure 4-3, Data Guard Manager provides a handy checklist of setup requirements and information to help you ensure the environment is properly prepared.

Figure 4-3 Create Configuration Wizard - Welcome Page

Text description of the illustration crwiz_welcome_bottom.gif

Step 2 Provide a configuration name.

The next dialog asks you to provide the name of the new Data Guard configuration. Each configuration name must be an Oracle identifier that is unique among the configurations that you have created with Data Guard Manager.

Figure 4-4 shows the Configuration Name dialog in which a new configuration, DGConfig, is named.

Figure 4-4 Create Configuration Wizard - Configuration Name

Text description of the illustration crwiz_configname.gif

Step 3 Choose a primary database.

The list of discovered database instances listed on this page contains all of the instances that have been discovered through the Enterprise Manager Console Discovery wizard. (These were discovered during the setup work performed in Section 4.1 in the step titled, "Discover the primary and standby nodes.")

Figure 4-5 Create Configuration Wizard - Choose Primary Database

Text description of the illustration crwiz_primarydb.gif

To select a primary database, select the Oracle9i database instance that you want to serve in the role of a primary database for this Data Guard configuration. The database instance that you choose must be release 9.0.1 or greater, and it must be a primary database, such that the CONTROL_FILE_TYPE in the V$DATABASE view must be equal to CURRENT.

Note: Although the list of instances on this page may include both Oracle9i database instances and older instances (such as Oracle8i) that were discovered, only Oracle9i instances can be used.

Step 4 Choose how you want to add a standby database.

The wizard allows you to create a new standby database or add an existing standby database.

This scenario will create a new standby database, as shown in Figure 4-6.

Figure 4-6 Create Configuration Wizard - Standby Database Creation Method

Text description of the illustration crwiz_standbycreatemethod.gif

If you choose to add an existing standby database, the wizard displays a list of discovered database instances from which you select a standby database to import into the Data Guard configuration. The wizard prompts you to name the standby database and connects to that database.

If you choose to create a new standby database, the wizard takes you through the following additional steps:

• Select the Oracle home on the standby node in which you want to create the standby database.

  The wizard displays a dialog that lists all of the Oracle homes that have been discovered through the Enterprise Manager Discovery wizard. You must select a discovered Oracle home and provide a unique name for the standby site.

  Figure 4-7 shows this step of the configuration process.

Figure 4-7 Selecting an Oracle Home on the Standby Node

Text description of the illustration crwiz_standbyoraclehome.gif

• Select RMAN or OS (operating system) copy method to move datafiles to the standby node.

  Part of the creation process involves copying the datafiles for the primary database to the standby node. The Data Guard Manager offers two different ways to do this: using the Oracle Recovery Manager (RMAN) or using the operating system (OS) method.

  Figure 4-8 shows this step of the configuration process.

Figure 4-8 Choosing a Datafile Copy Method

Text description of the illustration crwiz_standbydatafilecopymethod.gif

This scenario chooses the RMAN method because it is the default and it has the advantage of being available on all supported Oracle platforms. The operating system (OS) method is not available on all platforms and will be dimmed if it is not available.

• Select the location where you want the datafiles to be copied.

  When using the RMAN copy method, you must specify path name information for the network directory on the primary host, the destination directory on standby host, and the standby archived log file directory fields. (As you type the destination directory, the wizard assumes your directory structure will be the same on the primary and standby hosts and mirrors your input to the Standby archived log file directory field at the bottom of the page.)

  Figure 4-9 shows this step of the configuration process.

Figure 4-9 Supplying Datafile Copy Location Information

Text description of the illustration crwiz_standbydatafilecopylocation.gif

Step 5 Verify the information you supplied to the wizard and make changes, if necessary.

Figure 4-10 shows the Options dialog on which all values are set automatically.

Figure 4-10 Create Configuration Wizard - Options

Text description of the illustration crwiz_options.gif

Although you do not have to provide any input, you can optionally make changes to any of its fields. Table 4-1 describes the default values for each field and includes comments about how the information is used.

Table 4-1  Optional Input to the Create Configuration Wizard

Field	By Default . . .	Comments
Standby instance name	This is the primary database name with _2 appended to it.	If you edit the default name shown, ensure the new name is unique on the standby host. Note that the name is case sensitive. For example, site and SiTe are distinctive names.
Standby initialization file	This file is derived automatically from a combination of the current parameter settings for the primary database and additional standby database settings. You can edit the standby database parameter file to add or modify its contents.	The wizard creates the initialization file for the standby instance in the platform-specific default Oracle home. (For example, on UNIX this would be $ORACLE_HOME/dbs/initinstance_name.ora). In the DGConfig example, the generated filename would be initrdbms2_2.ora. If a file with this name already exists, you will be prompted to change the instance name.
Standby LISTENER.ORA file	A LISTENER.ORA file must already exist in the default location of the standby Oracle home (for example, $ORACLE_HOME/network/admin/ on UNIX). Otherwise, the standby creation process will fail.	Whether or not you edit the file, the wizard: Installs the modified LISTENER.ORA file in the default location in the Oracle home. Starts the Oracle Net listener (or restarts it, if it is already running) that will listen for the new instance, using the lsnrctl utility.
Standby database SYSDBA password	Although Data Guard Manager does not require a remote login password file for the standby database, this dialog box allows you to create one for the standby database to enable remote connections.	The wizard uses the orapwd utility to create the remote login password file in the default location in the Oracle home where you installed the standby database. For example, on a UNIX system the name of the file is $ORACLE_HOME/dbs/orapw.
Shutdown primary database prior to datafile copy check box	The primary database remains open during the standby creation process, which results in a hot (inconsistent) backup of the datafiles.	You can select this option to shut down the primary database (with the immediate option) prior to creating the standby database instance. This will result in a cold (consistent) backup of the datafiles.

Next, the wizard provides a summary page on which you can verify the information that you provided as input. If you find an error or decide to rename something, click Back to move backward through the screens in the wizard. Otherwise, click Finish to begin creating the Data Guard configuration.

Figure 4-11 shows the summary page.

Figure 4-11 Summary Page for the Create Configuration Wizard

Text description of the illustration crwiz_summary.gif

Data Guard Manager opens a dialog box (shown in Figure 4-12) to display the progress of the create operation after you finish providing input to the wizard. The progress information that is displayed varies depending on whether you are importing an existing standby database or creating a new standby database.

You can click Show Details to display detailed information as the operation proceeds. When you select this option, the progress dialog window expands and displays all of the output from the Data Guard log file. Click Hide Details to hide the right-hand pane.

Click Close when the create operation is done to close the progress dialog window and return control to the Data Guard Manager main window.

Figure 4-12 shows the progress dialog after the successful creation of the DGConfig configuration.

Figure 4-12 Progress Dialog Box for Creating the Configuration

Text description of the illustration crwiz_prog_complete.gif

When the Create Configuration Wizard completes, a To Do list is displayed that describes some tasks that you must complete.

4.3 Connecting to a Configuration

You access the new DGConfig configuration (created in Section 4.2) through the Data Guard Configuration Connect Information dialog box. You can connect through either the primary or the standby database.

To connect, double-click the configuration name in the tree view; this launches the Data Guard Connect Information dialog box shown in Figure 4-13.

Figure 4-13 Configuration Connect Information Dialog Box

Text description of the illustration dgconnect.gif

The connection must be made using an Administrator account that has SYSDBA privileges. You supply the following information in this dialog box:

• User Name--Type the username for an account that exists for the database displayed in the Connect Through field.

• Password--Enter the password for the account you specified in the Username box.

• Configuration--You cannot edit this field. It specifies the name of the Data Guard configuration that you selected in the tree view when you invoked the Data Guard Configuration Connect Information dialog box.

• Connect as--You cannot edit this field. Connecting to a Data Guard configuration requires the SYSDBA role.

• Connect Through--Select the name of the primary or standby database through which you want to connect. The account specified in the Username box must have SYSDBA privileges for this database displayed in the Connect Through field.

• Save as Preferred Credential--If the configuration to which you are connecting was discovered using the Enterprise Manager Console Discovery wizard, save your connection credentials by clicking the Preferred Credentials check box in Enterprise Manager.

4.4 Enabling the Configuration, Sites, and Resources

When the configuration is first created, the configuration, site, and resource objects are disabled, which means that you cannot manage or monitor the objects because they are not under the control of Data Guard Manager.

When you finish configuring the sites and resources and connect to a broker configuration, you must enable the configuration to allow the Data Guard monitor to manage the configuration, and to bring the primary and standby database systems online.

After the configuration is enabled the first time, you can subsequently enable or disable:

• The entire configuration, including all its sites and resources

• A standby site, including the database resource on the standby site

• The primary database resource or the standby database resource

  Note: If you disable a configuration while connected to the standby database. You must be connected to the primary database when you re-enable the configuration.

Step 1 Enable the entire configuration.

To enable the entire configuration, right-click the configuration and select Enable/Disable, as shown in Figure 4-14.

Figure 4-14 Enabling a Configuration

Text description of the illustration dgenable_config.gif

Data Guard Manager displays a progress dialog box as it enables the configuration. When processing completes, click Close in the progress dialog box to dismiss the progress dialog box and allow the enable operation to complete.

Step 2 Verify the configuration was successfully enabled.

When processing completes, you should verify the configuration state and status information on the general property page.

For example, the state and status information in Figure 4-15 shows that the DGConfig configuration was successfully enabled. The operating state of the configuration, including its sites and database resources, has changed from unknown to online, and its normal status (checkmarks) verifies that the configuration is operating without errors or warnings.

Figure 4-15 Verifying that a Configuration Is Enabled

Text description of the illustration dgenable_config2.gif

4.5 Performing Routine Maintenance

Data Guard Manager can help simplify some of the routine maintenance tasks you must perform in the configuration. The following sections provide two examples: one shows how to take a site offline to replace a faulty disk drive and the other example dynamically changes an attribute of the LOG_ARCHIVE_DEST_n parameter.

4.5.1 Changing the State of a Database Resource

This section describes how to take the standby database resource offline for the purpose of replacing a faulty disk drive.

To change the state of the standby database to be offline, follow these steps:

1. In the tree view, select the standby database.

2. In the right-hand property sheet, click Offline.

3. Click Apply.

   (If you were changing the state of the primary database to offline, you would also need to click Yes in the pop-up dialog box that displays to confirm that you want to change its state.)

When you change the state of the standby database to offline, the standby database instance will be put into a started, nomount state and log apply services will be stopped. This temporarily pauses the application of the archived redo logs to the standby database while you replace the faulty disk drive. (Note that log transport services continue to archive redo logs to the standby site.) After completing your maintenance tasks, you can follow the same sequence of steps to bring the database online again.

Figure 4-16 shows the General property page after you change the state of the standby database to offline.

Figure 4-16 Verifying a State Change to the Standby Database

Text description of the illustration dg_offline_stdby.gif

4.5.2 Changing a Database Property

This section describes how to modify the LogArchiveDestOptions property.

Data Guard Manager automatically sets the critical properties for the standby database resource to a null value. Thus, when you created the DGConfig configuration with Data Guard Manager, the LogArchiveDestOptions critical property on the standby database was set automatically to a null value (LogArchiveDestOptions = ' ').

However, you can edit critical (and noncritical) properties at any time to tune your current environment. For example, suppose you want to edit the LogArchiveDestOptions property to specify the MANDATORY attribute. (The MANDATORY attribute of the LOG_ARCHIVE_DEST_n parameter requires a successful archival to the destination before an online redo log is available for reuse.) All you have to do is specify the attribute on the Properties page for the standby database resource. The new value overrides the current (null) value of the LOG_ARCHIVE_DEST_n parameter and also propagates the change to the primary site.

You can edit database resource properties if the configuration and its sites and databases are enabled, disabled, online, or offline. To edit the LogArchiveDestOptions property with Data Guard Manager, follow these steps:

1. In the tree view, select the standby database resource.

2. In the property sheet, click the Properties tab.

3. On the Properties page, click inside the Value column for the LogArchiveDestOptions property.

4. Enter MANDATORY.

5. Click Apply.

When you edit a property, the new property value dynamically overrides the value of the parameter specified in the initialization parameter file, but it does not modify the contents of the file.

Note: If the database is shut down and restarted outside of Data Guard Manager or the CLI, the database will revert to the original values that were set in the parameter file and the properties maintained by Data Guard will be inconsistent with the actual database values.

Figure 4-17 shows the Properties page for the standby database resource.

Figure 4-17 Properties Page for the Standby Database Resource

Text description of the illustration dg_dbproperties.gif

See Also: Section 3.3 for complete information about configurable database resource properties

4.6 Performing a Manual Switchover Outside of Data Guard Manager

There may be occasions when you need to perform some operations outside of Data Guard Manager. For example, you might want to temporarily exit from Data Guard Manager so that you can use SQL statements to perform a switchover operation between the primary database and standby databases.

This section provides the steps you must do to exit the GUI, perform a switchover operation, and then return to managing the configuration with Data Guard Manager.

Step 1 Delete the configuration.

When you delete a configuration from Data Guard Manager, you remove all objects in the configuration from management and monitoring through the GUI. It does not affect the underlying operations of the primary and standby databases, log transport services, or log apply services. Operations such as log shipping and log applying continue to function. However, these services are no longer manageable through Data Guard Manager.

To delete the configuration, from the Data Guard Manager menu:

1. Make sure you are connected to the configuration through the primary database.

2. In the tree view, select the configuration.

3. From the Object menu, select Delete.

Data Guard Manager displays a warning and asks you to confirm the delete operation.

Step 2 Exit from Data Guard Manager.

To exit from Data Guard Manager, choose File > Exit.

Step 3 Stop the Data Guard monitor.

On both the primary and standby sites, stop the Data Guard monitor by setting the DRS_START=FALSE parameter using the SQL ALTER SYSTEM statement.

SQL> ALTER SYSTEM SET DRS_START=FALSE;
System altered.

SQL> SHOW PARAMETER DRS_START
NAME         TYPE      VALUE
------------------------------------  
drs_start    boolean   FALSE

Step 4 Use SQL statements to perform a switchover operation.

Follow the instructions in Oracle9i Data Guard Concepts and Administration for complete information using the SQL ALTER DATABASE COMMIT TO SWITCHOVER statement on both the primary and standby sites to perform a switchover operation.

.

Note: After performing this step, you should stop and restart the Intelligent Agent on both nodes to rediscover the nodes and databases. See Oracle Intelligent Agent User's Guide for additional information.

Step 5 Re-create the configuration with Data Guard Manager.

Use the Create Configuration wizard and choose the Create Existing Standby option to create and enable the configuration based on the new primary and standby roles. (Follow the steps in Section 4.2 through Section 4.4.) Because the standby site is already created, you can use the Create Existing Standby method to create the standby database. This method takes only a few minutes to re-create the standby database.

4.7 Monitoring a Data Guard Configuration

Data Guard Manager provides the ability to monitor the status of a configuration as well as the redo log activity of the primary and standby databases.

For example, Figure 4-18 shows general information for all of the objects in the DGConfig configuration.

Figure 4-18 Displaying General Information About the Configuration

Text description of the illustration dg_offline_stdby.gif

The General tab for the Data Guard configuration not only displays information about the configuration, but it includes summary information about its sites and database resources. In Figure 4-18, for example, the summary information on the property page shows that the standby database is offline, while all other objects in the configuration are online and running with normal status. If you want to find out more information about why the standby database is offline, select the standby database resource in the tree view and view the database resource's property pages.

To ensure you are seeing the most current information, you should refresh the display often. To do this, either click the refresh icon on the toolbar or select Navigator > Refresh from the menu bar.

4.7.1 Using Event Tests

In addition to monitoring the status and log activity using Data Guard Manager, you can register event tests with Oracle Enterprise Manager to monitor the redo log activity on the primary and standby databases or monitor the status of the configuration as a whole.

You can create events using predefined event tests that are installed with Data Guard. Table 4-2 describes the six Data Guard event tests.

Table 4-2  Data Guard Event Tests

Event	Description
Actual Apply Delay	Measures the difference (in number of archived redo logs) between the current log at the primary database and the last log applied on the standby database.
Data Not Applied	Measures the time difference (in minutes) between the last archived redo log received and the last log applied on the standby database.
Logs Not Applied	Measures the difference (in number of archived redo logs) between the last log received and the last log applied on the standby database.
Logs Not Shipped	Measures the difference (in number of archived redo logs) between the current log on the primary database and the last log shipped to the standby database.
Potential Data Loss	Measures the time difference (in minutes) between the current redo log on the primary database and the last log received on the standby database.
Status	Checks the status of the Data Guard configuration. Note: If the status is not SUCCESS, then this event test is triggered.

Using the Enterprise Manager Event System, you can register one or more Data Guard event tests against both the primary and standby databases. You can also set up the Paging /Email Services to notify you through your pager or e-mail if any of the event tests are triggered.

In addition to registering the Data Guard event tests, consider registering the Node UpDown event test against each node where the Oracle Intelligent Agent is running. This event test monitors the node and the Intelligent Agent. Because the UpDown event test is triggered if any problems occur with the node or agent, it can be very beneficial in detecting problems that may prevent other event tests, including Data Guard event tests, from running.

See Also: Oracle Enterprise Manager help and documentation for more information about registering event tests and using the Paging/Email Services

4.7.2 Creating and Registering Data Guard Events

The example in this section describes how to create and register Data Guard event tests and set up for notification through e-mail when an event occurs.

Step 1 Ensure Oracle Enterprise Manager is prepared.

To prepare the Enterprise Manager environment for events, it is essential that you have performed the following prerequisite tasks:

• Ensure the Oracle Intelligent Agent is running on both nodes.

• Ensure the primary and standby nodes have been discovered (and therefore the primary and standby databases have been discovered).

• Set Preferred Credentials on both databases.

• Invoke Data Guard Manager and connect to the Data Guard configuration.

  Note: These tasks were discussed in detail in Section 4.1.

Step 2 Set up to receive event notification by pager or e-mail.

If you want to receive event notification by pager or e-mail, invoke the Paging/Email Services to set up the SMTP mail gateway and mail address of the person who will receive the event notification. From the menu bar on the Enterprise Manager Console, invoke the Paging/Email Services by selecting: Configuration > Configure Paging/Email

See Also: The Oracle Enterprise Manager documentation and help for a complete description of the Paging/Email Services

Step 3 Create the event tests.

From the menu bar on the Enterprise Manager Console, select:

Event > Create Event

Complete or modify the fields in the following Create Event system property pages:

• General--Specifies a name for the event, destination-target type, and event targets. To create one or more the Data Guard event tests, enter a user-friendly name for the Event Name, select Database as the Target Type, and add the primary and standby databases as the targets you want to monitor.

• Tests--Specifies the event tests that you want to create. You can select any event listed in the Available Tests tree view, including any of the Data Guard event tests that were described in Table 4-2. To see the list of Data Guard event tests, select:

  Database > Specialized > Data Guard

  For each event test that you want to create, select the test from the Available Tests view and click Add to move it to the Selected Tests list. In Figure 4-19, all of the Data Guard event tests have been selected.

Figure 4-19 Predefined Data Guard Event Tests

Text description of the illustration event_tests.gif

• Parameters--Specifies settings, such as the number of occurrences and threshold values, that you can customize for each event test. Parameters vary according to the event test selected. The available parameters for an event test are displayed when the event test is selected. Some event tests, such as Data Guard Status, do not have parameters.

• Schedule--Specifies how frequently you want the Oracle Intelligent Agent to run event tests. By default, all of the event tests run every 5 minutes (except for the Up/Down event test, which is checked at an interval set by the system itself).

  Note: You should experiment with the schedule setting because there is a trade-off between frequency of the test and the performance of your system. Running tests at a more frequent interval increases the workload on your system and may produce a noticeable effect on performance.

• Access--Specifies the access permissions that you want to assign for the event. You can allow other DBAs no access, full access, or restricted access so that other DBAs can only view the event or modify the event log. Because the example in this section is set up for e-mail notification, you should ensure that the Notify option is selected for each DBA who requires notification.

• Fixit Jobs--Specifies jobs that respond to specific error conditions. There are no fixit jobs for Data Guard event tests.

When you have completed all of the Create Event property sheets, select Register and Add to Library option on the bottom left side and then click Register and Add to send the event to the selected destinations. This adds the event to the Library and saves the event definitions.

When the event is submitted, the primary and standby database destinations are validated and the Intelligent Agent for each destination processes the event.

Step 4 View registered events.

If the registration is successful, the event displays in the Registered page of the Events pane. For example, Figure 4-20 shows that the event named Data Guard Event was registered successfully.

Note: Remember, the primary and standby nodes must already be discovered, Preferred Credentials must be set, the Intelligent Agent must be running, and you must be connected to the Data Guard configuration for the registration to be successful.

Figure 4-20 Viewing Registered Events

Text description of the illustration registered_event.gif

Step 5 View triggered events.

If an event condition is triggered or a threshold value is exceeded, a notification is sent to the General page of the Events pane in the Enterprise Manager Console.

Figure 4-21 shows some Data Guard events that were triggered after log transport and apply stopped between the primary and standby databases.

Figure 4-21 General Property Page of the Event Viewer

Text description of the illustration event_viewer_general.gif

In Figure 4-21, notice how the events return a different flag symbol and message, depending on the severity of the event. The severity levels are determined by the parameters you set for the event tests when you created them. See the Oracle Enterprise Manager online help system for more information about the different symbols.

When running the Data Guard event tests, an error might occur for the following reasons:

• The event test fails to run.

• The event test cannot call the Data Guard monitor (DMON) process.

Because the Paging/Email Services was set up, DBAs are also notified by an e-mail message similar to the one shown in Figure 4-22.

Figure 4-22 E-Mail Notification for the Actual Apply Delay Event

Text description of the illustration email_notification.gif

After an event condition is fixed, the event is cleared automatically. You can also clear an event by acknowledging it and moving it to the Events History page.