Re: RE Startup on boot

Hi Guy,

	In my shop, if it's a database server, the sysadmins will not shut it down 
	without talking to a DBA.  If it's a crash, they will be talking to us anyways :)

	The main reason is often it is not just Oracle. There
	may be context servers, there may be replication, it 
	may be a parallel server, it may be hooked into a transaction
	manager, remote crons, LDAP ..... I do not expect the sysadmin 
	to track these things, I believe that is part of our job.

	sync, sync, sync 

	What is really scary is after watching alot  of sysadmins I respect 
	do this I've started doing it myself when in that situation.

Dave

>
> Dave Morgan wrote:
>
>
> > We have automated start scripts and I feel it is part of the job
> > to take calls at 3 AM to do starts. Also , the sysadmins I trust have
> > been shown how to start oracle. (NOT how to STOP oracle).
>
> You *must* also show them how to shut Oracle down cleanly, and make sure
> that they always do it. Traditional sysadmins tend to type things like:
>
> # sync; sync; sync; poweroff
>
> Which simply dumps the OS disk cache (VERY different to the SGA) to
> disk, kills every process without warning, and switches off the entire
> machine. This is because ordinary Unix daemons, such as FTP servers and
> the like, don't mind that sort of behavior.
>
> (Note: I have no idea why they sync three times, but every sysadmin
> I've ever met does. I've checked, and a single time would be enough.
> Must be some weird tribal tradition.)
>
> g
>

-- 
Dave Morgan
Senior Database Administrator
Internet Barter Inc.