>>So what is the point of having the SYSDBA user if you can't really do
>>anything with it?
>
>
> Whoo-ee, you sure can do literally *anything* with it. That's why you take
> great care to make sure that the owner of a database and of the objects in
> it are not SYSDBA, if you are going to be in the position where you can't
> have SYSDBA access.
>

They can't drop a constraint while more then one user is connected ;)

For that matter, there is a BUNCH of stuff that SYSDBA can't do when
another user is connected.