Re: Best practices for Datawarehouse: RAC or Non-RAC
From: Stefano Cislaghi <s.cislaghi_at_gmail.com>
Date: Wed, 17 Mar 2010 20:17:51 +0100
Message-ID: <d06f0d321003171217j14138049y23b5f1075e69281f_at_mail.gmail.com>
Hello,
Date: Wed, 17 Mar 2010 20:17:51 +0100
Message-ID: <d06f0d321003171217j14138049y23b5f1075e69281f_at_mail.gmail.com>
Hello,
Sure RAC may work well in a datawarehouse system, but you have IMHO to check your apps and jobs if are able to work in a RAC database. Also if you use legacy applications check with your vendor if there're known issues with RAC or not.
RAC address many misconceptions and it's vital for you to know really
well what you're doing in your env.
Check this doc:
http://orainternals.files.wordpress.com/2008/03/riyaj_battle_of_nodes_rac_perf_myths_doc.pdf
Ste
-- http://www.stefanocislaghi.eu 2010/3/17 Ravi Gaur <ravigaur1_at_gmail.com>:Received on Wed Mar 17 2010 - 14:17:51 CDT
> I'm sure this topic has been brought up several times before. I'm looking
> for some documentation /advice for building a new Datawarehouse. It will
> have the nightly ETL feeds, denormalization, long running queries etc. so
> I'm looking for some best practices if someone can point me to. Specifically
> any down-sides of using RAC.
> Our hardware is Sun (sun-fire-v495's which will eventually move to T5440s).
> The OLTP databases that will feed this are a mix of RAC and non-RAC
> databases (if that matters).
>
> TIA,
>
> - Ravi Gaur
>
-- http://www.freelists.org/webpage/oracle-l