We are running MAXDB 7.5.0.23 on SUSE Linux 9.1 (64-bit) and have encoutered a strange problem where a query result is consistently ordered incorrectly. Here is the query:
SELECT INVENTORY_ITEM_ID, INVENTORY_ITEM_DETAIL_SEQ_ID, QUANTITY_ON_HAND_DIFF, AVAILABLE_TO_PROMISE_DIFF, ORDER_ID, ORDER_ITEM_SEQ_ID, SHIPMENT_ID, SHIPMENT_ITEM_SEQ_ID, WORK_EFFORT_ID, ITEM_ISSUANCE_ID, RECEIPT_ID, PHYSICAL_INVENTORY_ID, LAST_UPDATED_STAMP, LAST_UPDATED_TX_STAMP, CREATED_STAMP, CREATED_TX_STAMP FROM INVENTORY_ITEM_DETAIL WHERE (INVENTORY_ITEM_ID = '10005') ORDER BY INVENTORY_ITEM_DETAIL_SEQ_ID DESC If we change the WHERE clause and fitler on a different INVENTORY_ITEM_ID, the ordering is correct. Also, if we disable the index on INVENTORY_ITEM_ID, then the problem goes away. It seems like the index is corrupted or something. We also know that the ordering for INVENTORY_ITEM_ID 10005 was correct recently (earlier today) using the index and that there have been no visible server problems. Is this a known problem? Ryan
