On 4/19/05, Hostetter, Jay M <JHostetter@(protected)> wrote: > 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: >=20 > 1) To get the datafiles and redologs listing file (which I no longer > need, now that I use RMAN) >=20 > 2) To get a clean cold backup. >=20 > Jay
Where to begin? In the land of win32, stopping an OS service that is set to use shutdown immediate is notorious for notorious for timing out prior to closing cleanly. Yes, one can hike the value of the key=20 HKLM\SYSTEM\CurrentControlSet\Control\WaitToKillServiceTimeout to a sensible value of (e.g. 300000) and use oradim to hike the "TIMEOUT" parameter. OEM agents, snmp agents are known to be resistant to dying quickly during a shutdown immediate.
Use hot or rman backups if the db is in archivelog mode.
Cold backups are highly overrated (a real pita).
I find them useful before a patchset is applied or before an upgrade to a new release. Making a hot backup consistent with a new set of binaries is an adventure that I do not recommend.
You're best off to check the current wind direction from Metalink, but I strongly believe that the preferred method is to:
alter system checkpoint; alter system switch logfile; shutdown abort; startup mount restrict; alter system set job_queue_processes=3D0; -- might want to mess with aq_processes here also shutdown immediate
(stop the OS service if you're on win32)
hth.
Paul
>=20 >=20 > -- --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" >=20 > Question: Why the double shutdown? A "shutdown immediate" is a clean > shutdown. >=20 > -- --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" >=20 > 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 >=20 > Shutdown immediate; > Startup restrict; > Shutdown; >=20 > 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. >=20 > 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: >=20 > alter system checkpoint; > shutdown abort; > Startup restrict; > Shutdown; >=20 > 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. >=20 > Jay >=20 > **DISCLAIMER > This e-mail message and any files transmitted with it are intended for th= e use of the individual or entity to which they are addressed and may conta= in information that is privileged, proprietary and confidential. If you are= not the intended recipient, you may not use, copy or disclose to anyone th= e message or any information contained in the message. If you have received= this communication in error, please notify the sender and delete this e-ma= il message. The contents do not represent the opinion of D&E except to the = extent that it relates to their official business. > -- > http://www.freelists.org/webpage/oracle-l >=20
--=20 #/etc/init.d/init.cssd stop # f=3Dma, divide by 1, convert to moles. -- http://www.freelists.org/webpage/oracle-l
