var sidebar_align = 'right';
var content_container_margin = parseInt('290px');
var sidebar_width = parseInt('270px');
Unanswered: Enterprise Manager console 220.127.116.11.0
Our DBA left the company without letting anyone know what the administrator password is for the Enterprise Manager Console. (we can’t reach him – not returning calls)
I can launch “stand alone” mode and login as sys or system without any problem.
However I cannot log into the Enterprise Manager Server with (sysman/oem_temp) I assume this was changed to “God knows what!?”
Is there any way to over ride or change this access?? Will I have to reinstall the console??
Here is a bizarre twist:
I can connect to the "stand alone" database as sysman/oem_temp….. go figa!?
Login as SYS
I wanted to know if one as a normal user could connect to the DB as a sys in the standalone mode ?
I would appreciate ur response, even though my question is on top ur yours.
Thanx and Regards
No I could not login STAND ALONE mode as sys (normal user) but I can as SYS or SYSTEM as (sysdba)
Have a great day!
SELECT DUH, HELLO
WHERE ANSWER = "IN FRONT OF FACE WHOLE TIME"
SORT BY HELLO
9i server 18.104.22.168.0 is in OraHome90 with OEM (22.214.171.124.0)
9iAS 126.96.36.199.0 is in OraHome90AS with OEM (188.8.131.52.0)
Two versions of OEM (AhhHa!)
The installation of 9iAS reinstalled the OEM Client resulting in the 184.108.40.206.0 client being upgraded to 220.127.116.11.0
OEM was never accessed via the 18.104.22.168.0 version so sysman/oem_temp had never been changed at all on that version.
OEM 22.214.171.124.0 - sysman password had been changed - and we found DBA's notes with the password.
I can now connect to the server as sysman with client and server 126.96.36.199.0 and “do it all” now...!!!
MORAL OF THE STORY:
OEM Server 188.8.131.52.0 is not compatable with OEM Client 184.108.40.206.0
...and they all lived happily ever after..