| 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: Drop user fails with ORA-01418
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.
~ Think on a grand scale, start to implement on a small scale ~
-----Original Message-----
From: Mercadante, Thomas F [mailto:thomas.mercadante_at_labor.state.ny.us]=20
Sent: Tuesday, November 16, 2004 9:09 AM
To: William B Ferguson; chadi_at_myvirtualmodel.com
Cc: oracle-l_at_freelists.org
Subject: RE: Drop user fails with ORA-01418
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_at_usgs.gov]=20
Sent: Tuesday, November 16, 2004 11:06 AM
To: chadi_at_myvirtualmodel.com; thomas.mercadante_at_labor.state.ny.us
Cc: oracle-l_at_freelists.org
Subject: RE: Drop user fails with ORA-01418
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.
~ Think on a grand scale, start to implement on a small scale ~
-----Original Message-----
From: oracle-l-bounce_at_freelists.org =
[mailto:oracle-l-bounce_at_freelists.org]
On Behalf Of chadi_at_myvirtualmodel.com
Sent: Tuesday, November 16, 2004 8:32 AM
To: 'Mercadante, Thomas F'
Cc: oracle-l_at_freelists.org
Subject: RE: Drop user fails with ORA-01418
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: 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_at_labor.state.ny.us]
Sent: Tuesday, November 16, 2004 10:24 AM
To: 'chadi_at_myvirtualmodel.com'; oracle-l_at_freelists.org
Subject: RE: Drop user fails with ORA-01418
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_at_myvirtualmodel.com]=20
Sent: Tuesday, November 16, 2004 10:01 AM
To: oracle-l_at_freelists.org
Subject: Drop user fails with ORA-01418
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: error occurred at recursive SQL level 1 ORA-01418: 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
Received on Tue Nov 16 2004 - 10:43:40 CST
 |
 |