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