drak0nian_at_yahoo.com (Paul Drake) wrote in message news:<1ac7c7b3.0210302243.a84b6fb_at_posting.google.com>...
> burgess_at_sympatico.ca (Bob Burgess) wrote in message news:<df35b276.0210291257.5868cafb_at_posting.google.com>...
> > For the benefit of those without Metalink access...
> > I recently encountered an ORA-27101 error from a user trying to
> > connect to his local Oracle database. He hadn't used it since our
> > system had been converted to use Active Directory (it worked before
> > then).
> > Changing "SQLNET.AUTHENTICATION_SERVICES= (NTS)" in his sqlnet.ora
> > file to "SQLNET.AUTHENTICATION_SERVICES= (NONE)" solved the problem.
> >
> > Bob Burgess
>
> Bob,
>
> If the local user belongs to the OS Group ORA_DBA or
> ORA_%ORACLE_SID%_DBA - NTS will work just fine. If you want to use
> domain accounts, add the domain user into a local group that has been
> granted the local group ORA_DBA.
>
> You aren't actually running an Oracle Database on a W2K Server acting
> as an Active Directory domain controller, are you?
> That is an explicit no-no, as no local accounts (groups) are allowed
> on such beasts.
>
> Separate the application servers (here, Oracle on W2K) from the domain
> controllers, please.
>
> also - make sure that you didn't break any scripts (backup jobs?) that
> used to "connect / as sysdba" - as they won't work anymore. You're
> back to putting passwords in the filesystem for such jobs.
>
> Paul
Paul,
Thanks for the info regarding the ORA_DBA group.
No, I'm not running an Oracle server on a domain controller. The
database is running on the user's laptop, but we are all authenticated
through Active Directory.
Good point about "connect / as sysdba", but we're not affected by this
change in this dev environment.
--Bob
Received on Tue Nov 12 2002 - 15:04:50 CST
