Use Grid Control to quickly deploy Oracle physical Data Guard

Use Grid Control to quickly deploy Oracle physical Data Guard

Grid Control (GC in this article) is a good helper for monitoring and managing databases, and also a double-edged sword. If you are proficient in applications, You can greatly improve the efficiency of database management and maintenance. Otherwise, if you do not fully grasp the hidden details, it is easy to cause unnecessary troubles and faults. This article demonstrates how to use Grid Control to quickly deploy Oracle physical tracing uard. For reference.

1. log on to GC and click Targets-Databases.
At this point, we can see two Oracle database instances managed by GC. secdb instances are physical primary uard master database instances, and secgc is the database instance corresponding to the GC tool.


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


3. Click "Maintenance" To Go To The secdb instance Maintenance page.
On the right side, we can find Data Guard and click "Setup and Manage" under Data Guard ".


4. In this case, you need to provide the management user and password information. click Login


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


6. Keep the default first option and click "Continue ".


7. Keep the default first option unchanged. click Next.
Now we have entered the step-by-step configuration phase. Because no backup media is available before, we choose to generate a backup here.


8. You need to provide the Directory and backup options for storing backup media.
Specify the backup directory as "/home/oracle ";
In order to save space, the corresponding backup time will also increase;
Retain the backup media as needed.


9. location where the physical Data Guard is stored
The instance name of the physical Data Guard is specified as secdg;
Enter the oracle user name and password;
In this configuration, the newly deployed slave database and master database are both on the host secdb1.


10. File ing
This step is critical, and countless people fall here.
Click Next to go to the Next step. Click Customize to Customize the file directory. Otherwise, the standby_file_management parameter will be set to "MANUAL", db_file_name_convert, and log_file_name_convert. If the backup database of the data file is added to the master database, it cannot be restored normally, for the case analysis of this fault, see [fault uard] fault analysis that data files cannot be added due to improper configuration of slave database parameters (http://space.itpub.net/519536/viewspace-670703 ).


11. By default, data files, temporary files, log files, and control files are created in the following three paths:
Is there a feeling of dumpness that the content of these paths needs to be adjusted urgently.






12. For ease of use, we specify the files corresponding to all databases to "/u01/app/oracle/oradata/secdg"
Note: it is not enough to provide a path. You must click "Go" next to the path ". Only in this way will the given path name be applied, otherwise it will not help.
1) make sure the changes are complete and then click "OK ".


2) Click OK and you will receive the following reminder. This warning message is generated because the specified directory is not created in advance. Click Yes and the system will automatically create it.


3) return to the File Locations interface again. Nothing seems to have happened, but everything has changed. Click Next to continue.


13. On the configuration page, you must provide the Unique Name, Target Name, and Standby archive path information of the slave database.
1) modify according to the content in the figure and click Next.


2) The warning information here is also caused by the absence of the configured Standby archive path. Click Yes to allow the system to automatically create the archive path.


14. This is the Review phase configured for the previous steps.
1) carefully check whether the basic parameter information of the master and slave databases is correct


2) check whether the correspondence between the data files, temporary files, log files, and control files of the master and slave databases is correct. After confirming everything is correct, click Finish. Then, the automatic creation process is automatically triggered.


15. The following describes how GC automatically creates a physical Data Guard. If the configuration is correct, a fresh physical Data Guard will be displayed in front of the world.
1) initialize the Job for subsequent automatic creation


2) automatically create a Job and run it in the background. Click "Creation in progress" to track the entire Job running process.


3) Overall Operation


4) Details and progress of each step


5) at this time, the creation of the entire physical Data Guard has been completed.
The total duration is 369 seconds, less than 7 minutes.


6) The Job status is "Succeeded" and created successfully.


16. Finally, you can see the information of the successfully added secdg instance on the Targets-Databases interface, which is the physical Data Guard database of secdb.


17. Summary
If everything goes well, it takes about 10 minutes to use Grid Control to create a physical Data Guard. At the same time, this method also hides a lot of implementation details, so it is not easy to understand the operating principles of Data Guard. We recommend that you use the Script Creation principle as a supplement to GC creation to explore the mysteries of Data Guard.

Cross-platform database migration using Oracle Data Guard