hi ....
I took risk in my test DB by dropping the user 'SYSTEM'. As you tested, the same steps i repeated in mine, all are fine, until before.
Now i shutdown my database and startup again, here the problem arises. Oracle mount the database but while opening the database, the instance has been terminated by PMON.
Sat Oct 20 10:57:45 2001
PMON: terminating instance due to error 470
Instance terminated by PMON, pid = 316
Oracle posted the following error continuosly in the alert log:
SMON: following errors trapped and ignored:
ORA-00376: file 1 cannot be read at this time
ORA-01110: data file 1: 'D:\ORACLE\ORADATA\ORCLSVR\SYSTEM01.DBF'
Am crusious, come to know what type of problem you have faced?....
Regards,
Nirmal
-----Original Message-----
From: Jacques Kilchoer [SMTP:[EMAIL PROTECTED]]
Sent: Friday, October 05, 2001 12:30 AM
To: Multiple recipients of list ORACLE-L
Subject: RE: Droping System User
> -----Original Message-----
> From: [EMAIL PROTECTED] [ <mailto:[EMAIL PROTECTED]>]
>
> Dropping the SYSTEM user is not really all that traumatic.
>
> In most cases it's just a DBA account that may own some pieces you'd
> rather not lose, but dropping SYSTEM will not be noticed by the users
> of the database.
That's the impression I get. When I looked at the objects owned by SYSTEM in my test database before the drop, none of them seemed vital.
On the other hand, dropping sys would probably be bad, but I wasn't able to do that (insufficient privileges.)
Trying to drop sys tables like sys.user$ caused an ORA-00701.
So since I'm on a quest to wound this database, I tried this:
SQL> delete from sys.user$ where name = 'SYS' ;
1 ligne supprim�e.
SQL> commit ;
Validation effectu�e.
So far no ill effects!
