RE: To autostart database or not?

We never used dbshut without customizing it first.   It shutdown aborts
etc., good for SA who reboots server before shuting down database, or a
crash if it is rc3 directories... but for normal use we always seemed to
have to customize it... same for oraenv which be default only sets a
couple variables.  

Joel Patterson
Database Administrator
joel.patterson@xxxxxxxxxxx
x72546
904  727-2546

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Luis Fernando Cerri
Sent: Thursday, May 10, 2007 3:53 PM
To: Jay.Miller@xxxxxxxxxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: To autostart database or not?

Thats why I stated to always keep /etc/oratab updated, dbshut and
dbstart are based on it. :-)

Thanks for sharing your experience.

Best regards,
Cerri



2007/5/10, Jay.Miller@xxxxxxxxxxxxxxxx <Jay.Miller@xxxxxxxxxxxxxxxx>:
> We used to have our SAs restart using a script until the day the
standby
> database server crashed and they used the regular database startup
> script to restart it.
>
> After that we asked to be called.
>
>
>
> Jay Miller
> Sr. Oracle DBA
> x68355
>
>
> -----Original Message-----
> From: oracle-l-bounce@xxxxxxxxxxxxx
> [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Luis Fernando
Cerri
> Sent: Thursday, May 10, 2007 1:54 PM
> To: oracle-l@xxxxxxxxxxxxx
> Subject: Re: To autostart database or not?
>
> Why not give the SA the minimum knowledge to use dbshut/dbstart and
> always update your /etc/oratab when you create, update or remove an
> instance? I've worked this way for years and SAs always did a good
> job. Of course I always change the shutdown method to immediate on
> dbshut.
>
> If I cannot trust that Oracle do a minimum quality health-check at
> startup I should not sleep by other reasons.
>
> Just my thinking.
>
> Best regards,
> Cerri
>
>
>
--
http://www.freelists.org/webpage/oracle-l


--
http://www.freelists.org/webpage/oracle-l

Other related posts: