Would you post the parameter file ??
Huge Buffer, commit=y, direct=y, assigning the big rollback segment should
help you to have faster export ,
and also you can have a look at the DISK I/O stats ( verify the OFA is same
on both the boxes ).
Thanks,
Madhu
-Original Message-
Sent: Monday
On Mon, 20 May 2002, Reddy, Madhusudana wrote:
> Huge Buffer, commit=y, direct=y, assigning the big rollback segment
> should help you to have faster export ,
What do you mean "assigning the big rollback segment?" How do you do
that to an export and what does it accomplish?
What does COMMIT=Y
--- Jeremiah Wilton <[EMAIL PROTECTED]> wrote:
> On Mon, 20 May 2002, Reddy, Madhusudana wrote:
>
> > Huge Buffer, commit=y, direct=y, assigning the big rollback segment
> > should help you to have faster export ,
>
> What does COMMIT=Y do in an export?
it causes an error message!
___
The idea of huge rollback segment is just to eliminate the contention the
rollback segment. Well its not always applicable ( possible make sure all
the other applications are not used), but we can create a big rollback
segment and bring it on line and make other rollback segments offline, and
run
On Mon, 20 May 2002, Reddy, Madhusudana wrote:
> The idea of huge rollback segment is just to eliminate the contention the
> rollback segment. Well its not always applicable ( possible make sure all
> the other applications are not used), but we can create a big rollback
> segment and bring it on
If an expert is done with consistent = 'N' it still must preserve some information.
In the beginning export runs some selects against the data dictionary and needs that
data to be consistent throughout the export. If that data changes then it needs to be
reconstructed from the undo generate
:RE: What makes Export slow ?
On Mon, 20 May 2002, Reddy, Madhusudana wrote:
> Huge Buffer, commit=y, direct=y, assigning the big rollback segment
> should help you to have faster export ,
What do you mean "assigning the big rollback segment?" How do you do
that to an export