Path: news.easynews.com!easynews!news.he.net!news-hog.berkeley.edu!ucberkeley!newsfeed.stanford.edu!sn-xit-01!sn-post-01!supernews.com!corp.supernews.com!not-for-mail From: Sybrand Bakker Newsgroups: comp.databases.oracle.server Subject: Re: Effect of NOLOGGING tablespace on hot backup Date: Thu, 06 Jun 2002 20:47:29 +0200 Organization: Posted via Supernews, http://www.supernews.com Message-ID: <0gbvfust155m9de2gu002ups7ve27mn9k9@4ax.com> Reply-To: postbus@sybrandb.demon-verwijderdit.nl References: <59dd9910.0206061024.318d582c@posting.google.com> X-Newsreader: Forte Agent 1.91/32.564 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: newsabuse@supernews.com Lines: 23 Xref: easynews comp.databases.oracle.server:149775 X-Received-Date: Thu, 06 Jun 2002 11:43:48 MST (news.easynews.com) On 6 Jun 2002 11:24:50 -0700, jennifer.corliss@roche.com (Jenn) wrote: >If I have a tablespace that is marked NOLOGGING and I do a hot backup, >what do I get back when I recover? > >1. Nothing >2. Objects as of the time of the backup with no ability to roll >forward through the logs >3. Everything >4. something else? > >Thanks, Jenn The impact of NOLOGGING has been discussed and explained many times here. Please note this group has archives and they are searchable via http://groups.google.com Hth Sybrand Bakker, Senior Oracle DBA To reply remove -verwijderdit from my e-mail address