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
Drop user fails with ORA-01418

Drop user fails with ORA-01418

2004-11-16       - By William B Ferguson

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

I think you can if you disable the flashback_recovery_area. It appears
that the main purpose is for a group like mine, where you have several
different people at the beginning stages of Oracle expertise, but they
still need (due to managerial and political considerations), full access
to all of the data. If they happen to accidentally drop an object, or =
even
rows from an object, with the flashback_recovery_area, you can recover
everything they accidentally did up to whatever point in time without =
have
to do a datafile restore and losing other appropriate changes made after
that.

It 's still new and I 'm still learning it, so I could be wrong, but =
that 's
my impression so far (and it 's actually saved me some grief so far as
well) with my limited expertise.

-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
Bill Ferguson
U.S. Geological Survey - Minerals Information Team
PO Box 25046, MS-750
Denver, Colorado 80225
Voice (303)236-8747 ext. 321 Fax (303)236-4208

~ Think on a grand scale, start to implement on a small scale ~




-- --Original Message-- --
From: Mercadante, Thomas F [mailto:thomas.mercadante@(protected)]=20
Sent: Tuesday, November 16, 2004 9:09 AM
To: William B Ferguson; chadi@(protected)
Cc: oracle-l@(protected)
Subject: RE: Drop user fails with ORA-01418 (See ORA-01418.ora-code.com)


Recycle bin. OMG. Has Oracle become Windows? We don 't need no freekin
recycle bin.

Can we turn this off???? :)



-- --Original Message-- --
From: William B Ferguson [mailto:wbfergus@(protected)]=20
Sent: Tuesday, November 16, 2004 11:06 AM
To: chadi@(protected); thomas.mercadante@(protected)
Cc: oracle-l@(protected)
Subject: RE: Drop user fails with ORA-01418 (See ORA-01418.ora-code.com)


Chadi,

The BIN$... Object is a dropped trigger (it appears to be anyway), that =
is
in the recycle bin, and apparently the drop user statement seems to be
having trouble deleting the user with an associated object in the =
recycle
bin.

To try and get around it, try going the web-enable enterprise manager, =
the
administration page, then Tables (or actaully any object), filter for =
the
owner of the object, the the recycle bin button appears. Or, from the =
sql
prompt, you can do a "purge dba_recyclebin; " (to empty the recycle bin =
for
all users, or connect as the user and issue a "purge recyclebin; ".

I think this will get around the problem you are experiencing.

-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
Bill Ferguson
U.S. Geological Survey - Minerals Information Team
PO Box 25046, MS-750
Denver, Colorado 80225
Voice (303)236-8747 ext. 321 Fax (303)236-4208

~ Think on a grand scale, start to implement on a small scale ~




-- --Original Message-- --
From: oracle-l-bounce@(protected) =
[mailto:oracle-l-bounce@(protected)]
On Behalf Of chadi@(protected)
Sent: Tuesday, November 16, 2004 8:32 AM
To: 'Mercadante, Thomas F '
Cc: oracle-l@(protected)
Subject: RE: Drop user fails with ORA-01418 (See ORA-01418.ora-code.com)


Actually, this is my problem. I couldn 't drop some objects in the user, =
so
i decided to rebuild the user and still stuck with this:

the trace is shwoning that some trigger is causing the ora600:

ksedmp: internal or fatal error
ORA-00600 (See ORA-00600.ora-code.com): internal error code, arguments: [15239], [], [], [], [], [],
[], [] Current SQL statement for this session: drop trigger
"CHADI ". "BIN$5/+ZaDjf/yjgMIEKQwE88g=3D=3D$0 "


Chadi.

-- --Original Message-- --
From: Mercadante, Thomas F [mailto:thomas.mercadante@(protected)]
Sent: Tuesday, November 16, 2004 10:24 AM
To: 'chadi@(protected) '; oracle-l@(protected)
Subject: RE: Drop user fails with ORA-01418 (See ORA-01418.ora-code.com)


Chadi,

Did the user get dropped?

If not, can you go through and drop the users objects manually? And =
then
drop the user? It is obviously an Oracle problem. But if you can find =
a
workaround, then you can chalk it up to experience.

Personally, I do not drop a user that has a bunch of objects. I prefer =
to
drop all the objects first and then the user just for this reason.

Hope this helps.

Tom Mercadante
Oracle Certified Professional


-- --Original Message-- --
From: Chadi Kassan [mailto:chadi@(protected)]=20
Sent: Tuesday, November 16, 2004 10:01 AM
To: oracle-l@(protected)
Subject: Drop user fails with ORA-01418 (See ORA-01418.ora-code.com)


Hi everyone,

I 'm pretty sure, many had run into this problem before and can provide
some help. When I try to drop one of my user, I get the following:

SQL > drop user theuser cascade;

ORA-00604 (See ORA-00604.ora-code.com): error occurred at recursive SQL level 1
ORA-01418 (See ORA-01418.ora-code.com): specified index does not exist

What index it 's talking about, metalink says this is related to some =
data
corruption in data dictionnary, but doesn 't provide a solution.


We run Oracle Database 10g Release 10.1.0.3.0 on Linux.

Thank you.
--
http://www.freelists.org/webpage/oracle-l
--
http://www.freelists.org/webpage/oracle-l
--
http://www.freelists.org/webpage/oracle-l