Re: Enterprise Manager no database

From: Lore Leuneog <Lore.Leuneog_at_gmx.net>
Date: Sat, 25 Oct 2003 19:09:29 +0200
Message-ID: <bneacv$gqk$03$1_at_news.t-online.com>


Hello Daniel
 
Well, wan't force you to understand german any [Quoted] more. I sat the hole day with my xxx!-oracle server and this is where I'm now:
I rebuild the repository. So the OEM started again but still without showing the databases.
 
I found out (correct me if it's wrong):
The OEM needs only the agent to start (not the [Quoted] listener). The agent executes the script: network\agent\config\nmiconf.tcl if it starts up.
The script is reading listener.ora, and tnsnames.ora files and generates the agent\services.ora file. (It should read also from the oratab - file but I couldn't find this on my windows 2000 system.) The services.ora file is used by the OEM to generate the nodes when choosing "autodetect nodes...".
 
In my services.ora file is no entry for the databases, that's why databases aren't shown in the OEM Console. If I add something like:
SQLSRV_server.xyz.local = (oracle_sysman_database, server.xyz.local, ???)
The database node is shown in the OEM.
 
But: 1) I don't know the right syntax for the services.ora entry (->???). How does your oracle_sysman_database entry in services.ora look like???
 
2) Every documentation warns to edit the services.ora manually. So how can I convince my nmiconf.tcl to generate the right services.ora? (Some entries to add to listener.ora, and tnsnames.ora ???)
 
Do you've got any hints???
Thank you very much
Sincerely
Lore
 
P.S. Are you a chemistry professor in washington???
 
"Daniel Morgan" <damorgan_at_x.washington.edu> schrieb im Newsbeitrag news:1067097431.237048_at_yasure...
Lore Leuneog wrote:
Hello Daniel
 
This morning the Enterprise Manager didn't show up anymore. I think it was because the Management Server wasn't started. The databases were started. I tried to start the OMS manually. But the error-log I got was (see below). Which file does the OMS get the username/password from? Tank you. Sincerely Lore
 
*ERROR LOG**************************************
Fehler beim Hochfahren von Oracle Management Server. oemctrl für Windows NT: Version 2.2.0.0.0
Copyright (c) 1998, 2000, Oracle Corporation.  Alle Rechte vorbehalten.
Oracle Management Server wird hochgefahren... [main][2003-10-25:12:58:21:234] VdbSession.processError: errorCode >1017<
 [main][2003-10-25:12:58:21:234] VdbSession.processError: errorMsg >ORA-01017: invalid username/password; logon denied
<
 [main][2003-10-25:12:58:21:234] ORA-01017: invalid username/password; logon denied
: ..../...._at_jdbc:oracle:oci8:_at_
 [main][2003-10-25:12:58:21:234] VdbSession.processError: invalid connect string
 
VXA-2018 :
Anmeldung bei OMS-Registrierungsdienst nicht möglichoracle.sysman.vxn.VxnBootstrapException:
 at oracle.sysman.vxa.VxaAppServer.startServices(VxaAppServer.java:1353)
 at oracle.sysman.vxa.VxaAppServer.main(VxaAppServer.java:2547)
 
*******************************************************
The only German I can read is chemical literature so some of this is outside of my ability
to read ... but you are supposed to be supplying the valid userid and password. Which
leads to the question of what you are doing to start it and what userid and password you
are supplying.

The default userid and password is: SYSMAN and OEM_TEMP. And they should still
be that unless you changed them.
-- 
Daniel Morgan
http://www.outreach.washington.edu/ext/certificates/oad/oad_crs.asp
http://www.outreach.washington.edu/ext/certificates/aoa/aoa_crs.asp
damorgan_at_x.washington.edu
(replace 'x' with a 'u' to reply)
Received on Sat Oct 25 2003 - 19:09:29 CEST

Original text of this message