Re: Oracle versus MS Sql Server

"Mark Townsend" <markbtownsend_at_home.com> schrieb im Newsbeitrag news:B7F589C4.3C02%markbtownsend_at_home.com...
> in article B7F585D2.3BF5%markbtownsend_at_home.com, Mark Townsend at
> markbtownsend_at_home.com wrote on 10/19/01 7:25 AM:
>
> > Make sure that the OS credential you set up in Oracle Management Server
is a
> > valid NT user with the correct system permissions to run batch jobs.
>
> I see in antoher post that you state you have already done this - however,
> finger trouble may get in the way - check that the userid can actually log
> in without error messages etc.
>
> 99.9999% of the time, this is the problem that causes the above message.
> However, you can also see it if the credential is in a different domain
than
> the OEM agent and the two domains can't communicate. This, with the
previous
> problem you had with NT authentication, makes me convinced that you have
> some sort of wierd domain flakiness going on in your NT environment.
> Unfortunately, I don't know enough about W2000 to help you debug this. I'd
> suggest that you call Oracle Support and get them on the case, or
> alternatively, as a test, repeat the process on a different machine,
> preferably one which isn't the PDC.

I do understand that helping is difficult without actually sitting at the machine. Anyway here are some more details, some related to your questions:

[1] I am no Oracle DBA guru at all. But I do know Windows. This system is very unlikely to have a "sort of wierd domain flakiness ".

[2] This is a single domain environment.

[3] The Oracle Server also happens to be a Windows 2000 Server, which also is the PDC. This PDC has no long history of install/uninstall. It is a fresh server.

[4] Maybe I did not quite understand my other problem regarding the "SQLNET.AUTHENTICATION_SERVICE " setting. My understanding so far has been that this setting should almost always have a value of "NONE" and not "NTS" (as the setup configured it).

[5] Yes, the user can log on interactively. For testing purposes I choose the domain admin.

[6] One more piece of information, which I cannot interpret correctly. When connecting to the database, I will fail if I connect as "SYS" or "SYSTEM" with the "AS SYSDBA" option. The "AS SYSDBA" can only be used with "INTERNAL". Does this give any hint or information to an expert Oracle DBA?

Michael G. Schneider Received on Fri Oct 19 2001 - 09:59:35 CDT