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 ...
this is what I got when I check the status of oms.
$ oemctrl status oms sysman/oem_temp
OEMCTRL for Solaris: Version 22.214.171.124.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%
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
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.
[QUOTE][i]Originally posted by james07 [/i]
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.