This content has been marked as final. Show 7 replies
Here's a list , what should be checked:
1. Verify the sid is present in oratab
2. Verify the database has a listener.
Start with the listener in the $TNS_ADMIN location and then move to the $OH of the database and finally other $OH's if present in the oratab.
Verify the listener.ora has no syntax problem. You can test this by running 'lsnrctl status <listener name>'.
Verify the listener is running and is listening for the database sid. You can test this by running 'lsnrctl services <listener name>'
If the database does not appear, restart the database and check again.
This is valid for UNIX systems, on Windows the registry is used instead of oratab.
I am looking at the oratab file in my primary database host machine. I see the following:
I verified that the listener is up and I also verified the following:
SQL> Select username, machine from v$session where username = 'DBSNMP' ;
This tells me that the agent is started and connected to my primary database. Please note that the agent I am talking about is the one running on the primary database host. Now my question, how do I check to see if the agent is communicating with the OMS that I installed the Grid Control and Repository?
check the agent home page, starting from the Grid Control homepage it is to be found under Management System ==> Management Services and Repository ==> Agents . On the Agents page you should see your installed agents, hopefully up and running. If you click on a agent tab, immediately the agent tries to communicate with the OMS.
If the communication is successfully established, a list of all observerd targets, including databases , is shown. If all this happens, on principle the communication works.
Additionally,check the account status of dbsnmp and sysman, they must be unlocked.
select username,account_status from dba_users where username in ('DBSNMP','SYSMAN'); must result in
Normally the status should be open, if necessary you have to change it:
alter user <username> account unlock;
Thank you so much for replying my earlier email. I went into Agents tab under Management System and I do not see any Agents. But when I issue http://macux3:1830/emd/main and http://macox4:1831/emd/main (Target Host) I am getting successful.
I went into Errors and I am seeing lots of errors that are similar to this one:
Thread: MetadataLoad http://macox4:1831/emd/main/:A0000000003.dat Failed to load A0000000003.xml because of errors; moving to errors directory, File name:/u01/app/oracle/product/10.1.0/oem/sysman/recv/A0000000003.xml
Do you think we should remove the agent from the Target host and Grid Control from grid machine and install it again?
I think, you are right, you should try to reinstall all components. It seems, there are some corruptions in your agent and/or Grid Control environment.
If you have a support contract with Oracle, you could ask directly the support staff for further and deeper investigation.
Hopefully this is the last question. Do you any specific steps to take to remove Agent and Grid Control?
1) stop the agent and OMS
2) use the OracleInstaller to remove agent and OMS
Theoretically it shouldn't be necessary, but I found out it is more reliable
3) delete completely the OMS and agent homedirectories from your disk(s)
On OTN I found step-by-step instructions, how to install and use Grid Control, maybe this is useful,too.