Home
All Oracle Error Codes
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

RE: ORA-01940: cannot drop a user that is currently connected

Spears, Brian

2006-07-05

Replies:
RE: ORA-01940: cannot drop a user that is currently connected

 Does the process show up in V$session. (Most people have scripts joining v$session and v$process to show sessions that will not show sessions because the show will only show sessions with process and you can miss some in other states.) Sometime app/web servers constantly relog in after being killed making it hard to drop the user. In those cases I shutdown /startup restrict, drop the user then take off the restricted session.

      -----Original Message-----
      From: oracle-l-bounce@freelists.org [mailto:oracle-l-bounce@freelists.org] On Behalf Of John Dunn
      Sent: Wednesday, July 05, 2006 5:27 AM
      To: 'oracle-l digest users'
      Subject: ORA-01940: cannot drop a user that is currently connected

      ORA-01940: cannot drop a user that is currently connected

      I get this error on Oracle 10.2.0.1.0 but cannot see any sessions for the user.

      I have rerun the drop, but now it just hangs.

      Anything I can do but bounce the database?

      John Dunn

      Product Consultant

      Direct Dial +44 (0) 117 373 6122

      Sefas Innovation Ltd, CityPoint, Temple Gate, Bristol BS1 6PL, UK.

      Tel: +44(0) 117 373 6114

      Fax: +44 (0) 117 373 6115

      www.sefas.com