Paula,
Shutdown abort is not recommended as the file
checkpointing is not done during shutdown abort. If you need to perform
shutdown abort, then, it is preferred to bring up the db with startup restrict
(so that the users wouldn't connect) and then, cleanly shutdown the db and bring
it up again.
Tell
to your sys admins. that shutdown immediate would take some time (about 5 to 10
minutes) depending on the activity on your db. They would have to wait for
that much time before calling a DBA during system boots.
Rao
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 29, 2003 11:30 AM
To: Multiple recipients of list ORACLE-L
Subject: RE: Debate on rc commands Solaris and OracleSystem Administrator says he doesn't trust that the rc commands will stop if the database doesn't want to shutdown and even if it does would want to shutdown with scripts beforehand so that a DBA could connect and resolve the issue. Other DBA says this is all wrong and rc commands should include shutdown immediate of database. In the past I had setup 2 processes in the system scripts for the sys admin - shutdown immediate - wait .... shutdown abort - on a read-only DSS system which of course allows some room for this type of activity. I kind of would want to know if a database was going to be shutdown with an abort esp. in OLTP system and do it myself.
- any ideas