I had rather thought that SYSDBA was an arbitrary account name generally
used when creating new databases. In fact, it is hard coded in at least
two places. Is this a really good idea? The idea of a magic account
like "root" is pretty much discredited in favor of schemes that create a
privileged account at creation time. Should we be considering
eliminating the builtin SYSDBA in favor of the user name give when
creating a database?

--

Jim Starkey
Netfrastructure, Inc.
978 526-1376