What is our primary use case?
We have a primary database and a secondary database. Both databases are on different sites, which are geographically distant. One site is used as the primary site, and the other one is used as the secondary site. We have configured Oracle Data Guard to instantly replicate the data from one database to the other database on a different site. That's what we do with the Oracle Data Guard at this point. It's about business continuity.
What is most valuable?
We have found the replication feature the most useful. We use this feature the most.
The ability to recover a database with less effort and the use of Oracle Data Guard Broker to administer the complete environment are also very useful features.
What needs improvement?
One thing that can be improved is the GUI. It would be good to have a very nice GUI to easily configure and administer, providing different presentations to the database administrator.
The feature that can be included is the integration with third-party monitoring systems, that is, monitoring systems from other vendors, not only from Oracle.
For how long have I used the solution?
We have been using Oracle Data Guard since 2010. Currently, we are using the latest version.
What do I think about the stability of the solution?
We didn't have any incidents that caused any major problems with this implementation. There aren't any concerns regarding the stability of this solution.
Once implemented, we can administer the whole environment with no downtime. We can switch over between sites and keep on using Oracle Data Guard like this. Until now, there aren't many things to do. It has been very good. That's why we keep on using this solution.
What do I think about the scalability of the solution?
It was a good experience when we had to replicate it to more than one database and use it for new database creations and all such things. It was very simple, and until now, there are not many problems or gaps in the usability of this solution. It works very well.
How are customer service and technical support?
We didn't have many problems and much experience with technical support.
Once implemented, we only have to monitor and take care of the gaps in the solution. Most of them happen because of the connectivity, either bandwidth or something else, or because of the growth of the database or the data being migrated from one database to another.
How was the initial setup?
The initial setup was quite complex, but it was because of a different implementation approach. It's not so complex as such.
When it was the manual version 9, we migrated it to version 11, and now we migrated again to version 19, which is a different approach for implementing it. In the beginning, it was new and quite complex, but not so much to be done later.
What other advice do I have?
It's mandatory in order to be ready for any incident when someone has a similar environment.
When we talk about Oracle, we are talking about the venue database, translation of database, online translation of database, and atomic translations. When we need to guarantee the stability of the database, we have to be careful.
In financial enterprises that use Oracle as a secure relational database management system, the data that you have is very important, and it is the asset that brings the most value to the company. I would recommend that every implementation that goes to the production environment must be done together with Oracle Data Guard. Even small databases can be powered by this solution.
I would rate Oracle Data Guard a nine out of ten. During all these times and all these years, if I can count the number of times that we had to intervene or we had to do something by ourselves, I can't count more than three times.
Which deployment model are you using for this solution?
Which version of this solution are you currently using?