Re: Newbie Question - Enterprise Manager

Peter,

The problem is that the OMS cannot find the repository. Using the Configuration Assistant, you tell the OMS how and were to log into the repository. You can use the Repository Manager to create the repository before using the config. assistant to connect. You should create a separate instance for your repository, because if the database that houses the repository goes down, so does the OMS, and OEM.

Marty

Peter Cheung wrote in message <37E69B58.4AB6B1CA_at_bratch.com>...
> I had no problem installing Oracle Enterprise v8.1.5 to my NT server
>sp5 machine (the installation created ORCL as the default instance, and
>I was able to connect the database using Net8 Easy Config with userid of
>'system' and password of 'manager' - I assume that means the TNSListener
>worked). Then I installed Enterprise Manager v2.0.4, and the
>installation went fine. After that, I rebooted the machine, the Oracle
>services were able to bring up with any problem, except Enterprise
>Management Server service. So I tried to start it by typing 'oemctrl
>start oms' to explicitly starting the service, but it failed with a
>following message in sysman\oms.log.0:
>
> [main][16:30:13:980] VdbSession.processError: errorCode >12154<
> [main][16:30:13:980] VdbSession.processError: errorMsg >ORA-12154:
>TNS:could not resolve service name<
> [main][16:30:13:980] VdbSession.processError: database connection error
>
>VXA-2018 :
>Unable to connect to OMS registry service
>ORA-12154: TNS:could not resolve service name
> [main][16:30:14:50]
>Error starting Oracle Management Server. ORA-12154: TNS:could not
>resolve service name
>
> Please help. Thx in advance.
>
Received on Mon Sep 20 1999 - 16:52:41 CDT