pratz09
asked on
Enterprise Manager console for oracle 11g on windows server 2008
Hey !
I installed Oracle 11g R2 on virtual server with windows server 2008 on it. The installation went fine, global database xyz was created on domain and a URL to access Enterprise Manager for xyz instance was created. I was able to open the link. But when I go to "Database instance: xyz" section, it says database instance is open, but the listener is unavailable and agent connection to instance failed. (ORA-12541)
I fired command lsnrctl and checked the status - which is "started". but the service instance is "CLRExtProc". I am not sure, but shouldn't it be xyz ? If yes, then how to change it ?
I also want to change the port number of Listener from default to something else. Is there anything I need to do in addition to editing Listener.ora file ?
My ultimate aim is: After configuring Database (listener port, etc), I want the database to be accessed by people using client EM from their local machine after login to VPN of my organization. I have scripts to create logins for the users. What else do I need to do to enable remote login to the database xyz.
Lastly, I am used to of using the traditional OEM (stand alone application which used to come with 10g). Can I use it in 11g or is the web based OEM the only option ?
Thanks a lot.
I installed Oracle 11g R2 on virtual server with windows server 2008 on it. The installation went fine, global database xyz was created on domain and a URL to access Enterprise Manager for xyz instance was created. I was able to open the link. But when I go to "Database instance: xyz" section, it says database instance is open, but the listener is unavailable and agent connection to instance failed. (ORA-12541)
I fired command lsnrctl and checked the status - which is "started". but the service instance is "CLRExtProc". I am not sure, but shouldn't it be xyz ? If yes, then how to change it ?
I also want to change the port number of Listener from default to something else. Is there anything I need to do in addition to editing Listener.ora file ?
My ultimate aim is: After configuring Database (listener port, etc), I want the database to be accessed by people using client EM from their local machine after login to VPN of my organization. I have scripts to create logins for the users. What else do I need to do to enable remote login to the database xyz.
Lastly, I am used to of using the traditional OEM (stand alone application which used to come with 10g). Can I use it in 11g or is the web based OEM the only option ?
Thanks a lot.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You really should ask a single question per question.
Please take some time to review the Help pages for how EE works.
https://www.experts-exchange.com/help.jsp#hs=23&hi=23
>> but the listener is unavailable and agent connection to instance failed.
From a command prompt on the database server post the results of:
lsnrctl status
Please take some time to review the Help pages for how EE works.
https://www.experts-exchange.com/help.jsp#hs=23&hi=23
>> but the listener is unavailable and agent connection to instance failed.
From a command prompt on the database server post the results of:
lsnrctl status
ASKER
Sorry ! My Bad. I never thought about it like that. Won't repeat.
ASKER
I opened the Em web link after fresh installation, when I go to "Database instance: xyz" section, it says database instance is open, but the listener is unavailable and agent connection to instance failed. (ORA-12541)
I fired command lsnrctl and checked the status - which is "started". but the service instance is "CLRExtProc". I am not sure, but shouldn't it be xyz ? If yes, then how to change it ?
Secondly, I want the database to be accessed by multiple remote users. How to enable that ? I cannot see client software for 11g on Oracle website, is it like the remote users can hit the database instance with the same URL I am accessing it ? As of now, when I am opening the URL from another workstation in the same network, it is not opening.