Xref: alice comp.databases.oracle.server:39635 Path: alice!news-feed.fnsi.net!newspump.monmouth.com!newspeer.monmouth.com!newsfeed.corridex.com!hub1.ispnews.com!feed.centuryinter.net!newsread1-mx.centuryinter.net.POSTED!not-for-mail From: "Sean Fitzgerald" Newsgroups: comp.databases.oracle.server References: <36B7B818.3D43B469@bigfoot.com> Subject: Re: shutdown abort & consistent=Y Lines: 10 X-Newsreader: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Message-ID: Date: Tue, 2 Feb 1999 22:23:19 -0500 X-Complaints-To: abuse@centuryinter.net X-Trace: newsread1-mx.centuryinter.net 918012445 209.142.156.134 (Tue, 02 Feb 1999 21:27:25 CDT) NNTP-Posting-Date: Tue, 02 Feb 1999 21:27:25 CDT Organization: CENTURYinter.net you won't lose anything by doing a shutdown abort followed by a startup restrict because upon the startup, oracle does an instance recovery using the online redo logs. This is a safe practice as long as you know what is happening on your database when you shutdown abort. For example, if you shutdown abort while tablespaces are in backup mode then the db will complain (file xyz needs media recovery.....) upon restart and you will need to take each datafile out of backup mode manually in order to open the db.