Funny filter failure on select from sysmaster:syspools

Please excuse the alliteration. I was wondering if others on other platforms/versions/installations get the same result as that listed below. There seems to be no (specific) defect recorded. onstat -VInformix Dynamic Server 2000 Version 9.21.UC2 uname -a Linux 2.2.14-5.0 database sysmaster; select * from syspools; po_id po_address po_name po_class po_freeamt po_usedamt 1 268439584 resident 1 4472 573064 2 269017120 res-buff 1 4472 2051720 3 271200288 global 2 39304 4351608 4 271220768 mt 2 704120 1851784 5 271634464 smartblob 2 1304 2792 6 271638560 sbtlist 2 5600 6688 7 271650848 sb_delq 2 8424 20248 8 271753248 sb_delundoq 2 8424 20248 9 271855648 sb_lofd 2 8424 20248 10 271958048 sb_loheader 2 25944 236200 11 272293920 sb_arcspace 2 832 3264 12 272306208 rsam 2 2544 886288 13 272633888 aio 2 62208 425216 14 276787232 gls 2 5760 22912 ... etc select * from syspools where po_address > 0; No rows found. Filters for < and = produce the same. Brett Randall

> select * > from syspools > where po_address > 0;> > No rows found. > > Filters for < and = produce the same. I've seen this kind of thing on the XPS (8.x) server too. Range filters on "indexed" columns of SMI tables don't work very well. SMI tables are queries against memory, and the "indexed" columns (such as 'po_address' of 'syspools') don't have a real index on them, so range traversal through the "index" is not reliable. Only equality/inequality filters are useful on such columns. In the above case, "=" probably would have worked fine if there had been any such values, but po_address is unlikely to be Null (0). -cs Sent via Deja.com http://www.deja.com/