From: Hostetter, Jay M [mailto:JHostetter@(protected)] Sent: Tuesday, April 19, 2005 11:49 AM To: Oracle-L Cc: Goulet, Dick Subject: RE: sqlplus shutdown "time-out"
It's left over from Rama Velpouri's scripts in his Backup and Recovery handbook. (OK - I have the 7.3 book, so I don't know if this was changed in later releases of the book - if there were any). His book cites the reasons as:
1) To get the datafiles and redologs listing file (which I no longer need, now that I use RMAN)
2) To get a clean cold backup.
Jay
-- --Original Message-- -- From: Goulet, Dick [mailto:DGoulet@(protected)] Sent: Tuesday, April 19, 2005 11:44 AM To: Hostetter, Jay M; Oracle-L Cc: vitalisman@(protected) Subject: RE: sqlplus shutdown "time-out"
Question: Why the double shutdown? A "shutdown immediate" is a clean shutdown.
-- --Original Message-- -- From: oracle-l-bounce@(protected) [mailto:oracle-l-bounce@(protected)] On Behalf Of Hostetter, Jay M Sent: Tuesday, April 19, 2005 11:17 AM To: Oracle-L Cc: vitalisman@(protected) Subject: RE: sqlplus shutdown "time-out"
We are running the same database version and OS version. This same problem just recently started happening on one of our databases. We do the folowing
Shutdown immediate; Startup restrict; Shutdown;
The shutdown immediate was fine. However, the normal shutdown was generating the 1013 error. From what I could tell, a user with dba rights was connecting while the database was in restrict mode. I modified the script so that it locks that user's account prior to the first shutdown. This seems to have fixed my problem.
However, I'm not answering your question. I'm not sure what timeout value is used. Are these sessions executing some long running SQL commands? Can they be rescheduled to run at another time? Years ago, I had an instructer tell me that for backups, just do the following:
alter system checkpoint; shutdown abort; Startup restrict; Shutdown;
While this definitely brings the database down, I never really felt comfortable doing this. You might just want to kill active processes before you start your backup.
Jay
**DISCLAIMER This e-mail message and any files transmitted with it are intended for the use of the individual or entity to which they are addressed and may contain information that is privileged, proprietary and confidential. If you are not the intended recipient, you may not use, copy or disclose to anyone the message or any information contained in the message. If you have received this communication in error, please notify the sender and delete this e-mail message. The contents do not represent the opinion of D&E except to the extent that it relates to their official business.
