Re: Can OEM list the Nodes folder in terms of IP address, instead of Hostname

"Niall Litchfield" <niall.litchfield_at_dial.pipex.com> wrote in message news:<3eea133e$0$19598$cc9e4d1f_at_news.dial.pipex.com>...
> "Jeffrey Yee" <jeffyee_at_hotmail.com> wrote in message
> news:ec4cec95.0306121831.3a6b2fe3_at_posting.google.com...
> >
> > Relocating a database might also involve changes to the hostname. But
> > that is beside the point. Customer prefer to see the IP address for
> > some reason, and it would be a shame that OEM cannot cater for such
> > trivia stuff. It's just the label of the node.
>
>
> What happens if you don't have a DNS entry for that server at all? I haven't
> tried this but it maybe that OEM would revert to using the IP Address in
> this case.
>

I'm very keen to try this out, but I heard from my colleagues that host file in windows 2000 is cached, and changes to the host file will not take effect immediately. Any idea how I do I refresh the cache? If this is successful, and than I put back the DNS entry, and do a refresh node, wonder if this will change the IP address back to hostname. I will try it, once I figure out the cache issue.

> > > >
> > > >Lastly, I also have problem with OS authentication db using OEM. How
> > > >do I login into OEM as SYSDBA, if OEM is running on Win2000 server?
> > > >The only OS user that has SYSDBA privilege on HP-UX is Oracle, and the
> > > >remote_os_authent parameter is set to false.
> > >
> > > Just grant any ordinary oracle user SYSDBA privilege. That's all. Also
> > > if remote_login_passwordfile has been set correctly SYS can also login
> > > as SYSDBA. This is a non-issue which has already been dealt with.
> >
> > My customer still prefer the remote_login_passwordfile=none, means
> > using OS authentication. Under this circumstances, I can't grant
> > sysdba to another user, because there is no password file to write to.
>
> As you are using a repository you don't login to OEM as sysdba, you login to
> OEM as an administrator, which is an OEM Role and does not correspond to a
> database user. Each administrator has preferred credentials for the objects
> they administer, in the case of a node this would be an OS Users
> credentials. The situation you describe (Only Oracle is allowed sysdba privs
> and then only physically at the console) seems designed to prevent remote
> management of the machine (unless I am missing something daft). Assuming the
> customer would be OK with this I would suggest creating an OS account for
> use by OEM and placing it in the DBA OS Group, you would then need to put he
> credentials for that user into the preferred credentials for use by OEM on
> that node. I believe that the actual login with this account is done by the
> agent on the db server and so you shouldn't need to change remote_os_auth at
> all.
>

My mistake, I meant to type login to the database of a node as sysdba, instead of login in to OEM as sysdba. I login to OEM as sysman at the moment. Sorry for the confusion.

I took the time to try out everyone's comment and you guys are 100% correct. In short, I will have to set
remote_login_passwordfile=EXCLUSIVE (or SHARE) and create the password file using ORAPWD, in order to login to db as sysdba, via OEM. And OEM doesn't support OS authentication, even when the OEM console, OMS and the db is residing in the same server.

Thank you, guys, I'm very grateful for all your help. You give me ideas on how to test. Received on Tue Jun 17 2003 - 05:29:07 CDT