Rapid Deployment of Oracle Physical Data Guard Using Grid Control

[Date: 2016-04-18]

Source: Linux Community Author: secooler

Grid Control (referred to as GC in the text) is a good helper for monitoring and managing databases, and it is also a double-edged sword. If you can "proficiently" the application, you can greatly improve the efficiency of database management and maintenance; on the contrary, if you don't have a comprehensive grasp of its implied details, it is easy to bring unnecessary troubles and failures. This article shows you the detailed process of using Grid Control to quickly deploy Oracle physical DataGuard through practical operations. for reference.

1. Log in to the GC, click Targets - Databases in turn, and
you can see two Oracle database instances managed by the GC. The secdb instance is the physical DataGuard master database instance, and secgc is the database instance corresponding to the GC tool.

2. Click the secdb instance to enter the Home page of the secdb instance

3. Click "Maintenance" to enter the maintenance page of the secdb instance
On the right side, we can find Data Guard, and click "Setup and Manage" under Data Guard.

4. At this point, you need to provide management user and password information, click Login

5. Click "Add Standby Database"
This page gives the advantages of using GC to create and manage Data Guard.

6. Keep the default first option, click Continue

7. Keep the default first option unchanged, click Next, you
have entered the step-by-step configuration stage, because no backup media is available before, so here we Select Generate Backup.

8. Here you need to provide the directory where the backup media is stored and backup options. The
backup directory is specified as "/home/oracle";
In order to save space and choose to compress the backup, the corresponding backup time will also be increased;
keep the backup media for emergencies.

9. Give the location where the
physical Data Guard is stored. The instance name of the physical Data Guard is specified here as secdg;
enter the oracle user name and password;
under this configuration, the newly deployed standby database and the main database are on the host secdb1.

10. Give the file correspondence
This step is very critical, and countless people with lofty ideals have fallen here.
Don't rush to click Next to go to the next link, we need to click Customize to customize the file directory. Otherwise, the standby_file_management parameter will be "MANUAL", and the db_file_name_convert and log_file_name_convert parameters will be empty. When the main database adds data files to the backup database, the backup database will not be able to recover normally. For the case analysis of this failure, please refer to "[DataGuard] The data file fails due to improper parameter settings of the backup database. Added Failure Analysis" (http://space.itpub.net/519536/viewspace-670703).

11. By default, the creation paths of data files, temporary files, log files and control files are shown in the following three figures.
Do you feel dumbfounded that the content of these paths needs to be adjusted urgently.

12. For simplicity, we assign all the files corresponding to the database to "/u01/app/oracle/oradata/secdg"
Note: It is not enough to simply give the path, you must click "Go" behind the path. Only then will the given pathname actually be applied, otherwise it will not help.
1) Modify one by one, make sure that the modification is complete and click "OK".

2) After clicking OK, you will receive the following reminder message. This warning message is caused by the fact that the directory we specified has not been created in advance. Click Yes and the system will create it automatically.

3) Going back to the File Locations interface, nothing seems to have happened, but everything has changed. Click Next to continue.

13. The configuration interface needs to give the Unique Name, Target Name and Standby archive path information of the standby database
1) Modify according to the content in the figure, and click Next after modification.

2) The warning message here is also caused by the fact that the set Standby archive path does not exist. Click Yes to let the system create it automatically.

14. This is the Review stage of the configuration of the previous steps
1) Double check whether the basic parameter information of the active and

standby databases is correct 2) Double check whether the corresponding relationship between the data files, temporary files, log files and control files of the active and standby databases is adjusted correctly. . After everything is confirmed, click Finish, and then it will enter the unattended automatic creation stage.

15. The following is the process by which GC automatically creates a physical Data Guard. If there is no problem with the previous configuration, after a while, a live physical Data Guard will appear in front of the world.
1) Initialize the job for subsequent automatic creation

2) Automatically create the job to run automatically in the background, at this time, you can click "Creation in progress" to track the running process of the entire job

3) The overall operation status

4) The details of the operation of each step and Progress

5) At this point, the creation of the entire physical Data Guard has been completed in
a total time of 369 seconds, less than 7 minutes.

6) At this time, the status of the Job has been displayed as "Succeeded", and the creation is successful.

16. Finally, the information of the successfully added secdg instance can be seen from the Targets - Databases interface, which is the physical Data Guard database of secdb.

17. Summary
If all goes well, it only takes about 10 minutes to create a physical Data Guard using Grid Control, which is amazingly fast. While being convenient, this method also hides many implementation details, making it inconvenient to deeply understand the operating principle of Data Guard. It is recommended to explore the mysteries of Data Guard based on the principle of script creation as the main GC creation.