Please review Note #147474.1 on Metalink.

Unrecoverable and nologging options are used to stop redo log generation in
a some specific operations.

To control use of Rollback segments, committing rows at some interval would
help.

In this case, one will need to write a PL/SQL loop to count deletions and
then commit.

HTH,

- Kirti


-----Original Message-----
From: Pfaff, Jody [mailto:jody.[Email Address Removed] Friday, June 28, 2002 1:31 PM
To: LazyDBA.com Discussion
Subject: Rollback Segment and Commit



Depending on your Oracle version...

You may have to use...delete from <table> nologging where <condition>;

I guess they think that sounds less damaging.

Jody


-----Original Message-----
From: Wayne Scotchmer [mailto:[Email Address Removed] Friday, June 28, 2002 5:14 PM
To: LazyDBA.com Discussion
Subject: RE: Rollback Segment and Commit


Try

delete from <table> unrecoverable where <condition>

Thanks.
__________________________________
Wayne Scotchmer
Implementation Consultant
North Plains Systems Corp.

P: 905.565.1900
F: 905.565.1978
[Email Address Removed] Message-----
From: Derrick Pitts [mailto:[Email Address Removed] Friday, June 28, 2002 11:05 AM
To: LazyDBA.com Discussion
Subject: Rollback Segment and Commit


Gurus,

I'm trying to delete about 400,000 rows from a table.
When 1 run my SQL statement I receive an error message
about the rollback segments not able to extend. I did
a commit.

Does anyone know of a way to commit after so many
records have been deleted?



Oracle LazyDBA home page