Home » Infrastructure » Other Operating Systems » OEM 2.1 on NT and Oracle 8.1.7 on OS/390
OEM 2.1 on NT and Oracle 8.1.7 on OS/390 [message #113624] Thu, 01 February 2001 12:42 Go to next message
Subhash Roy
Messages: 24
Registered: January 2001
Junior Member
The Oracle Management Server (OMS) won't start in the
Services in the control panel. The SQL*Net and the
Oracle database are running ok on the OS/390. The new
repository is on the OS/390 also and in the TEMP
segment in the USERS tablespace. This is for test only
before we'll use the existing repository on the NT,
which will eventually replace the OEM 1.3.5. Also, We
tried the standalone DBA studio and clicked on the
database in the instance navigator tree with no luck.
Any body experienced this kind of problem before?
Please note that the OEM Intelligent Agent/Gatherer is
not up or operastional yet. But, can't we test the
database connection with the standalone DBA studio?
Your help will be appreciated.
Thanks,
Subhash
Re: OEM 2.1 on NT and Oracle 8.1.7 on OS/390 [message #113629 is a reply to message #113624] Thu, 08 February 2001 08:51 Go to previous message
Subhash Roy
Messages: 24
Registered: January 2001
Junior Member
: The Oracle Management Server (OMS) won't start in the
: Services in the control panel. The SQL*Net and the
: Oracle database are running ok on the OS/390. The new
: repository is on the OS/390 also and in the TEMP
: segment in the USERS tablespace. This is for test only
: before we'll use the existing repository on the NT,
: which will eventually replace the OEM 1.3.5. Also, We
: tried the standalone DBA studio and clicked on the
: database in the instance navigator tree with no luck.
: Any body experienced this kind of problem before?
: Please note that the OEM Intelligent Agent/Gatherer is
: not up or operastional yet. But, can't we test the
: database connection with the standalone DBA studio?
: Your help will be appreciated.
: Thanks,
: Subhash

: Lesson learned - after the OEM 2.1 install, we can add as many databases in the tnsnames file as they
: are known on the network and start the DBA Studio. But, it's a limited functionality. The Intelligent
: Agent/gatherer once set up on the remote node will enable the Oracle management Server (OMS) to
: discover the nodes and to automatically create the database connect information in the tnsnames files
: for us.
Previous Topic: Conversion FORMS to VB
Next Topic: 14th Annual MVS Oracle SIG last chance
Goto Forum:
  


Current Time: Sun Jan 17 13:59:25 CST 2021