Re: Concurrency for resources by several instances on one host

"Howard J. Rogers" wrote:

> Should be, actually. Oracle's recommendation (and never mind the licensing
> fees) is that there should be one App.-one Database-one Server. Anything
> else is a compromise.

Unless things have changed, Oracle used to recommend 1 server = 1 instance. But many apps within that instance specifically so you could get resource management. The resource management extends a long way past Resource Manager as well, deep into the OS and Disk substructure.

> If the bun-fight is really as bad as you make it sound, then I was idly
> speculating that consolidating both databases into one, and then going
> hell-for-leather with Resource Manager might be your best go.

This is usually the first thing I consider these days. IMHO, a new instance is always more expensive to set up than a decent consolidation algorithm, esp. when you start adding in the extra security, backup/reco, memory, os-tuning, disk alloc, etc., etc., etc.

in fact, i've never really understood the typical dba's gut reaction to equate 1 instance to 1 app. (putting on flame-proof suit <g>) there are times & reasons for not consolidating, yes - but generally i think consolidation should be the first option considered

However, back to the question at hand ......

In this case the OLTP vs DW tx mix might cause me to rethink that suggestion. Careful eval required ...

As a side thought - are there other ways of improving the Data Mining system? Eg: are the mining tools run on that machine? (are you using Darwin or other Oracle minimg tools?) Can the tools be run on another server, just fetching the data fro this one? Can the algorithms take advantage of Summaries? Is it feasible to subset based on the algorithms? is this as 24x7 or could the mining be shifted off-hours? can the minimg be trialled during daytime, followed by a real run overnight? Received on Sun May 11 2003 - 23:27:14 CDT