We are set up the same. Production auto starts. Dev and test do not. SAs know to call if there is an issue on restart. Works great. I love my sleep. Steve Smith Desk: 303-231-5499 -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Guang Mei Sent: Thursday, May 10, 2007 7:44 AM To: dwaynec@xxxxxxxxxxxxxx; oracle-l@xxxxxxxxxxxxx Subject: RE: To autostart database or not? I have my production dbs auto-started, while the dev dbs not. Usually the alert log file and trace/dump file would give you enough clue(s) why the instance goes down. I am in Boston and I had one db in California went down at 3am (Boston time) because of power outage. I did not get the call and it auto-started. Guang -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Dwayne Cox Sent: Thursday, May 10, 2007 8:38 AM To: oracle-l@xxxxxxxxxxxxx Subject: To autostart database or not? We are running a few Oracle9i and 10g databases on RHEL and I have always opted NOT to have the databases automatically restart when the server goes down due to something unexpected. My thinking was that if the server crashed, then I want to be there to bring up the databases to assess and repair any damage (yes, I am the only production DBA). Am I being overly controlling? Looking for other opinions and thoughts on the matter. Thanks -- Dwayne Cox, Corporate DBA Info Tech, Inc. dwayne.cox@xxxxxxxxxxxxxx -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l