OEM connection problem.
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 9 of 9

Thread: OEM connection problem.

  1. #1
    Join Date
    Feb 2001
    Posts
    53

    Cool


    I know I had the OEM installed on the Solaris box with Oracle 8.1.6 SE.

    The guy that installed it with me, had created an account for oem sever connect login. which I don't remember, but in any case, I should be able to used sysman/oem_temp.

    I can't get connected at all. How can I tell if the server service is running? It doesn't used the listener does it?

    thanks, if you can point me to the right directions

  2. #2
    Join Date
    Feb 2001
    Location
    Chennai
    Posts
    17
    Hi James,

    Log in as SYS and try to change sysman password. Actually I didn't tried that But I think it will work

    Siva Kumar N.V
    PeopleSoft Architect

  3. #3
    Join Date
    Jun 2000
    Posts
    295
    Take a look at:

    [url]http://www.dbasupport.com/forums/showthread.php?threadid=6987[/url]

  4. #4
    Join Date
    Feb 2001
    Posts
    53
    Sivakuarn,

    I try doing that, but it tells me that user sysman does not exist??

  5. #5
    Join Date
    Oct 2000
    Location
    Saskatoon, SK, Canada
    Posts
    3,925
    Could you explain the setps that you did to conncet to the oem. Check whether you are able to use the sysman/oem_temp to see whether the oms is running.

    $oemctrl status oms sysman/oem_temp

    If you are successfull in connecting, you would be able to see the status of the oms. If it was down, try restarting it. If you encounter a problem check your process and kill launchOms and the next child .../jre process and then try restarting the oms. If you further encounter any problem, let me know I'll give to instructions to trouble shoot it.

    This status check will let you know whether the password was the oem_temp or it had been changed. The repository user name has no correlation to the oem user name and they both are independent.

    IF ther password was not oem_temp then, the worst case senario would be that to drop the repository and recreate one through emca. I hope at this point you don't have any jobs running through oem. IF that is the case, my suggestion would be to consult oracle support before you drop and recreate the repository through emca.

    LEt me know of the status, just curoius to know.

    Hope this would help you to configure things ...
    Sam
    Thanx
    Sam



    Life is a journey, not a destination!


  6. #6
    Join Date
    Feb 2001
    Posts
    53
    Sambavan,

    this is what I got when I check the status of oms.

    $ oemctrl status oms sysman/oem_temp
    OEMCTRL for Solaris: Version 2.1.0.0.0
    Copyright (c) 1998, 1999 Oracle Corporation. All rights reserved.
    /u01/app/oracle/admin/orb/resources.ora is not found!

    The Oracle Management Server on host [simba] is functioning properly.

    The server has been up for 0 00:00:03.295

    Target database session count: 0 (session sharing is off)
    Operations queued for processing: 0
    Number of OMS systems in domain: 1 (simba)
    Number of administrators logged in: 0
    Repository session pool depth: 15
    Repository session count: 7 in-use and 0 available, pool efficiency: 12%

    what does this mean?

  7. #7
    Join Date
    Oct 2000
    Location
    Saskatoon, SK, Canada
    Posts
    3,925
    O.K this confirms that you can access the with the sysman/oem_temp and the readings confirms that the OMS is active. Now can you connect to your OEM on the solaris box using

    $oemapp console &

    give the same user name and password and see whether you were able to get the console gui. Once you are sure about this
    then on the NT application, give this solaris box's host name and the same user name and password and try connecting to the solaris system. If that does not go through, do

    ping solaris_hostname.domain

    and see whether you are able to make connection to it. In the mean time, you got to be sure that you are running the same version of OEM as that of the solaris one.

    Let me know of if you have any problem.
    Sam
    Thanx
    Sam



    Life is a journey, not a destination!


  8. #8
    Join Date
    Jan 2001
    Location
    Vancouver, Canada
    Posts
    87
    [QUOTE][i]Originally posted by james07 [/i]
    [B]
    I know I had the OEM installed on the Solaris box with Oracle 8.1.6 SE.

    The guy that installed it with me, had created an account for oem sever connect login. which I don't remember, but in any case, I should be able to used sysman/oem_temp.

    I can't get connected at all. How can I tell if the server service is running? It doesn't used the listener does it?

    thanks, if you can point me to the right directions [/B][/QUOTE]

    Which version of OEM did you install ?
    sysman username as well as password is case-sensitive.
    This user is created in your database
    to findout user list.
    SELECT * FROM ALL_USERS;
    You can change sysman password in sqlplus as long as you are connected as "SYS" or system.

  9. #9
    Join Date
    Jun 2000
    Location
    Madrid, Spain
    Posts
    7,447
    just wanted to point out sysman is not a database user so it wont be shown in all_users

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