Thanks for the tips. I figured it was straight forward. And luckily we only
have a few servers to deal with.
Sent from my iPhone
On Apr 11, 2015, at 10:31 AM, MARK BRINSMEAD <mark.brinsmead@xxxxxxxxx> wrote:
Just to expand on the last suggestion...
If there are "problems" with the domain account, you can also run into
(possibly silent) failures in jobs scheduled by Windows. Your backups may
not start, data extracts or loads might not run. Perhaps even your
monitoring may stop working if it needs to be restarted periodically, or
relies on one-off scripts.
I am no windows expert, so I can't say much about the mechanisms involved,
but I have seen failures on customer systems where domain accounts were used
for these sorts of purposes. Expired passwords were, I think, a common cause
of issues but there may also have been causes buried in the LDAP (or whatever
Microsoft has renamed it) layer.
On Sat, Apr 11, 2015 at 10:48 AM, H. Abhishek <authoritydba@xxxxxxxxx> wrote:
The biggest 'gotcha' would be, in my opinion, if this goes large scale and
something goes wrong with the domain 'service' account password getting
changed/ locked.
You would end up with the services not coming up and will need a tool/
manually update the password everywhere.
Regards,
Abhishek
On Sat, Apr 11, 2015 at 4:38 AM, David Ramírez Reyes <dramirezr@xxxxxxxxx>
wrote:
We have both scenarios here and switch from local user to a domain user is
as easy as it seems, as long as the domain user is part of the
Administrators group, you won't have any problem.
Regards
David Ramírez Reyes
Profesión: Padre de Familia
On 10 April 2015 at 17:48, Jeff Chirco <backseatdba@xxxxxxxxx> wrote:
For the Oracle on Windows DBA's. We currently have the Windows Service set
to Log On As "Local System" but we need to change this to run as a Domain
account so we can access our file share. I added the domain account to
the Administrators and ora_dba and everything seems good. But is their any
other gotchas that I could be missing?
Jeff
