Re: changing workgroup corrupts autostart service on windows 2000?

"Sybrand Bakker" <gooiditweg_at_sybrandb.demon.nl> wrote in message news:sqlg00pes8832atobv5m1adf1q6na5bq1f_at_4ax.com...
> On Fri, 16 Jan 2004 20:06:03 GMT, "FC" <flavio_at_tin.it> wrote:
>
> >Hi all,
> >I am experiencing problems with the autostart setting of a database
service
> >and instance, after changing the workgroup.
> >This happens on Windows 2000 server + SP3 and Oracle 9.2.0.1.0.
> >I found a message suggesting to recreate the service using ORADIM but it
> >didn't work.
> >The event viewer does not show any entry for oracle unlike normally
happens
> >upon booting up the machine and also the ALRTxxxx.log file doesn't record
> >anything.
> >It looks like the service doesn't start at all.
> >All Oracle registry setting seem ok, I didn't change them since the db
> >installation.
> >If I start the db manually, it works fine.
> >I am going to reinstall Oracle from scratch unless someone comes up with
a
> >solution first.
> >
> >Any ideas?
> >Bye,
> >Flavio
>
> Without knowing exactly what the old and the new workgroup was and
> whether it is appropiate for Oracle, your question comes down to a
> call for crystal balls.
> Also, did you check the oradin.log at all to check whether anything is
> happening?
>
>
> --
> Sybrand Bakker, Senior Oracle DBA

Hello Sybrand,
by workgroup I mean the windows workgroup used to group together machines on a windows network, not a group of users. At any rate, the original workgroup was "WORKGROUP" and has been changed to "LG".
This machine is standalone, it's not a domain controller, the installation was carried out using the local administrator account.

The oradim.log contains a long sequence of "12638 credential retrieval failed", which must be paired with the corresponding entries in the sqlnet.log that is present in the same directory. Sqlnet.log contains error messages about authentication failure using bequeath protocol.

If I comment out SQLNET.AUTHENTICATION =(NTS), the db starts up automatically, however I wonder what is the difference with other machines where this parameter also is present.
Moreover I would like to fix the authentication problem, I do like os authentication when connecting via command line using "/ as sysdba".

Thanks,
Flavio Received on Mon Jan 19 2004 - 08:20:12 CST