>From what I have read, a full table scan may be necessary to initiate block cleanout in a VLDB to prevent ORA-01555 errors due to delayed block cleanout. However, if the full table scan itself falls victim to the ORA-01555 error, how does one guarantee that all the blocks in the table are visited?--keep running the FTS query? The parameter delayed_logging_block_cleanout is not an option as it is no longer available in my DB (8.1.7.2 comp=8.1.6.3).
Thanks. -w __________________________________________________ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.yahoo.com -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Walter K INET: [EMAIL PROTECTED] 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: [EMAIL PROTECTED] (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).
