Re: why my oem can't use service name?

Richard,

The problem you are having is with the TNSNAMES.ora file in the oem home. When you do discovery of a node, the information in the services.ora file on that node gets passed to eom. That's the information displayed in the Navigator window, and the service names for jobs and events. The tnsnames.ora file in your oem home doesn't have the same service name. It may be the .world if specified in the sqlnet.ora file, or just a uppercase/lowercase problem. If you use the menu option from OEM to update the configuration files, it should fix your problem. It will actually modify the tnsnames.ora file and make it contain ALL of the service information oem knows about from the discovery process.

Good Luck,
Marty

I also sent this to your personal e-mail address rongtao_at_my-deja.com wrote in message <7rp6g9$5ih$1_at_nnrp1.deja.com>...
>hi, there,
>
>every time I use service name in any oem 2.0.4 product, I got an ORA-
>12154 error: TNS: could not resolve service name. But besides oem
>product, the service name works perfect with other oracle products. also
>I test the service name in Net8 Assistant, and it is OK!! also I
>uninstall and reinstall the oem, I still got the same problem. without
>the service name support, I can't carry out some database management
>jobs. anybody has ran into this problem? if you have some idea, please
>email me.
>
>thanks in advance!!
>
>richard
>
>
>Sent via Deja.com http://www.deja.com/
>Share what you know. Learn what you don't.
Received on Thu Sep 16 1999 - 03:11:10 CEST