John Kanagaraj
ds.com> cc:
Sent by: Subject: RE: dire
cc:
Sent by: Subject: RE: direct path read waits
[EMA
John Kanagaraj
ds.com> cc:
Sent by: Subject: RE: dire
Babu,
You:
> All the tablespaces are on different disks - Sorry I should
> have mentioned
> this in the original post itself...
Me:
> Your answer was buried in the question itself. If the TEMP
> tablespace had to contend with Tablespace C on the same 'disk' then such a
result is
> expected.
Not
Babu,
Did you run each scenario more than once to make sure it is not an anomaly?
Henry
-Original Message-
[EMAIL PROTECTED]
Sent: Thursday, February 20, 2003 2:41 PM
To: Multiple recipients of list ORACLE-L
All
We are doing some performance testing while moving from one server to
ano
garaj
ds.com> cc:
Sent by: Subject: RE: direct path
read waits
[EMAIL PROTECTED]
02/20/03
cc:
Sent by: Subject: RE: direct path read waits
[EMAIL PROTEC
Tablespace C is on the I/O path as TEMP tablespace maybe???
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 20, 2003 1:41 PM
> To: Multiple recipients of list ORACLE-L
> Subject: direct path read waits
>
>
&g
ple recipients of list ORACLE-L
> Subject: direct path read waits
>
>
> All
>
> We are doing some performance testing while moving from one server to
> another. I was trying to time some index rebuilds and noticed
> something
> that I cant explain.
>
> I am rebuild
Babu
When building an index, there are 3 (at least) tablespaces that matter:
1. Table tablespace
2. Temp tablespace for sorting
3. Index tablespace (could be the same as the table tablespace)
Ideally you will have all 3 on separate devices. I suspect for your test
cases that sometime
All
We are doing some performance testing while moving from one server to
another. I was trying to time some index rebuilds and noticed something
that I cant explain.
I am rebuilding an index on a 1 million row table. Lets say its on
tablespace A and when I rebuild it to tablespace B it does in
11 matches
Mail list logo
