Professional Documents
Culture Documents
9i Data Guard Manager
9i Data Guard Manager
June, 2001
Table of Contents
ORACLE DATA GUARD MANAGER............................................................................8
Welcome to Oracle Data Guard Manager ................................................................................8 How Does Oracle Data Guard Manager Work? .......................................................................9 What are Configuration, Site, and Resource Objects?.............................................................. 10 Getting Started...................................................................................................................... 11
Before You Get Started.............................................................................................................................................11 Discovering Nodes .....................................................................................................................................................12
To discover nodes: ................................................................................................................................................12 Usage Notes.....................................................................................................................................................12 Related Topics ................................................................................................................................................12
Additional Requirements When Creating a New Standby Database................................................................14 Creating a Data Guard Configuration....................................................................................................................16
To start the Create Configuration Wizard:..........................................................................................................16 Usage Notes.....................................................................................................................................................16 Related Topics ................................................................................................................................................16
To change the state of a database resource:.........................................................................................................22 To change the standby database resource to be read-only:..................................................................................22 Usage Notes.....................................................................................................................................................22 Related Topics ................................................................................................................................................22
Refreshing the View..................................................................................................................................................32 Registering Events.....................................................................................................................................................33 Removing a Configuration from Data Guard Manager.......................................................................................34
To remove a Data Guard configuration:.............................................................................................................34 Usage Notes.....................................................................................................................................................34
Properties Tab - Database Resource ......................................................................................................................41 Log Files Tab - Database Resource.........................................................................................................................42
To display Log Files tab for the primary database:.............................................................................................42 To display Log Files tab for the standby database: .............................................................................................42 Usage Notes.....................................................................................................................................................42
Create Configuration Wizard - Standby Database Type .....................................................................................54 Create Configuration Wizard - Standby Oracle Home .......................................................................................55
Usage Notes.....................................................................................................................................................55
Choosing the Recovery Manager (RMAN) method:...........................................................................................56 Choosing the operating system (OS) method: .....................................................................................................56 Related Topics ................................................................................................................................................56
Events.................................................................................................................................. 61
Data Guard - Actual Apply Delay.............................................................................................................................61 Data Guard - Data Not Applied.................................................................................................................................62 Data Guard - Logs Not Applied................................................................................................................................63 Data Guard - Logs Not Shipped................................................................................................................................64 Data Guard - Potential Data Loss............................................................................................................................65 Data Guard - Status....................................................................................................................................................66
Exit Command.............................................................................................................................................................73
To exit from Data Guard Manager: ....................................................................................................................73
File Menu.....................................................................................................................................................................74
Related Topics ................................................................................................................................................74
Glossary.......................................................................................................................................................................75 Help Menu....................................................................................................................................................................76 Data Guard Main Window.........................................................................................................................................77 Navigator Menu ..........................................................................................................................................................78
Troubleshooting .................................................................................................................... 86
Cleaning Up After A Failed or Canceled Configuration Creation....................................................................86
On the primary node:...........................................................................................................................................86 On the standby node: ...........................................................................................................................................86
Error and Status Messages ......................................................................................................................................87 Progress Dialog When Creating a New Standby Database................................................................................88
Usage Notes.....................................................................................................................................................88 Related Topics ................................................................................................................................................88
ARCHIVEDESTDEPENDENCY PROPERTY..............................................................90
Usage Notes ..............................................................................................................................................................90
ARCHIVELAGTARGET.................................................................................................91
Usage Notes ..............................................................................................................................................................91
CONFIGURING THE STANDBY ENVIRONMENT ..................................................92 COPYING DATAFILES...................................................................................................93 CREATING THE DATA GUARD CONFIGURATION ...............................................95 FALCLIENT PROPERTY...............................................................................................96
Usage Notes ..............................................................................................................................................................96
FALSERVER PROPERTY..............................................................................................97
Usage Notes ..............................................................................................................................................................97
LOGARCHIVEDESTOPTIONS PROPERTY...............................................................98
6
LOGXPTSTATUS PROPERTY.....................................................................................100 MOUNTING PRIMARY DATABASE.........................................................................101 OPENING PRIMARY DATABASE.............................................................................102 PROGRESS DIALOG DURING A SWITCHOVER OPERATION ..........................103
Usage Notes ............................................................................................................................................................103
RENAMING DATAFILES ............................................................................................104 RETRIEVING LISTENER CONFIGURATION FILE...............................................105 SHUTTING DOWN PRIMARY DATABASE.............................................................106 STANDBYARCHIVEDEST PROPERTY ....................................................................107
Usage Notes ............................................................................................................................................................107
STANDBYFILEMANAGEMENT PROPERTY..........................................................108
Usage Notes ............................................................................................................................................................108
As the figure shows, Oracle9i Data Guard Manager works through the broker to easily create and monitor a two-node Data Guard environment from a single management interface. Oracle9i Data Guard Manager: Automates the tasks involved in setting up and managing a standby database environment. Is integrated with Oracle Enterprise Manager to provide enhanced monitoring, alert, and control mechanisms for all systems in a Data Guard configuration Allows you to change the state of a Data Guard configuration. For example, you can enable or disable the sites and database resource objects in the configuration. Provides a way to change the value of database resource properties. For example, you can change some of the attributes of the log transport services such as the location of archived redo log files arriving from a primary database. Once configured, Data Guard Manager provides monitoring capabilities so you can oversee the entire configuration from a single management interface. Plus, you can use the Oracle Enterprise Manager Job Scheduling services to automate standard and repetitive tasks, such as executing a SQL script or running an operating system program on your primary and standby databases.
10
Getting Started
11
Discovering Nodes
You must discover the primary and standby nodes that you want to configure and administer with Data Guard Manager. You use the Discovery Wizard in the Oracle Enterprise Manager Console to discover them; you cannot discover nodes through Data Guard Manager. To discover nodes: From the Navigator menu In the Oracle Enterprise Manager Console, choose Discover Nodes. The Console starts the Discovery Wizard. Follow the steps in the Discovery Wizard, adding nodes that contain the databases you want to discover and subsequently access with Data Guard Manager. Click Finish. Databases on the nodes you specified are displayed in the Navigator tree in the Console. When you use Data Guard Manager, these databases appear when you run the Create Configuration Wizard. Usage Notes For more information about Oracle Enterprise Manager and discovering nodes, see the Oracle Enterprise Manager help. Related Topics Discovering Data Guard Configurations
12
13
Start the Intelligent Agent on the primary and standby nodes Discover the primary and standby nodes using the Discovery Wizard
Additional Requirements When Creating a New Standby Database If you plan to have the wizard create a new standby database, ensure the following additional tasks have been performed: Task Verify the location of the listener.ora file on the standby node Comments The wizard automatically modifies the standby node's listener configuration file. The wizard assumes that it will find a listener configuration file in the default location ($ORACLE_HOME/network/admin/listener.ora on UNIX platforms) of the standby Oracle home that you choose for the new standby database. While this is the standard situation for a Oracle installation, ensure that the file exists in the standby Oracle home
14
prior to beginning. Set Preferred Credentials on the primary and standby nodes Decide on a method for copying datafiles to the standby node See Setting Preferred Credentials.
Part of the creation process involves copying the primary database datafiles to the standby node. There are two methods to do this: the Oracle Recovery Manager (RMAN) or an operating system (OS) copy. Each method has its own setup requirements that apply only when the primary and the standby are on different systems. If you use RMAN (the default method), verify the RMAN copy preparation. See Using the Recovery Manager (RMAN) Method. If you use OS copy, verify the remote access. See Using the Operating System (OS) Method.
15
In the tree view, right-click the Data Guard Configurations container and select Create Configuration Wizard. On the Object menu, select Create Configuration Wizard. See Create Configuration Wizard Welcome for more information about providing input to the wizard. Usage Notes You can create multiple Data Guard configurations in the same Data Guard Manager window. Each configuration must have a unique primary database and standby database. There is no limit on the number of Data Guard configurations that you can configure and monitor from Oracle Data Guard Manager. When you complete the Create Configuration Wizard, Data Guard Manager opens a window to display the progress of the operation. When the Create Configuration Wizard completes, you must connect to the Data Guard configuration. See Connect to a Data Guard Configuration. When the Create Configuration Wizard completes, the Data Guard configuration is disabled. You must enable it to start managing the Data Guard configuration. See Enabling or Disabling Configuration Objects. When the Create Configuration Wizard completes, a To Do list is displayed that contains several tasks that you must complete. Related Topics Before You Get Started Create Configuration Wizard - Welcome Create Configuration Wizard - Setup Requirements Cleaning Up After A Failed or Canceled Configuration Creation
16
17
18
19
20
21
22
23
24
25
26
27
28
Editing a Configuration
You can edit a Data Guard configuration to change its state from online to offline or from offline to online. To edit a Data Guard configuration: In the tree view, select the configuration. In the Object menu, select Edit. (Or, select Edit from the right-click menu.) See Object Menu Configuration Related Topics Change the State of a Data Guard Configuration Configuration States Changing the Health Check Interval
29
30
Editing a Site
You can edit a site to change its state from online to offline or from offline to online. To edit a site: In the tree view, select the site. In the Object menu, select Edit. (Or, select Edit from the right-click menu.) See Object Menu Configuration Related Topics Change the State of a Site
31
32
Registering Events
Data Guard provides the ability to monitor the status of a configuration as well as the redo log activity of the primary and standby databases to ensure that the configuration is running properly. In addition to being able to view the status and redo log activity using Data Guard Manager, you can register Enterprise Manager event tests to monitor Data Guard so that you will be notified of any problems. By taking advantage of the event tests, you do not have to be connected to Data Guard Manager to receive problem notification. There are six predefined events tests that will monitor the Data Guard configuration. Using Enterprise Manager Console, you can register all of the Data Guard event tests against both the primary and standby databases. The Status event test monitors the status of the Data Guard configuration, and the remainder of the event tests monitor the redo log activity on the primary and standby databases. You can set up the Paging /Email services to notify you via your pager or e-mail if any of the event tests are triggered. In addition to registering the Data Guard event tests, you should also register the Node UpDown event test against the node where the Intelligent Agent is running. This event test will monitor the node as well as the Intelligent Agent. This event test will be triggered if any problems occur with the node or agent; such problems may prevent other event tests, including Data Guard event tests, from running. For more information about Enterprise Manager Event framework and Paging/Email services, see the Oracle Enterprise Manager help.
33
34
35
The database resource is enabled automatically when you enable the Data Guard configuration or the site on which the database resource is located. You can also view resource information on the General tab for the site or the General tab for the configuration. This page does not refresh automatically. You might need to refresh the view to see changes. See Refreshing the View. The Last Refreshed Message at the bottom of the property sheet displays the date and time when you last refreshed Data Guard Manager. Related Topics Database Resource States Changing the State of a Database Resource Properties Tab - Database Resource Refreshing the View
36
Note: It is important to check the configuration status to verify that it is operating properly. Information Displays the name of the Data Guard configuration, its status, and whether or not the configuration is enabled. Summary Displays a summary table of all sites in the Data Guard configuration. The summary table includes the list of sites in the configuration and the current state, status, and role of each site. You can optionally display both the sites and resources configured on each site: Select Show Sites Only to display a summary table of the sites in the configuration. Select Show Sites and Resources to display a summary table of the sites and resources in the configuration. Position the mouse over the icon in the Status column to display the text of any error message. See Configuration Status. Usage Notes A login dialog pops up to establish a connection to the Data Guard configuration, if necessary. See Connect to a Data Guard Configuration. When you change the state of the Data Guard configuration, it effects the state of all of the sites and resources in the configuration. You can make configuration changes when the configuration is offline, such as property changes. However, the configuration changes will take effect only after you change the state of a Data Guard configuration to the online state. See Change the State of a Data Guard Configuration. This page does not refresh automatically. You might need to refresh the view to see changes. See Refreshing the View. The Last Refreshed Message at the bottom of the property sheet displays the date and time when you last refreshed the window. Related Topics Configuration States
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
Information Required for Both the OS and the RMAN copy methods
Destination directory on standby host. The pathname of the actual (native) directory on the standby node to which the datafiles will be copied. In the above example, this is specified as /standby/datafiles, because that is the name of the actual datafile location on the standby host (as opposed to the virtual name, /mnt/datafiles, with which that location is accessed from the primary host). Note that as you type the destination directory, it is mirrored to the standby archived redo log file directory area at the bottom of the dialog. Standby archived redo logs directory. This is the pathname of the actual (native) location on the standby host where the archived redo logs shipped from the primary will be copied. These logs may take up a large amount of space on the standby host. Thus, you may want to specify the exact destination location. The default value for this field is the value specified in Destination directory on the standby host.
57
58
kind of entry that will be added in this case: SID_DESC=(SID_NAME=rdbms2)(ORACLE_HOME=/home/oracle)) If no existing listeners are configured to listen on a TCP port, a new listener is added and configured to listen on port 1521 (the default Oracle port), and the new standby instance is added to the new listeners SID_LIST. (Note: A check is not performed to ensure that port 1521 is available.) If an existing listeners SID_LIST is modified to include the new standby instance, that listener will be restarted during the creation process (if its currently running) to pick up the new instance. Other listeners that may be running out of other Oracle homes on the standby host are ignored. It is assumed that any listeners running from the new databases Oracle home will not collide with these other listeners. Standby database SYSDBA password The creation process will attempt to create a remote login password file for the standby database to enable remote connections to the database. (Note: A remote login password file is not necessary for Data Guard operation; it is only needed to allow remote connections to the database from clients, such as other Enterprise Manager tools.) Following is the algorithm that is used by the creation process to determine if a standby password file can be created: If you manually add a REMOTE_LOGIN_PASSWORDFILE entry in the standby initialization parameter file (by editing the standby parameter file through the Options page), a remote login password file will not be created by the standby creation process on the assumption that there is an existing password file. If the password file does not exist in the standby Oracle Home, and it is possible to create it, it will be created using the password you specified, or by using change_on_install as the password if none was specified. If there is a pre-existing password file in the standby Oracle Home and you did not add "remote_login_passwordfile" to the standby initialization parameter file, you will be interactively queried (during the creation progress dialog) on whether you want to use the existing file. If you answer Yes, a REMOTE_LOGIN_PASSWORD=SHARED entry will be put in the standby parameter file. If you answer No, no entry will be added, and you will be reminded to handle the problem in the post-creation checklist dialog that displays after the creation progress dialog is closed. Otherwise, there is no existing password file, its not possible to create one (for example, the orapwd executable was not found on the standby host), and you did not manually add the parameter to the initialization file. Nothing is done and you will be reminded to handle the problem in the postcreation To Do checklist. Shutdown primary database prior to datafile copy checkbox This checkbox displays only if the primary database is currently open. This results in a hot, or inconsistent, backup of the datafiles. Normally, the standby creation process proceeds with the primary remaining open. However, if you select this option, the primary database will be shut down (with the immediate option) started, and mounted prior to performing the standby creation. This will result in a cold (consistent) backup of the datafiles. Note: This checkbox displays only if the primary database is open and Data Guard Manager is not going to automatically shut down the database for any reason.
59
60
Events
61
62
63
64
65
66
Reference Topics
Configuration States
When enabled, a configuration, site, or database resource can be in one of two general states: offline or online: Offline: If you take a Data Guard configuration offline, the configuration and all its dependent sites and resources are also taken offline. For example, the databases in the configuration will be closed and not mounted, and the log transport services will stop sending archived redo log files to the standby database. Online: The Data Guard configuration is online and its database resources are running the log transport services and log apply services to ship and apply archived redo log files to the standby database. Data Guard Manager uses a stoplight icon Usage Notes When you change the state of the Data Guard configuration, it affects the state of all of the sites and resources in the configuration. State transitions for the entire Data Guard configuration cascade to the sites, which in turn cascade to the resources on each site. Related Topics Database Resource States Enabling or Disabling Configuration Objects to give a visual indication of the state.
67
Configuration Status
A Data Guard configuration can be in any of the following status modes: Status Normal Icon Description The configuration, including all of the database resources configured in it, is operating as specified by the user. All of the resources that are ONLINE are operating properly without any warnings or errors. One or more of the database resources in the configuration has failed and may no longer be operating as specified by the user. To obtain more information, locate each resource and examine its error status to reveal the source of the problem. One or more of the database resources in the configuration is not operating as specified by the user. To obtain more information, locate each resource and examine its warning status to reveal the source of the problem. The configuration is disabled. Therefore the state is unknown.
Error
Warning
Unknown
68
69
Connect to a Data Guard Configuration Change the Database that you Connect Through
70
71
Usage Notes To change the standby database to be read-only; log apply services stopped, see Changing the State of a Database Resource. When the log transport services are in the stopped state, the archived redo logs are not archived to the standby database. When the log apply services are in the stopped state, the redo logs are not applied to the standby database. Related Topics Enabling or Disabling Configuration Objects
72
Exit Command
To exit from Data Guard Manager: Choose the Exit command from the File menu, Or, press ALT/F4 , Or, click X on the title bar to close the window.
73
File Menu
The File menu provides an Exit command to exit from Data Guard Manager. Related Topics Exit Command
74
Glossary
broker A distributed management framework that automates and simplifies most of the complex operations required to create, control, and monitor a Data Guard configuration. You can perform these operations using either of these interfaces: Oracle9i Data Guard Manager or the Data Guard command-line interface (DGMGRL). critical property Properties for resources can be either critical and noncritical. A critical property is one that must be set for the Data Guard configuration to function properly. Data Guard Configuration A collection of one or more sites and resources that you want to manage as a group. menu bar The menu bar provides commands that you can issue against the object you select in the tree view. The menu bar appears at the top of the window, below the title bar. noncritical property Properties for resources can be either critical and noncritical. If a noncritical database property is not set, then Data Guard uses the value that is in the initialization parameter file. property sheets Property sheets allow you to set parameters and display the status of Data Guard objects. Property sheets appear on the right-hand side of the window when you select an object from the tree view. roles An Oracle9i database can be in one of two mutually exclusive roles: primary or standby. You can change the roles dynamically, either via a pre-planned switchover transition or via a failover as the result of an unplanned failure. toolbar The toolbar contains a subset of the most commonly used menu bar commands. The toolbar displays to the left of the tree view pane. Place the mouse pointer over a toolbar icon to display a description of the action that will be performed when you click the toolbar icon. tree view The tree view represents all objects and resources in the Data Guard configuration. The tree view appears on the left-hand side of the Oracle Data Guard main window. The tree view is also known as the navigator.
75
Help Menu
The Help menu lets you issue commands to access help. Contents--Opens Oracle Data Guard Manager online help system and displays the first topic. Search for Help on--Displays the Contents and Search tabs for the Oracle Data Guard Manager help system. Using Help--Provides general information about how to use the online help system. About Data Guard Manager--Displays the version number and copyright date for the Oracle Data Guard Manager software you are using.
76
77
Navigator Menu
The Navigator Menu provides a Refresh command to update the display of information in the Data Guard Manager window. Related Topics Refreshing the View
78
79
Object Menu
The following commands can appear on the Object menu or the right-mouse menu when an object is selected. The options on the Object menu vary depending on what you have currently selected in the navigation tree. When you select: Data Guard Configurations at the top of the tree view, the Object Menu allows you to invoke the Create Configuration wizard. The configuration name in the tree view, the Object Menu provides the following options: Edit Delete Remove from Navigator Connect Disconnect Enable/Disable View Log Verify A primary site in the tree view, the Object Menu allows you to edit the site. A standby site in the tree view, the Object Menu allows you to edit the site, or to enable or disable the site. A database (primary or standby) resource in the tree view, the Object Menu allows you to edit the database resource, or to enable or disable the database resource.
80
81
Site States
When enabled, a site object can be in one of two general states: offline or online: Offline: If a sites state is offline, the site has been turned off. If you take a site offline, all of its dependent resources are also taken offline. Thus, the database instances on the site will be put into a started, nomount state. If this is a primary database resource, then the log transport services will stop sending archived redo logs to the standby database. If this is a standby database resource, then the log apply services will stop applying the archived redo logs to the standby database. Online: If a site is online, the site is operating and performing a designated activity. The site is being managed through Data Guard Manager and each database resource for the site will be put into its appropriate state: The primary database will be open and the transport services will ship archived redo log files to the standby database. The standby database will be mounted and the log apply services will apply archived redo logs to the standby database.
82
83
84
85
Troubleshooting
86
87
88
89
ArchiveDestDependency Property
You must set this property on the standby site to specify the dependency attribute for the LOG_ARCHIVE_DEST_n parameter. The site name can be the primary or a standby site name on which this site depends for receiving archived redo log files. If this property is not set on the standby database, then the log transport services will not be enabled. For example, consider one primary site (Boston) and two standby sites (San Jose and Chicago respectively). Suppose you want to specify that San Jose depends on Chicago for its archived redo log files. Then, you update the property ArchiveDestDependency of the San Jose database resource to value Chicago. To edit the value of the ArchiveDestDependency property, see Editing a Database Resource. Usage Notes Use the LogArchiveDestOptions property to configure all other LOG_ARCHIVE_DEST_n parameters. The ArchiveDestDependency property is a critical database property. See Critical Database Resource Properties.
90
ArchiveLagTarget
You can optionally set this property on the primary site to update the attributes of the ARCHIVE_LAG_TARGET=seconds initialization parameter setting. This property limits the amount of data that can be lost and effectively increases the availability of the standby database by forcing a log switch after the amount of time you specify (in seconds) elapses. That way, the standby database will not miss redo records generated from a time range longer than a value of the ARCHIVE_LAG_TARGET parameter. To edit the value of the ArchiveLagTarget property, see Editing a Database Resource. Usage Notes The ArchiveLagTarget property is a noncritical database property. See Noncritical Database Resource Properties.
91
92
Copying Datafiles
This is the most time-consuming part of the creation process. In this step, the primary database datafiles and controlfile are copied to locations on the node that will host the standby database. There are many reasons why this step can fail. If it is successful, all datafiles and the standby controlfile have been copied to the standby node. Cancelable: Yes. All copy processes in progress on the primary node will be stopped. A cancel will not, however, remove any files that have been partially or completely copied to the standby destination. Troubleshooting: Data Guard performs this step by submitting an Enterprise Manager Job. If the job fails, the error is displayed in the following places: Data Guard Manager progress dialog window. You should be able to diagnose the problem based on the output in the progress dialog. Enterprise Manager job history entry in the Jobs History pane. To examine the job history, look for an entry named Backupnnn for an RMAN copy, or OSCopynnn for an operating system (OS) copy. (In both cases, nnn is a sequence number.) If there is more than one entry, look for the most recent sequence number. (Only failed Create Configuration jobs are displayed in the Jobs History pane; successful jobs are not kept in the history list.) View the job and examine the Failed entry in the job log for an explanation of what failed. See the Oracle Enterprise Manager Administrator's Guide for more information. Problem Solving: Problem: The RMAN copy failed. Solution: A failed RMAN copy is probably due to an error encountered by the RMAN process. The output from a failed RMAN process will be returned to the progress dialog, including any ORA errors returned by RMAN. Consult the Oracle9i Recovery Manager documentation and the Oracle9i Error Messages documentation for an explanation of the error. Problem: The OS copy failed. Solution: A failed OS copy may be due to errors encountered running the UNIX operating system commands required for the job to perform the actual copy. On UNIX, the rcp utility is used for noncompression copies, and the rsh utility is used for compression copies. To successfully run either of these utilities, you must correctly configure the UNIX environment on the primary node. Then, the owner of the Oracle Enterprise Manager job (specified in the Enterprise Manager Preferred Credentials for the primary node) can use UNIX r-commands (for example, rcp and rsh). See the rhosts manual page on the UNIX operating system for details about the setup requirements. Also, the following conditions may result in the failure of rsh and rcp commands: A UNIX r-commands environment that was set up incorrectly may result in the rcp or rsh utility failing with a permission denied error. An incorrectly specified destination directory (for example, a nonexistent directory or one for which you do not have write permission) may result in the rcp utility failing with a permission denied error. If you have output generated by your UNIX .profile/.cshrc file, this may cause the rcp utility to behave unpredictably. (See the UNIX rcp manual page for details.) In this case the O/S copy job may complete successfully even though it did not actually copy the datafiles and/or controlfile to the standby location. The standby creation process will likely fail during a later step because of missing datafiles and/or the controlfile. Problem: Standby database file system is out of space. Solution: A destination file system that is out of space is a potential cause of job failure. Problem: OS copy fails when copying the control file.
93
Solution: If an OS copy successfully copies all datafiles, but fails at the point where the standby control file is being copied (as indicated in the progress dialog), the command to create the standby control file may have failed in the primary database. The copy step actually creates the standby control file immediately prior to copying the file to its destination. Examine the primary database Alert log to see if the ALTER SYSTEM CREATE STANDBY CONTROLFILE command resulted in an error. Problem: Data Guard Manager may have timed out waiting for the job to complete. Solution: This will be apparent if the step fails but there is no output in Jobs History pane (Enterprise Manager Console) indicating a job failure. It is possible the job was never submitted if the Intelligent Agent is not running on the standby node, or the job may have been submitted but it never started due to a problem with either the Intelligent Agent or the Oracle Management Server (OMS).
94
95
FalClient Property
You can optionally set this property to update the attributes of the FAL_CLIENT parameter. This property updates the FAL_CLIENT=OracleNet_Service_Name initialization parameter setting, which is the Oracle Net service name used by the primary database to refer to the standby database. To edit the value of the FalClient property, see Editing a Database Resource. Usage Notes The FalClient property assigns the FAL (Fetch Archive Log Server) client name used by the FAL server to refer to the FAL client. The FalClient property is a noncritical database property. If you never change the FalClient property and the current FAL_CLIENT parameter for the standby database is empty, then the database resource automatically sets the value to the net service name for the standby database. See Noncritical Database Resource Properties.
96
FalServer Property
You can optionally set this property to update the attributes of the FAL_SERVER=OracleNet_Service_Name initialization parameter setting. Set this on the standby database resource to assign the FAL (Fetch Archive Log Server) server for the standby database. Set this property to an integer value to see the progression of the archiving of redo logs to the standby database. Oracle database server writes an audit trail of the archived logs received from the primary database into a trace file. To edit the value of the FalServer property, see Editing a Database Resource. Usage Notes The FalServer property is a noncritical database property. If you never change the FalServer property and the current FAL_SERVER parameter for the standby database is empty, then the database resource automatically sets the value to the net service name for the primary database. See Noncritical Database Resource Properties.
97
LogArchiveDestOptions Property
You must set this property to specify the attributes of the LOG_ARCHIVE_DEST_n parameter (for example, "optional, reopen=30"). If this property is not set, the Data Configuration will not function properly. Data Guard Manager initially sets the value to an empty string. To edit the value of the LogArchiveDestOptions property, see Editing a Database Resource. Usage Notes You cannot specify the service and location attributes with the LogArchiveDestOptions property, because these attributes are maintained automatically by the Data Guard broker. You cannot specify the dependency attribute with the LogArchiveDestOptions property. Use the ArchiveDestDependency property to configure the dependency attribute of the LOG_ARCHIVE_DEST_n parameter . The LogArchiveDestOptions property is a critical database property. See Critical Database Resource Properties.
98
LogArchiveTrace Property
You can optionally set this property to specify the attributes of the LOG_ARCHIVE_TRACE=integer initialization parameter. Set this property to an integer value to see the progression of the archiving of redo logs to the standby database. Oracle writes an audit trail of the archived logs received from the primary database into a trace file. To edit the value of the LogArchiveTrace property, see Editing a Database Resource. Usage Notes The LogArchiveDestOptions property is a noncritical database property. See Noncritical Database Resource Properties.
99
LogXptStatus Property
This is a read-only property that contains the error status (if any) of the log transport services for each of the currently enabled standby sites. The error status can be an empty string that indicates no error.
100
101
102
103
Renaming Datafiles
This step is accomplished by the same Enterprise Manager job that performed Step 4 (Configuring the Standby Environment) and Step 5 (Starting the Physical Standby Database). The job completes the standby setup process by performing the following actions on the standby instance: Renames the standby instance datafiles to correspond to the datafile location on the standby node. Creates online redo log files for the standby instance. Cancelable: No Troubleshooting: Check the ORA error messages shown in the progress window. See the Oracle9i Error Messages documentation for more information about the ORA message.
104
105
106
StandbyArchiveDest Property
You must set this property to specify the attributes of the STANDBY_ARCHIVE_DEST parameter. If you do not set this property, the Data Configuration will not function properly. To edit the value of the StandbyArchiveDest property, see Editing a Database Resource. Usage Notes The StandbyArchiveDest property is a critical database property. See Critical Database Resource Properties.
107
StandbyFileManagement Property
You can optionally set this property to update the attributes of the STANDBY_FILE_MANAGEMENT[ AUTO | MANUAL ] parameter setting. Set this property on standby database resources to indicate whether or not the file names on the standby database are the same as those on the primary database. Set to AUTO only if the COMPATIBILITY parameter is set to 9.0.n. To edit the value of the StandbyFileManagement property, see Editing a Database Resource. Usage Notes The StandbyFileManagement property is a noncritical database property. See Noncritical Database Resource Properties.
108
109
110
111