I have a problem using "Shutdown immediate;". It shuts down the instance but sometimes it won't return to the sqlplus prompt. I have to close the terminal and start the database in a new terminal. Do you know why? Oracle 9i/Solaris 9 64bit. Thanks.
-- --Original Message-- -- From: oracle-l-bounce@(protected) [ mailto:oracle-l-bounce@(protected)]On Behalf Of Powell, Mark D Sent: Tuesday, April 19, 2005 10:37 AM To: Oracle-L Subject: RE: sqlplus shutdown "time-out"
Since a shutdown immediate leaves a database in a consistent state there really is no reason to re-start Oracle in a restricted state and then shut it back down again.
If you run a kill script to kill all connected user sessions prior to issuing the shutdown immediate any shutdown hanging problems your may be encountering are likely to become much less frequent.
HTH -- Mark D Powell --
-- --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
-- --Original Message-- -- From: oracle-l-bounce@(protected) [ mailto:oracle-l-bounce@(protected)] On Behalf Of Vitalis Sent: Thursday, April 14, 2005 9:45 AM To: Oracle-L Subject: sqlplus shutdown "time-out"
Hi all,
9.2.0.5.0 on Aix 5L. Before our cold RMAN backups, we shutdown and startup the instances as foll= ows:
sqlplus '/ as sysdba' <<EOD shutdown immediate startup shutdown immediate startup mount EOD
Sometimes both shutdowns seem to time-out automatically (certainly while Oracle is busy rolling back some huge transactions):
SQL*Plus: Release 9.2.0.5.0 - Production on Thu Apr 14 01:35:02 2005
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to: Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production With the Partitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.5.0 - Production
SQL> ORA-01013 (See ORA-01013.ora-code.com): user requested cancel of current operation SQL> ORA-01081 (See ORA-01081.ora-code.com): cannot start already-running ORACLE - shut it down first SQL> ORA-01013 (See ORA-01013.ora-code.com): user requested cancel of current operation SQL> ORA-01081 (See ORA-01081.ora-code.com): cannot start already-running ORACLE - shut it down first SQL> Disconnected from Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production With the Partitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.5.0 - Production =3D=3D> Ended consistent instance shutdown and mount: Thu Apr 14 03:37:55 D= FT 2005
Both "user requested cancel" aren't human actions and it seems that both shutdowns time-out after 1 hour.
What might be the cause of thes time-outs giving that sql*net is not involved and that sys's profile is "default" (idle_time=3Dunlimited). I can't find any relevant time-out parameter for sqlplus (only for isqlplus).
For technical support please email tech_support@(protected) or you can call (972)721-8257. This email has been scanned for all viruses by the MessageLabs Email Security System.
This e-mail is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. Any review, dissemination, copying, printing or other use of this e-mail by persons or entities other than the addressee is prohibited. If you have received this e -mail in error, please contact the sender immediately and delete the material. __ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ _____ This email has been scanned for all viruses by the MessageLabs Email Security System. Any questions please call 972-721-8257 or email your request to tech _support@(protected) -- http://www.freelists.org/webpage/oracle-l
