Re: Huge generation of archivelog: how to tweak that ?
From: ca111026 <ca111026_at_gmail.com>
Date: Mon, 3 Aug 2009 22:47:45 -0700 (PDT)
Message-ID: <41ff5a21-fcba-40de-a333-89e79db5e1b9_at_v23g2000pro.googlegroups.com>
Because "purge" means DELETE and DELETE is quite inefficient - it deletes records one-by-one.
If a table has indexes it also needs to delete all index entries. I don't think there is a silver bullet for this situation, you just need more disk space for keeping archivelog files. Received on Tue Aug 04 2009 - 00:47:45 CDT
Date: Mon, 3 Aug 2009 22:47:45 -0700 (PDT)
Message-ID: <41ff5a21-fcba-40de-a333-89e79db5e1b9_at_v23g2000pro.googlegroups.com>
Because "purge" means DELETE and DELETE is quite inefficient - it deletes records one-by-one.
If a table has indexes it also needs to delete all index entries. I don't think there is a silver bullet for this situation, you just need more disk space for keeping archivelog files. Received on Tue Aug 04 2009 - 00:47:45 CDT