Re: sgadef.dbf file after Unix m/c crash

Naren Chintala wrote:
>
> Keith,
>
> The sgadefsid.dbf file has to be removed manually IF it is left behind after
> the instance startup fails or is shutdown abnormally. This is documented in the
> Installation and User's Guide (refer the index for sgadefsid.dbf,recovery).
>
> You can also use the startup command with the FORCE option which removes this
> file before starting the instance.
>
> ex. startup pfile=initSID.ora force
>
> Naren Chintala
> AT&T
> naren_at_mink.att.com
>
> ---------------------------------------------------------------
>
> From: keith_at_keithd.demon.co.uk (Keith Davies)
> Newsgroups: comp.databases.oracle
> Subject: sgadef.dbf file after Unix m/c crash
> Date: Sat, 18 May 1996 08:43:17 +0100
> Organization: Dis
> Message-ID: <ADC33E25966822997_at_keithd.demon.co.uk>
>
> When a Unix machine crashes the Oracle instances leave behind sgadef.dbf
> files which we delete to allow the instances to be restarted. Is this the
> best way of doing this? I have never seen this described in Oracle
> documentation.
>
> Keith

This would have been a problem in Version 5.x.x.x.x of Oracles RDBMS but with version 6 the RDBMS on startup will remove the file and startup. This remains consistent with Version 7.x.x.x.x. and as the previous post denotes a startup force will remove the file and startup the instance. This is real handy on Windows 3.x machines with personal oracle v.7.x after a GPF. Here we have observed that 3.x, Win95 and AIX all have this same feature.... Received on Sat May 18 1996 - 00:00:00 CEST