Hi All,
I have *finally* got time to drop one of our test instances and recreate it
(tomorrow), and wanted some feedback from all of you as to the best way to
go around this?
The current instance is 8.1.7. on a Win2K machine.. The reason that I'm
dropping/recreating (some of you may remember
Something to do with SYS.DUC$? Have you tried to delete all objects first (ie tables
(with CASCADE CONSTRAINTS), views, types, packages, sequences, functions, procedures
and synonyms - indexes, triggers and package bodies will go anyway) then to DROP USER
without CASCADE ? Otherwise if your
Never mind all - I cheated and used the Database Configuration Assistant
to drop and create a new one.. ;P
-Original Message-
Sent: 24 April 2002 12:53
To: Multiple recipients of list ORACLE-L
Hi All,
I have *finally* got time to drop one of our test instances and recreate it
Hi Witold,
Thanks for the reply..
I had already dropped all of scott's objects (although this does actually
occur with *any* user that I tried it against), then connected as SYS as
shown below, and still got the same error. I also re-ran catalog.sql and
catproc.sql..
There were no other
Mark,
to remove an instance on NT (not the software, just the instance) do the
following:
Use ORADIM -sid {sid} -delete to remove the NT services for the instance.
then, simply remove all file structures for the database.
That's all there is to it. The database is gone.
On a side note - I
The db config assistanct has a 'delete db' option that
works quite well. even if it cannot connect to the
db, it will still get rid of the registry and services
bits for the db
hth
connor
--- Mark Leith [EMAIL PROTECTED] wrote: Hi
All,
I have *finally* got time to drop one of our test
Mark,
Shame on you. Ignoring good old ORADIM?
Igor Neyman, OCP DBA
[EMAIL PROTECTED]
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Wednesday, April 24, 2002 9:03 AM
Never mind all - I cheated and used the Database Configuration
Assistant
to
Hi Mark,
Regarding your problem with dropping a user, I've seen something like that
before - this was 817 on Solaris, and the DBA there was getting a ORA-00942
at recursive SQL when trying any CTAS.
I ran a trace on the statement and found that Oracle was looking for a
sys.snap$ table which