disk bottleneck?

[Bill Hassell]

With some legacy SAL, are you running 32bit Oracle? If so, you need to maximize the SGA but like the old (inefficient?) SQL, 32bit programs are crippled by a small address space. You can use a memory window to separate all the other shared memory (and shared libraries and memory mapped files) into their own map and give your DBA up to 1750 megs for SGA. This will allow row insertions in memory and temp sort tasks can take place without using a temp disk file.

To allow the Oracle program(s) that access SGA to address a larger space (default is maxed at 960 megs). Look at the white papers for process and memory management found in /usr/share/doc (11.11 users will have to go to www.docs.hp.com for these papers).

[doug mielke]

Thanks all for the help. I'll change the time slice, and decrease the cache.

I think we're near our SGA limit on 32 bit Oracle Apps. at 1.7 gig. I'll be looking for a way to increase that, either with a dbase upgrade or some memory management tricks.