It looks like the management server is unable to connect to oem repository
...
Either the database/listener for the oem repository isn't running - or you
need to reconfigure the management server (create or reuse repository)
"news.bentium.com" <leizj_at_mginfotech.com> wrote in message
news:a0es9u$2vho$1_at_news.cz.js.cn...
> this is error of following:
>
> OEMCTRL for Linux: Version 2.2.0.0.0
> Copyright (c) 1998, 2000, Oracle Corporation. All rights reserved.
> Starting the Oracle Management Server...............
> Timed out trying to start the OMS.
> Please check the file
> /home/u01/app/oracle/product/8.1.7/sysman/log/oms.nohup for more details.
> Terminated
>
>
> In the /home/u01/app/oracle/product/8.1.7/sysman/log/oms.nohup file:
>
> Error starting Oracle Management Server. Starting the management server at
> Thu D
> ec 27 17:58:34 HKT 2001
> OEMCTRL for Linux: Version 2.2.0.0.0
> Copyright (c) 1998, 2000, Oracle Corporation. All rights reserved.
> Starting the Oracle Management Server... [main][2001-12-27:17:58:42:403]
> VdbSess
> ion.processError: errorCode >12154<
> [main][2001-12-27:17:58:42:403] VdbSession.processError: errorMsg
> >ORA-12154: T
> NS:could not resolve service name
> <
> [main][2001-12-27:17:58:42:404] VdbSession.processError: database
> connection er
> ror
>
> VXA-2018 :
> Unable to connect to OMS registry
> serviceoracle.sysman.vxn.VxnBootstrapException
> :
> at
> oracle.sysman.vxa.VxaAppServer.startServices(VxaAppServer.java:1353)
> at oracle.sysman.vxa.VxaAppServer.main(VxaAppServer.java:2547)
>
> Error starting Oracle Management Server.
>
>
> ples tell me how to ?
>
> thinks.
>
>
Received on Thu Dec 27 2001 - 04:51:49 CST
