In addition, if running in Archivelog mode, check if the archive log
destination is getting full, and, if automated, if any, process of emptying
it is not keeping up with log generations.
> -----Original Message-----
> From: Sandeep Dubey [SMTP:sandeep.dubey_at_induscorp.com]
> Sent: Monday, June 26, 2000 11:50 AM
> To: Multiple recipients of list ORACLE-L
> Subject: RE: Slow delete
>
> Dave
>
> Could be any of these or other reasons.
>
> 1. table could be heavily indexed.
> 2.You are deleting a master table referenceing other child table with
> foreign key with on delete cascade which is deleting other tables data.
> 3. Rollback segement may be a bottle neck too.
>
> Sandeep
>
>
>
> -----Original Message-----
> Sent: Monday, June 26, 2000 11:11 AM
> To: Multiple recipients of list ORACLE-L
>
>
> Any idea why a delete of all the rows in a table might take hours when
> there
> are only 30,000 rows? There are no other users on the system. Rowlength is
> about 120.
>
>
> Dave Turner
>
> --
>
> Dave Turner, Senior Database Administrator, Linuxcare, Inc.
>
> 913.383.3052 tel, 913.579.3803 cel, 913.652.0687 fax, 877.443.9553 pager
>
> dturner@linuxcare.com, http://www.linuxcare.com/
> <http://www.linuxcare.com/>
>
> Linuxcare. Support for the revolution.
Received on Mon Jun 26 2000 - 11:24:14 CDT
