Re: tunning an index built

2003-09-18 Thread Craig Munday
Hi, How many CPUs do you have on your machine? I assume not 32 - perhaps reducing the degree of parallelism might help (less is sometimes more). How much memory do you have on your machine? I suggest fixing your virtual memory paging problem first - do this by resizing areas like the buffer

Re: tunning an index built

2003-09-18 Thread Mark Richard
: Sent by: Subject: Re: tunning an index built [EMAIL PROTECTED

RE: tunning an index built

2003-07-10 Thread Niall Litchfield
Hi all. Thanks to all who replied. I'm still trying to speed the things up and wondering whether someone can explain what is paging to file system is referring to? Does this indicate that I don't have enough memory? Is it related to reads? Anything else? Yes it does relate to a lack of

Re: tunning an index built

2003-07-09 Thread zhu chao
Hi, First of all, you should use nologging. This helps a lot. Second, when using parallel clause, the sort_area_size of the ora_pxxx size is not the sort_area_size of your session, it is the instance's default size, when it is started. I have verified it. So if you want to

Re: tunning an index built

2003-07-09 Thread Kirtikumar Deshpande
When using parallelization with higher values for S_A_S, keep in mind that *each* PQ slave will potentially use that much memory for sorting. Should this sorting use disk, it would cause even more direct i/o to temp tablespace. Parallelization can very easily paralyze you system ;) Also,

Re: tunning an index built

2003-07-09 Thread Gurelei
Hi all. Thanks to all who replied. I'm still trying to speed the things up and wondering whether someone can explain what is paging to file system is referring to? Does this indicate that I don't have enough memory? Is it related to reads? Anything else? thanks --- zhu chao [EMAIL PROTECTED]

RE: tunning an index built

2003-07-08 Thread John Kanagaraj
How about Sort_area_size? This will matter - check for 'sorts to disk' and 'sort rows' from that session's v$sesstat (joined to v$statname). John Kanagaraj Oracle Applications DBA DBSoft Inc (W): 408-970-7002 Grace - Getting something we don't deserve; Mercy - NOT getting something we deserve

RE: tunning an index built

2003-07-08 Thread Kevin Toepke
what is your sort_area_size? Try changing it to something huge (say 200MB)for the session... alter session set sort_area_size = 2; Kevin -Original Message- Sent: Tuesday, July 08, 2003 5:30 PM To: Multiple recipients of list ORACLE-L Hi. I'm trying to tune an index build.

RE: tunning an index built

2003-07-08 Thread Gurelei
I had it set to 50M. I'll try 200M tonight. thanks Gene --- Kevin Toepke [EMAIL PROTECTED] wrote: what is your sort_area_size? Try changing it to something huge (say 200MB)for the session... alter session set sort_area_size = 2; Kevin -Original Message- Sent:

RE: tunning an index built

2003-07-08 Thread Gurelei
Sort_area_size is set to 50M for this session. almost 16000 sotrs in memory vs 23 sotrs on disk Gene --- John Kanagaraj [EMAIL PROTECTED] wrote: How about Sort_area_size? This will matter - check for 'sorts to disk' and 'sort rows' from that session's v$sesstat (joined to v$statname). John

Re: tunning an index built

2003-07-08 Thread Mladen Gogala
DB Cache doesn't help you. IO waits mean that oracle processes are waiting to complete I/O requests. The I/O waits usually come with arguments like P1TEXT,P1,P2TEXT,P2,P3TEXT and P3 which can help you in locating file and block that the oracle processes are waiting for. Move those files and blocks