Managment Server problem [message #99471] |
Sun, 25 November 2001 14:19 |
JoJohn
Messages: 2 Registered: November 2001
|
Junior Member |
|
|
Hi.
I have following problem:
I have install Oracle8i. Create database. Create repository. There is no problems with database connection from DBS Studio in stand alone mode. But when I try to start Oracle Managmen Server error occure and following records in log file:
In WinNT:
OEMCTRL for Windows NT: Version 2.2.0.0.0
Copyright © 1998, 2000, Oracle Corporation.
All rights reserved.
Starting the Oracle Management Server...
[[main]][[2001-11-21:4:57:24:503]] VdbSession.processError: errorCode >3113<
[[main]][[2001-11-21:4:57:24:503]] VdbSession.processError: errorMsg >ORA-03113: end-of-file on communication channel<
[[main]][[2001-11-21:4:57:24:503]] VdbSession.processError: lost connection
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.
In Win2000:
OEMCTRL for Windows NT: Version 2.2.0.0.0
Copyright © 1998, 2000, Oracle Corporation.
All rights reserved.
Starting the Oracle Management Server...
[[main]][[2001-11-22:6:44:7:138]] VdbSession.processError: errorCode >12640<
[[main]][[2001-11-22:6:44:7:138]] VdbSession.processError: errorMsg >ORA-12640: Authentication adapter initialization failed<
[[main]][[2001-11-22:6:44:7:138]] VdbSession.processError: database connection error
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.
HELP ME PLEASE !!!!
Thanks.
----------------------------------------------------------------------
|
|
|
|
|
Re: Managment Server problem [message #99611 is a reply to message #99471] |
Fri, 25 January 2002 11:37 |
gina
Messages: 2 Registered: January 2002
|
Junior Member |
|
|
I had the same problem and I solved it by editing de configuration parameters of the repository and changing the pwd of sysman, just as follows:
Open enterprise manager configuration assistant and select the option: edit configuration parameters - Next
In the next screen it will show you the repository connection information already filled. If not or if you have more than one repository, type de username, newpwd of the repository user, and the service name of the database that has that repository (it has to be open).
Also check that you have enough processes allowed to run in this database because by starting OMServer it starts like 10 processes.
click next after you filled the information of this page. The repository is going to be reconfigured, if it tells you that it was successful, restart the service of Management Server, and it will start without any problems.
Hope it helps.
|
|
|
Re: Managment Server problem [message #99657 is a reply to message #99558] |
Thu, 07 February 2002 14:31 |
KG
Messages: 1 Registered: February 2002
|
Junior Member |
|
|
Yes, I believe the sqlnet.authentication is the real problem, I had the same problem and fixed it using sqlnet.authentication_services=(NONE)
|
|
|
|
|
|
Re: Managment Server problem [message #100376 is a reply to message #99471] |
Wed, 20 November 2002 14:38 |
Lorie
Messages: 2 Registered: November 2002
|
Junior Member |
|
|
Hello,
I have an Oracle 8i database on a Windows 2000 server, which has been running perfectly (up until now) The OracleOraHome81ManagementServer service will not start. It gives me the following error:
Could not start the OracleOraHome81ManagementServer service on Local Computer. Ther service did not return an error. This could be an internal Windows error or an internal service error. If the problem persists, contact your system administrator.
When I look at the oms.nohup log file, this is the error I'm getting:
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.
My sqlnet.ora contains the following line (which I have seen as a suggestion) :
SQLNET.AUTHENTICATION_SERVICES=(NONE)
I don't know if it has to do with the repository. And I don't understand why the repository allows you to change the username and password without the confirmation of the old password. I was on vacation when this occured, I had asked to see if anyone made changes to the server, database, usernames or passwords and the answer was "No".
Does anyone know if I can re-install the Oracle Management Server (OMS) and/or the repositiory without harming my existing Oracle database.
I'm new to Oracle and trying my hardest to figure this out, but I have been working on this issue for a couple of days now, and I'm confused.
Any suggestions or comment would be deeply appreciated.
Thank you very much,
Lorie
|
|
|
Re: Managment Server problem [message #100454 is a reply to message #99471] |
Mon, 06 January 2003 13:22 |
Lorie
Messages: 2 Registered: November 2002
|
Junior Member |
|
|
Do have a error message in your ome.nohup file like this:
"errorMsg > ORA-12541: TNS: no listener"
If the ans is yes.
Try to change your configure parameters. Use your
oracle service name in service input box, instead of the "<host>:<port>:<sid>"
|
|
|
Re: Managment Server problem [message #100536 is a reply to message #99471] |
Sun, 09 February 2003 12:53 |
Nirav
Messages: 2 Registered: February 2001
|
Junior Member |
|
|
I chaged SQL*NET entry to (NONE).
After that I am trying to start "OracleOraHome81ManagementServer" service then its reaching all the way and on last BAR on services start I am getting following error message.
"Could not start the OracleOraHome81ManagementServer service on local computer.
Error 1053 service did not respond to start in timely fashion"
Can help me what else I have do to start my management server so I can connect to OEM.
Thanks
|
|
|
|
|