From: "Sean Fitzgerald" Newsgroups: comp.databases.oracle.server References: <3b706dac.1653221296@news.alt.net> Subject: Re: Archiving Redo logs while tablespace is in backup mode. Lines: 12 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Message-ID: Date: Tue, 7 Aug 2001 23:38:37 -0700 NNTP-Posting-Host: 209.142.155.61 X-Complaints-To: abuse@centurytel.net X-Trace: feed.centurytel.net 997242198 209.142.155.61 (Tue, 07 Aug 2001 22:43:18 CDT) NNTP-Posting-Date: Tue, 07 Aug 2001 22:43:18 CDT Organization: CenturyTel.Net You are not quite correct. While the tablespace is in hot backup mode, the change number of the blocks are frozen. Changes are still applied to the blocks and redo is still generated (Oracle does not "save up" all the changes during the backup and then replay them at the end -- otherwise your database query results would be quite stale). At the end of the backup, the change numbers are updated, but the actual row changes have already taken place as they would any other time. The reason the hot backup works is because if you restored the files backed up during the hot backup, the change number would be at the point of the beginning of the backup and then normal recovery with redo logs can take place.