And for an opposing opinion: Let's see now. We create another user and grant that user all the privileges needed to do ANYTHING. And that makes things sooooo much more secure? If that's the prevailing thought among the database world, then it's safe to say that the Unix admins have infinitely more common sense by logging as root when functioning as root. Well NO! We should create a user named rewt with the same UID and GID as root; and then always log in as rewt (or route).
For what it's worth, if you have many databases, it's going to be a real pain in the ass to track every stinkin' DBA account and not have those DBA accounts that we forgot about when old Joe quit or (worse) when Billy Bob decided to become a developer instead of a DBA. If somebody can't log in as SYSTEM or SYS without fouling things up, they shouldn't be logging in at all. And if they have DBA privs, they can make a mess regardless of whether they log in as SYSTEM or CISTUM. -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: <[EMAIL PROTECTED] INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
