If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

increasing ram to counter slow query

2) even with more ram, one still need to configure , ie, the shared pool, data buffer,redo buffer in order to take advantage of this increase in memory?

3) anyway, i think the crux is not the hardware but rather the examiniation of the slowness. Without the latter, my management went straight away to getting more ram. A more realistic method will be getting more CPUs instead.

You could maybe try analyzing your database on a regular basis too. This has had a dramatic effect on a couple of our applications. There may be other tools available to investigate at the OS level, but what OS is it?

If I have to choose between two evils, I always like to choose the one I haven't tried yet.

2) even with more ram, one still need to configure , ie, the shared pool, data buffer,redo buffer in order to take advantage of this increase in memory?

Unless you have paging/swapping problems.

3) anyway, i think the crux is not the hardware but rather the examiniation of the slowness. Without the latter, my management went straight away to getting more ram. A more realistic method will be getting more CPUs instead.

How so? If you don't know what the problem is how can you suggest more hardware?

I can't believe that I'm the first to say "statspack"! world's smnallest hooray for me.

But anyway, get statspack running for a fifteen minute interval when the database appears to be under pressure, then pull the top SQL's from it. You could easily have a handful of badly tuned SQL in there that is the source of 90% of your problems.