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
sqlplus shutdown "time-out "

sqlplus shutdown "time-out "

2005-04-14       - By Vitalis

Reply:     1     2     3     4     5     6     7     8     9     10     >>  

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):

=3D=3D> 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 (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).

TIA,
Jerome
--
http://www.freelists.org/webpage/oracle-l