Not getting connected to OMS
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 4 of 4

Thread: Not getting connected to OMS

  1. #1
    Join Date
    Feb 2001
    Location
    Bombay,India
    Posts
    530

    Angry

    Hi Friends,
    I have got Oracle Management Server(OMS) running on Windows NT machine.I want to connect my Windows 95 Client machine to access the OMS server but it is not getting collected.
    OMS server and the agent is running on the Windows Nt server and when I sit on it I can use the OEM but I want to access the Enetrprise manager from Windows 95 client on which Oracle 8.1.7 client is loaded.
    Let me know how to configure my client and access the OEM.

    regards,
    Rohit Nirkhe,Oracle DBA,OCP 8i

  2. #2
    Join Date
    Oct 2000
    Location
    Saskatoon, SK, Canada
    Posts
    3,925
    One way to do this is to install OEM on your client system and access it. On otherwords you wouldn't require to create the OMS repository but you need to have the OEM to invoke the OEM. Provide the host name to where the OMS resides and establish a connection. Other way is to map your oracle home to the client machine and start accessing from there.

    BTW: did you provide the correct hostname to connect for the oemapp. Try giving the ip address instead of the host name.

    Sam



    [Edited by sambavan on 04-19-2001 at 11:17 AM]
    Thanx
    Sam



    Life is a journey, not a destination!


  3. #3
    Join Date
    Feb 2001
    Location
    Bombay,India
    Posts
    530
    Hi,
    On my machine (windows 95) client I have installed OEM 2.2 and it has an icon called Console.When I click on it I get the Oracle Management Console screen which asks for me the username,password and Management Server
    Our Management server or OMS is started on Windows Nt server and when I sit on that machine OEM is working fine.But when I try to connect from my Windows 95 machine it goes into a hang.Can u please tell me how I can configure my Windows 95 machine to get connected to the OMS on Windows Nt server.

    Regards,
    Rohit Nirkhe,Oracle DBA,OCP 8i

  4. #4
    Join Date
    Oct 2000
    Location
    Saskatoon, SK, Canada
    Posts
    3,925
    Does the NT lie in the firewall? If so it could be a problem. because OEM uses port #3339 or something to communicate. Secondly on the dos prompt try issuing

    ping your_nt_hostname

    and make sure that your 95 machine was able to talk to NT.

    now, if you have the oracle client on your 95 machine, check whether you have the tnsping normally present under
    $ORACLE_HOME/bin

    C:> tnsping hostname count

    Upto this point if you see o.k then it confirms that your system was able to establish connection to the server


    Now check your tnsnames.ora file under your client and make sure that they are o.k. Other wise, copy a tnsnames.ora file from a working system. Then invoke the sql to all the clients and see whether it is able to establish the connection. Then make invoke the oem console and give the username sysman and its corresponding password and it were a new installation it would be oem_temp and the fully qualified hostname and see whether it connects.


    Sam
    Thanx
    Sam



    Life is a journey, not a destination!


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width