Links
• Home
• Oracle DBA Forum
Frequent Oracle Errors
•TNS:could not resolve the connect identifier specified
•Backtrace message unwound by exceptions
•invalid identifier
•PL/SQL compilation error
•internal error
•missing expression
•table or view does not exist
•end-of-file on communication channel
•TNS:listener unknown in connect descriptor
•insufficient privileges
•PL/SQL: numeric or value error string
•TNS:protocol adapter error
•ORACLE not available
•target host or object does not exist
•invalid number
•unable to allocate string bytes of shared memory
•resource busy and acquire with NOWAIT specified
•error occurred at recursive SQL level string
•ORACLE initialization or shutdown in progress
•archiver error. Connect internal only, until freed
•snapshot too old
•unable to extend temp segment by string in tablespace
•Credential retrieval failed
•missing or invalid option
•invalid username/password; logon denied
•unable to create INITIAL extent for segment
•out of process memory when trying to allocate string bytes
•shared memory realm does not exist
•cannot insert NULL
•TNS:unable to connect to destination
•remote database not found'>ora-02019
•exception encountered: core dump
•inconsistent datatypes
•no data found
•TNS:operation timed out
•PL/SQL: could not find program
•existing state of packages has been discarded
•maximum number of processes exceeded
•error signaled in parallel query server
•ORACLE instance terminated. Disconnection forced
•TNS:packet writer failure
•see ORA-12699
•missing right parenthesis
•name is already used by an existing object
•cannot identify/lock data file
•invalid file operation
•quoted string not properly terminated
hanging shutdowns (addressing the requirement for a UNIX reboot)

hanging shutdowns (addressing the requirement for a UNIX reboot)

2006-03-01       - By John Kanagaraj

Reply:     1     2     3     4     5  

Boris,

I don't know about the other issues, but if 'shutdown immediate' was
Control-ced and it never came back to the prompt (i.e. hung), then you
will have to kill the sqlplus session itself. In that case, you will not
be able to relogin... It seems in your case, you reused the same session
and did not have to relogin.

John

-- --Original Message-- --
From: Boris Dali [mailto:boris_dali@(protected)]
Sent: Wednesday, March 01, 2006 11:33 AM
To: John Kanagaraj; roger_xu@(protected); Oracle-L@(protected)
Subject: RE: hanging shutdowns (addressing the requirement for a UNIX
reboot)

John,

> This is because once you initiate a 'shutdown immediate' and
> 'control-c'ed out of it, then you will never be able to login since
> any new attaches will complain that a shutdown is in progress, and the

> only way out is to kill the backend processes.

This must be platform specific. Here's for instance how it works for me
in Oracle 9.2.0.6 on Linux:

SQL> sho release
release 902000600

SQL> shutdown immediate;  -- and Ctrl-C
ORA-01013 (See ORA-01013.ora-code.com): user requested cancel of current operation

SQL> shutdown abort;  -- no problem to abort
ORACLE instance shut down.
--
http://www.freelists.org/webpage/oracle-l