We have a couple of Oracle systems that are attached to different types of applications.
In terms of Data Guard, we use it for factory monitoring.
We like Oracle because the solution is very robust. It's also efficient for queries and is easy to scale.
The database administration needs improvement. With Oracle, we have a lot of features for administrating data, but it might be too many. It needs to be simplified. It should be automated. Looking at Enterprise Manager, there are too many KPIs in place. Directly on-site, we do not need to choose all of them. Administration, generally speaking, needs to be improved.
Oracle should also continue to simplify the upgrade using Data Guard. We have already seen reduced outage timing any time we are doing upgrade, so maybe they are heading in that direction, but it can always be improved.
I've been using the solution for more than 10 years.
The stability of the solution is good.
The scalability of the solution is good. We have roughly 1,000 users right now.
Technical support is very good. If at any time we write a ticket, we get the appropriate answer on time.
The set is straightforward but it is dependent on the audience you have. Internally, we have experienced DBAs, so deploying Oracle is straightforward. If we had to do the same job for an external company it could be complex.
Previously we were doing the set up ourselves. Now, for more than a decade, we work with a third party, and we delegate the deployment, the support, and the maintenance of the Oracle Database.
The pricing of Oracle is average. It's not inexpensive but it's okay.
Currently, we are using the on-premise version on the solution.
I would rate this solution eight out of ten. I would recommend the solution because it is a good product and it's working fine. But I'm not sure if it's suitable for every consideration or any environment.
I don't quite agree with "you have to keep monitoring the system all the time". Monitoring is just part of any Oracle database or system. You implement monitoring of your databases with Cloud Control and that automatically includes Data Guard monitoring. If you define your monitoring templates and incident rules in Cloud Control appropriately, the monitoring work will all be done by Oracle, not you. You can configure Cloud Control to send a mail to you whenever there a Data Guard problem, or have an incident created, or have a text sent to DBA team, or a corrective action fired, etc. Monitoring should not be a burden! However, troubleshooting DG whenever there is a problem can be more tricky. But most of time a simple "disable configuration; enable configuration;" solves synchronization problems.
We created an interactive script to create a Data Guard. Therefore, the time required to create a DG is roughly the time needed to clone the primary database. The script does everything, including changing files tnsnames.ora, listener.ora, etc. Invest some time in scripting and creating Data Guard databases will become as easy as creating a standalone database.