this issue was resolved by oracle support. the SR number associated with the
issue is:
5754547.993
if you want to see what they did. i still don't understand the cause but at least
it is working correctly now.
-- michael
On Fri, Sep 01, 2006 at 10:34:17AM -0700, saravanavijayan velu wrote:
> Hi Michael,
>
> Pls try theses as well.
>
> 1)stop the agent , enable agent trace ( how -> Refer doc id 229624.1
> <https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=229624.1>
> in metalink), rm agent-home/sysman/logs/* and start the agent
> 2)Review the emagent.trc, lookout for - lookout all ERROR and
TIMEOUT lines...
> 3)get strace with -f flag as well.
>
> Thanks
> Vijay
>
>
> Michael Galloway wrote:
> >here is what strace output looks like from:
> >
> >strace -p 5466 -o emagent.trace.out
> >
> >more emagent.trace.out
> >--- SIGSTOP (Stopped (signal)) @ 0 (0) ---
> >--- SIGSTOP (Stopped (signal)) @ 0 (0) ---
> >times(NULL) = -2136728721
> >times(NULL) = -2136728721
> >times(NULL) = -2136728721
> >times(NULL) = -2136728721
> >times(NULL) = -2136728721
> >times(NULL) = -2136728721
> >times(NULL) = -2136728721
> >times(NULL) = -2136728721
> >times(NULL) = -2136728721
> >times(NULL) = -2136728721
> >times(NULL) = -2136728721
> >times(NULL) = -2136728721
> >times(NULL) = -2136728721
> >times(NULL) = -2136728721
> >times(NULL) = -2136728721
> >times(NULL) = -2136728721
> >times(NULL) = -2136728721
> >times(NULL) = -2136728721
> >times(NULL) = -2136728721
> >times(NULL) = -2136728721
> >times(NULL) = -2136728721
> >times(NULL) = -2136728721
> >times(NULL) = -2136728721
> >times(NULL) = -2136728721
> >times(NULL) = -2136728721
> >times(NULL) = -2136728721
> >times(NULL) = -2136728721
> >times(NULL) = -2136728721
> >times(NULL) = -2136728721
> >
> >
> >does that continuously ...
> >
> >- michael
> >On Fri, Sep 01, 2006 at 08:54:06AM -0700, Saravanavijayan Velu wrote:
> >
> >>Hi Michael,
> >>
> >>Can you pls check on following ?
> >>
> >>
> >> * OH/sysman/logs/*.logs
> >> * trace the top process and check if it getting stuck somewhere...
> >>
> >>
> >>Thanks
> >>Vijay
> >>
> >>Michael Galloway wrote:
> >>
> >>
> >>>relink did not resolve it :-\ i do have a thread open on the oracle
> >>>forums:
> >>>
> >>>http://forums.oracle.com/forums/thread.jspa?threadID=418993&tstart=0
> >>>
> >>>-- michael
> >>>
> >>>
> >>>
> >>>
> >>>>-----Original Message-----
> >>>>From: Taylor, Michael D
> >>>>Sent: Thursday, August 31, 2006 2:19 PM
> >>>>To: 'Michael Galloway'
> >>>>Subject: RE: [suse-oracle] emagent runs at 100% cpu after patch update
> >>>>
> >>>>Have you already tried shutting everything down and doing a relink all
> >>>>
> >>>>from the Oracle Home? I have 5225798 CPU on 32 bit Suse 10.1 for 10gR2
> >>>
> >>>>and have had no problems.
> >>>>
> >>>>-Michael
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >
> >
>
--
To unsubscribe, email: suse-oracle-unsubscribe@(protected)
For additional commands, email: suse-oracle-help@(protected)
Please see http://www.suse.com/oracle/ before posting