Creation of a physical Standby Database using OEM GC

Transcription

1 Creation of a physical Standby Database using OEM GC Author: Rob Zoeteweij Date: July 19, In this paper I will show how easy it is to create a physical Standby Database. First we will select the Database we want to create the Standby Database for. Select the Availability tab of the Database Home Page Select the Add Standby Database link

2 Select the Add Standby Database link As we want to create a new physical Standby Database, select. Press [Continue] As in this example we don t have any Backup present, we will base our Standby Database on a online Backup, that will be created first and will be used as source

3 Press [Next] We need to enter a Staging Area Location We will indicate that the Staging Area Location might be deleted after creation of the Standby Database Enter the Host Credentials In this example we will use Oracle Managed Files Press [Next]

4 We will name the Standby Database orcl3 and use the File System as Database Storage. Of course if you are using ASM as Storage Manager you would select ASM here. We will select base1.mycorpdomain.com as Host for the Standby Database and use the given Oracle Home as it s Oracle Home Enter the Host Credentials for the Standby Database Host Press [Next] We will use LISTENER as the Listener for the Standby Database, that will use Port 1521 We will orcl3 as the Database Unique Name and the Target name as it will be created in OEM. We need to enter the Standby Archive Location We must use the SYSDBA role to monitor the Standby Database

5 We will use the Data Guard Broker Press [Finish] to start the creation of the Standby Database Next you will see a Progress Indicator showing you the process of Data Guard Configuration creation and submitting the Standby Database creation Job After some minutes the Data Guard Page shows up indicating that the creation of the Standby Database is in progress. After creation is completed the following Page will be shown

6 As we can see orcl3 now functions as a Standby Database Let s take a close look to both of the databases now orcl1.base1.mycorpdomain.com is now functioning as in the Primary Database role. orcl3.base1.mycorpdomain.com has been created and is the role of Standby Database. As you can see the Database Home Page for orcl1 also shows the Primary Role of the database Let s now select the High Availability Console

7 The Console now includes the Data Guard Summary, information on the Standby Database and the Primary Database Redo Rate When selecting the Data Guard link from the Database Home Page, the Data Guard Page is displayed This page shows detailed information on the Standby Database Progress in terms of Transport Lag and Apply Lag. Notice the [Switchover] and [Failover] Buttons Let s perform a Switchover, meaning that the Primary and Standby Roles will be switched. This will result in orcl1 being the Standby Database and orcl3 begin the Primary Database. Now press the [Switchover] Button

8 The Confirmation Page allows us to do the following: We will choose to swap the Monitoring Settings. This means that all Metrics and Thresholds that were set for orcl1, will be switched with the Metrics and Threshold settings or orcl3. This makes sense, knowing that both Primary and Standby Databases are not equally opened and several Metrics that do apply to a Primary Role Database will not apply to a Standby Role Database. We will choose to Transfer Jobs As we can see there is one Jobs scheduled for orcl1, which we would like to run on orcl3 as soon as the Roles are switched. We will now press the [Yes] Button. Next a progress Page will show you all actions being performed during the switchover. After the switchover is completed the following page is shown:

9 As expected, orcl3 now is the Primary Database and orcl1 the Standby Database.