Oracle Intelligent Agent produce many defunc processes

[H.J. Zintl]

hello
I had installed Oracle Intelligent Agent (Version 9.2.0.2) in an different ORACLE_HOME, different user/group as the ORACLE_HOME of the database. For this case I change the owner,group and permissions of dbsnmp-binary (chmod 6751 dbsnmp, chgrp dbsnmp).
After registering some event monitors - like database updown, listener updown, tablespace full and so on - Oracle Intelligent Agent produce manny defunc-processes. I had 10 installations of intelligent agent on different maschine and all show the same behavior.

Regards
hans juergen

[Yogeeraj_1]

hi,

this information is from Metalink.


Relink the Oracle Intelligent Agent and set the ownership and permission, Then restart the agent by performing the following actions:

1) Log on as oracle.

2) cd $ORACLE_HOME/network/lib
make -f ins_oemagent.mk install

Make sure it relinks without errors.

3) If so, then log in as root and rerun "root.sh" or manually do:

cd $ORACLE_HOME/bin
chown root dbsnmp
chmod u+s dbsnmp

4) Then log back in as oracle and do:

lsnrctl dbsnmp_start

Back on the console side, try a Navigator/Service Discovery/Refresh Services and make sure that agent can be contacted again.

If the job or event system for some reason doesn't work, try:

1) Remove all registered events and pending jobs from the console.

2) Clear job history.

3) On server:

Stop the agent
cd $ORACLE_HOME/network/agent
rm *.q and services.ora
cd $ORACLE_HOME/network/admin
rm snmp*.ora
cd $ORACLE_HOME/network/log
rm dbsnmp*.log and nmi*.log

4) And restart agent one more time. Refresh the agent from console.



hth
Yogeeraj

[T G Manikandan]

It is a bug 879208

check the attachment

[H.J. Zintl]

hi,
in your attachment it refer to version 8.1.5. Is it also related for 9.2 Intelligent Agent.
Bug 879208 and 893151 are not public so I coudn't get the info.

Ciao
hans juergen

[H.J. Zintl]

hi Yogeeraj,
I had relink the agent software without errors, but the same behavior.

Thanks alot
hans juergen

[H.J. Zintl]

Hi T G Manikandan
it is a new bug in 9.2.0.2.
See bug 2697921
the workaround is to disable Oracle Net UpDown job
the problem would be fixed in 9.2.0.3.0 patchset.
Ciao
hans juergen