database could not be started

this is what actually happens
1) we had scripts to shutdown/startup the database for offline backup in our crontab entries
2) and these scripts had been working fine. 3) but recently, there had been 2 times when the scripts are not working
4) scenario: couldnt startup database therefore go and analyze 5) found that the shutdown script did not shutdown the database. Cos going into svrmgrl, and doing a startup says that "the oracle instance is still running"
5.1) do a ps -ef | grep ora and indeed saw all these oracle processes including the shutdown script entry.
5.2) going back to svrmgrl, did a shutdown immediate. still same result in 5.1
5.3) colleague did a shutdown abort and it works.

my questions

1)is that isnt it dangerous to do a shutdown abort. actually, i was thinking about killing all the orace processes. so which is more advisable?

2) what are the valid reasons doing a shutdown abort.

thanks Received on Fri Aug 08 2003 - 19:25:36 CDT