Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: Don't Startup manager server ???
On Thu, 27 Dec 2001 18:23:03 +0800, "news.bentium.com"
<leizj_at_mginfotech.com> wrote:
>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.
>
The basic error here is ora-12154, which means your tnsnames.ora (in $ORACLE_HOME/network/admin) is incorrect. It has nothing to do at all with an absent listener and it has also nothing do with an absent reposiotory. You are getting VXA-2018 because you have ora-12154
Hth
Sybrand Bakker, Senior Oracle DBA
To reply remove -verwijderdit from my e-mail address Received on Thu Dec 27 2001 - 05:08:27 CST