Sebastian Solbach (DBA Community) wrote:
Buy Enterprise Edition.....
Because of license prices customer even dont want Enterprise edition and customer wants high availability. Same situation i went across.
Then manual standby is only option,
If OP is going for third party like "Dbvisit" of course there are several features available and which can do very quick and even i also prefer to go enterprise edition. so that along with Data Guard of course we can use more features like advisors so on.. :)
this sounds like: I have a very important database, which my business is totally dependend on. It needs high availability and reliability - but I don't want to spend money for it.
Sorry... this I really cannot understand....
Also make sure the customer knows the implication of using dbvisit. DBVisit is based on archive redologs (same as manual standby mechanism). So he will definitely loose some transactions in failover case.
There is no Zero Data Loss.
Furthermore make sure you are not using STANDBY_FILE_MANAGEMENT set to auto. This is Enterprise Edition functionality.
I personally would look on other options to save costs: Like using an Oracle database appliance, where I can reduce license costs by disabling cores. This may enable the customer to use EE (with only minor investment).
You can still do a good old fashioned STANDBY database in SE. You just might need to code some of the things like log shipping yourself where as of course DG automates that.
I'd go with STANDBY database. Shareplex is costly and complicated. As is GoldenGate.
You don't need any third party tool. Give google a search string such as oracle+manual+standby and you will find many articles describing how to set it up and scripts for automation.
And (unlike Sebastian) I agree with you completely on licencing: there are many cases where a Sandard Edition 1 licence for USD5800 per CPU makes a lot more sense than an Enterprise Edition licence at USD47500 for every two cores (depending on the core licencing factor). Do that arirthmetic when your server has a SPARC T4 8core CPU, and EE is often not possible.
Edited by: JohnWatson on Jan 24, 2013 9:22 AM
I just noticed that you mentioned a problem being archive logs on ASM. No problem: in SE, you are allowed to have two destinations. So set log_archive_duplex_dest to a file system directory.