SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
02-27-2008, 08:38 AM
| ||||
| ||||
 Snapshot problem for dynamic-sql: zero cpu counters Problem: the snapshot output for dynamic SQL shows some SELECT statements executed many times but all three CPU counters (total/system/user) in the dynamic-sql-snapshot are zero, but most other SQL statements are correctly timed. Environment: DB2 v7.2 fp13 on AIX all 32-bit. At this site, a script executes once an hour which enables STATEMENT monitor switches, resets the counters, sleeps for a while and then performs db2 get snapshot for all on... One frequently executed SELECT statement always reports exactly zero for the Total Execution time/System Time/CPU Time, and that is the only such statement in the snapshot (all other SQL statements will show non-zero counters for the same elements). The specific SQL statement is a SELECT statement that usually returns a small number of rows (e.g. 0, 1 or less than a dozen or so rows in the result-set). The access-plan looks good, no scanning, correctly indexed. The query has run almost a million times over the past few months. The specific SQL statement is the first statement in a multi-statement distributed transaction (j2ee/jta/WAS4). Anyone know why DB2 dynamic-sql snapshot can have zero values for some SQL statements but not others ?      |
Linear Mode
