Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!apple!mips!daver!kcdev!genco!rad
From: rad@genco.bungi.com (Bob Daniel)
Newsgroups: comp.unix.admin
Subject: Re: Who's in charge here: Oracle or Unix?
Keywords: Oracle, system, files
Message-ID: <504@genco.bungi.com>
Date: 22 Feb 91 03:13:15 GMT
References: <635@uswnvg.UUCP> <1777@public.BTR.COM> <1991Feb18.102140.29446@erbe.se>
Reply-To: rad@genco.bungi.com (Bob Daniel)
Organization: Gentry & Assoc. Excelsior Springs, MO
Lines: 14

>In article <1777@public.BTR.COM> scharf@public.BTR.COM (Jerry Scharf  scharf@btr.com) writes:
>
>>My personal experiences with Oracle are as bad as the
>>others I've seen. Do they still fail to catch the shutdown signal, and
>>leave the database corrupted when the system is shut down without first
>>stopping Oracle.

There is a simple solution to this.  You can easily setup a shutdown
oracle script and place it in /etc/rc0.d  and to auto startup oracle,
place a startup script in /etc/rc2.d.  This works very well for me. 
When unix performs a shutdown, the oracle database(s) will be properly
shutdown.  When unix comes up, the database(s) come up.  The concept
is exactly the same as starting up/shutting down the lp scheduler and
cron.  If anyone wants the scripts to do this, I'll email them.