RE: delayed block cleanout

Hi,
What you are doing is the right (and AFAICR is the only) choice. I might add that if you knew the tables that were modified, then an FTS on only those table would suffice.
- Kirti Deshpande

> -----Original Message-----
> From: Russell Brooks [SMTP:russell.brooks_at_amctechnology.com]
> Sent: Tuesday, February 27, 2001 8:41 AM
> To: Multiple recipients of list ORACLE-L
> Subject: delayed block cleanout
>
> Hi,
> In order to avoid ORA-1555s due to delayed block cleanout during a
> particular conversion, we are running full table scans before the
> conversion. Someone has asked if bouncing the system prior to the
> conversion, which would be much faster, would suffice. I think the
> rollback
> segment entries are already flagged as commited, and the header of the
> data
> blocks would still contain the pointer to the RBS. Even if you bounce the
> system, I think you still get to wait until the next access of the block.
> Does anyone else have an opinion?
>
> Cheers,
> Russ Brooks
> --

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Deshpande, Kirti
  INET: kirti.deshpande_at_verizon.com

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).