Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email firstname.lastname@example.org
RE: Analyzer error
From: Becker, Holger (holger.beckersap.com)
Date: Tue Apr 11 2006 - 03:16:45 CDT
Daniel Castro wrote:
> I dont have the source code.
> Is there any other way to do that?
> Any SQL monitoring tool?
> Best Regards
you could enable the diagnose monitor with the command
diagnose monitor read | time | selectivity <unsigned int>
After that you'll find the executed commands in the table SYSPARSEID
and the resource consumption for each command which exceed the given
threshold in the table SYSMONITOR.
The treshold given by the <unsigned int> have different meanings
on the three keywords read, time and selectivity.
Read stands for the amount of pages the command have to read,
time stands for the execution time in milli seconds and selectivity
for the rate of rows qualified / rows read.
If you set more than one threshold the command is inserted in SYSMONITOR
one threshold is exceeded.
The table SYSMONITOR will be cyclically overwritten. To adjust the
cycle size you could use the command
diagnose monitor rowno <unsigned int>
The maximum rowno is 9999.
With this join you will get the commands in descending order of their
select /*+ordered */
substr(sp.sql_statement, 1, 2000), sm.*
sysmonitor sm, sysparseid sp
sm.parseid = sp.parseid
I hope this will help you to find the problematic commands.
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb