| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Proposed Report Server Architecture
Allan,
First thing I think you should consider is the amount of workload that would be placed on this system. Data Warehouse applications can be intensive, but they also can be more sporadic than one would like to consider. We ran a data warehouse at my last location. Early in the morning it would get very busy, but then the rest of the day was almost a 0 load. RAC in this case could be overload. The next thing is to look at what is needed in the data warehouse. Obviously not every thing in your E-Business suite in going to make the transition. This becomes the hard part because end users are almost unanimous in that they "need everything". If this were true then a 2 node RAC for your production system would be the most cost effective, give up on the data warehouse for the moment. Lastly a logical standby isn't your best bet. A totally standalone database with a regular ETL process will do just fine. For what a DW is used for, trend analysis, data 24 hours old fits the bill nicely. If people are saying that they need more current data their not doing trend analysis, their doing real time reactive analysis which has to be done off of the production system.
........................................................................Kanbay <http://www.kanbay.com/>
.............................................................
Dick Goulet, Senior Oracle DBA
45 Bartlett St | Marlborough, MA 01752 USA Tel: 508.573.1978 | Fax: 508.229.2019 | Cell: 508.742.5795
rgoulet_at_kanbay.com <mailto:rgoulet_at_kanbay.com> ........................................................................
.............................................................
On February 8, 2007 Kanbay was acquired by Capgemini, one of the world's
leaders in consulting, technology and outsourcing services, employing
nearly
68,000 people in North America, Europe, and the Asia Pacific region.
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Allan Nelson
Sent: Tuesday, March 27, 2007 10:19 AM
To: oracle-l_at_freelists.org
Subject: Proposed Report Server Architecture
We have been running our reporting tool (Cognos) against our Oracle
E-Business Suite schemas for some years now. This situation is about to
end and I am considering architectures that will lead me to a data
warehouse type environment. What I would like to consider is a logical
standby database running on a Linux based RAC. I'm reluctant to
introduce RAC into my environment without a fairly certain return on
cost and complexity. Could I use one node of the RAC to apply the logs
to while leaving other nodes free for reporting? Would this be a recipe
for trouble given that one node would be updating objects another node
would be querying? Or could I use one node to apply logs, another node
to do ETL in the standby and yet other nodes to report against the
denormalized data?
Some of the criteria that are driving our discussions is the need to get
reporting off production fairly quickly and a readily scalable
architecture. I have heard that RAC is not all that scalable unless
careful consideration is given to the application so that use of the
interconnect is as small as possible. I know this question is very
general but I would appreciate any discussion or pointers to
documentation or presentations.
We will be in a 10gR2 environment when this effort takes off.
Thanks
Allan
-- http://www.freelists.org/webpage/oracle-lReceived on Tue Mar 27 2007 - 10:22:16 CDT
 |
 |