Re: Gathering EXTREME amounts of time in %sys CPU

Greg, I don't mean to downplay any of what you said, but if you notice, this situation results in a complete lockup. We have to push the dump switch to get it going again. I consider that a "problem". Thanks for the response though. Grek Staska also followed up, and our DBA, Carlos Bolden, e-mailed Greg the incident number, etc. So we will keep pushing on as many channels as we can. Richard Doug Reiland wrote in message ... >The kernel profiler may be used to isolate the "problem". It may not be a >problem, but a workload issue. Anyway, the prfld, prfstat,prfsnap, etc... >can be used to find out what areas the kernel is spending time in. This is >usually not task for an end user and usually requires assistance from NCR >support. > >Doug

Per our emails the incident has been received and NCR Support is increasing activity on the problem. Richard Thomas wrote: > > Greg, I don't mean to downplay any of what you said, but if you notice, > this situation results in a complete lockup. > > We have to push the dump switch to get it going again. I consider that > a "problem". > > Thanks for the response though. Grek Staska also followed up, and our DBA, > Carlos Bolden, e-mailed Greg the incident number, etc. So we will keep > pushing on as many channels as we can. > > Richard > > Doug Reiland wrote in message ... > >The kernel profiler may be used to isolate the "problem". It may not be a > >problem, but a workload issue. Anyway, the prfld, prfstat,prfsnap, etc... > >can be used to find out what areas the kernel is spending time in. This is > >usually not task for an end user and usually requires assistance from NCR > >support. > > > >Doug