Hi, For me it depends on what is expected from the DR environment. If management is fully aware that it will only will allow to run in a somewhat restricted way, I don't have much problem in using lesser hardware for a DR site. Just make sure you have a paper trail confirming their awareness ;-) I have seen the combination exadata primary - oda standby being proposed before, with virtualization enabled on the ODA Reason behind is is that you can run on a minimal set of CPU's activated on the standby site and only activate the rest when doing a failover. As the primary site at that point no longer exists, you could argue that you don't need additional db licenses. (Now, that is something I would like to see confirmed in writing from Oracle LMS ;-) ) Kind regards, -- Freek D'Hooge Exitas NV Senior Oracle DBA email: freek.dhooge@xxxxxxxxx tel +32(03) 443 12 38 http://www.exitas.be On di, 2014-04-15 at 19:40 +0200, Martin Bach wrote: > Hello all, > > This is an interesting thread! > > I think an important point is missing here though. Exadata, especially > since 11.2.3.3.0, will make very elegant choices when it comes to > caching data in the Smart Flash Cache. You will see very decent > response times. You will also notice that smart scans will benefit > from intelligent caching. This works so well that I had to rewrite > some of my demos. > > Those features do not exist outside the Exadata platform. Outside of > Exadata you get no smart IO either, so when you are in the > uncomfortable position where you actually have to invoke DR you could > well be in trouble because your DR site does not perform adequately. > And there is more hidden trouble like for example IORM you can't have > outside of Exadata... > > Not using identical hardware for DR is a risk in my opinion. The OPs > question is similar in concept to reusing your old production kit for > DR. It too might work while in the standby role, but will cost likely > not support the production workload (it is the old kit for a reason). > > Hope this helps, > > Martin