Re: Oracle Management Server problem !

[Quoted] Well Niall, I managed to fix the problem. [Quoted] There were several factors leading to the authentication failure, including a misinterpretation of your advice.
[Quoted] Moreover I think Oracle Documentation is not bulletproof in this case, I find it somewhat confusing given the number of documents that one should read before having the complete picture (Installation Readme, Configuration [Quoted] Guide, Release Notes, Administration Guide).

[Quoted] Basically I found out that I had mistakenly configured the Intelligent Agent, forcing it to run as a user different from LocalSystem, although that [Quoted] was one of the possibilities mentioned in the docs. The fact that such user [Quoted] was granted the privilege "Logon as a batch job" was useless.

Summarising the configuration steps:

1.1 On the managed node there must be an Intellingent Agent of a version equal or higher than the database(s) being managed.

1.2. The Intelligent Agent should (or must?) run as LocalSystem.

1.3 The TMP environment variable must point to a folder whose security rights allow the "Agent" user to read and write data. At some point it turned out that TMP was set to C:\WINNT\TEMP and the user I created didn't have the required rights. This was also confusing because normally the TMP variable is set to C:\Documents and settings\<%username%>, so I was surprised by this problem.

1.4 User rights must be also correctly set for any other folder(s) where the output of the jobs will be placed.

2.1 OMS credentials for the node: name of a Windows 2000 user having the "logon as batch job" privilege.

2.2 OMS credentials for the DB: any user with the appropriate priveleges or roles required by the tasks that you want to perform.

Thanks for now!
Flavio

"Niall Litchfield" <n-litchfield_at_audit-commission.gov.uk> wrote in message news:3e22aa90$0$245$ed9e5944_at_reading.news.pipex.net...
> I'd try setting the authentication details for the database to
> system/<password> as well. I.E. not faffing about with external
> authentication just yet. Oh and I had a problem with one of my servers
where
> the overnight batch jobs didn't run for almost a week, until I figured out
> that I hadn't typed the password correctly :(.
>
>
> --
> Niall Litchfield
> Oracle DBA
> Audit Commission UK
> *****************************************
> Please include version and platform
> and SQL where applicable
> It makes life easier and increases the
> likelihood of a good answer
>
> ******************************************
> "FC" <flavio_at_tin.it> wrote in message
> news:lngU9.20096$0v.553489_at_news1.tin.it...
> >
> > "Niall Litchfield" <niall.litchfield_at_dial.pipex.com> wrote in message
> > news:3e21899b$0$238$cc9e4d1f_at_news.dial.pipex.com...
> >
> > > "FC" <flavio_at_tin.it> wrote in message
> > > news:yCeU9.19539$0v.537438_at_news1.tin.it...
> > > > If you ever manage to submit and execute successfully a batch job
> using
> > > OMS,
> > > > let me know, I am stuck right there!
> > >
> > > You will need the preferred credentials for the node that you wish to
> run
> > > the batch job on to be set to an operating system account, On windows
> that
> > > account needs at the very least the 'log on as a batch job' privilege.
> You
> > > obviously also need valid oracle credentials.
> > >
> > >
> > > --
> > > Niall Litchfield
> > > Oracle DBA
> > > Audit Commission UK
> >
> > That is exactly what I did, or at least I believe so.
> > I created an OS user, granted the "logon as a batch job" privelege,
> created
> > an oracle user with the same name (os_authent_prefix = ""), set
> > authentication to "external", granted DBA role, and.... it doesn't work.
> > That's where I am stuck. Well, I am trying out the OMS in my spare time,
I
> > am not wasting hours on it, but at any rate, it's not so "hasslefree"
the
> > installation.
> >
> > Bye,
> > Flavio
> >
> >
>
>
Received on Mon Jan 13 2003 - 21:08:17 CET