| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: sqlplus shutdown "time-out"
Question: Why the double shutdown? A "shutdown immediate" is a clean
shutdown.=20
-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Hostetter, Jay M
Sent: Tuesday, April 19, 2005 11:17 AM
To: Oracle-L
Cc: vitalisman_at_gmail.com
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_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] 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=3D
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):
=3D3D=3D3D> Beginning consistent instance shutdown and mount: Thu Apr 14 01:35:02 DFT 2005 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: user requested cancel of current operation SQL> ORA-01081: cannot start already-running ORACLE - shut it down first SQL> ORA-01013: user requested cancel of current operation SQL> ORA-01081: cannot start already-running ORACLE - shut it down first SQL> Disconnected from Oracle9i Enterprise Edition Release 9.2.0.5.0 -64bit Production
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=3D3Dunlimited). =
I
can't find any relevant time-out parameter for sqlplus (only for
isqlplus).
TIA,
Jerome
**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.
-- http://www.freelists.org/webpage/oracle-l -- http://www.freelists.org/webpage/oracle-lReceived on Tue Apr 19 2005 - 12:05:47 CDT
 |
 |