Kbase P123238: SQL Result set is different when using the ORDER BY clause
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
27/04/2009 |
|
Status: Unverified
SYMPTOM(s):
Result set is different when using ORDER BY
When using the ORDER BY clause, the number of records returned is lower than expected.
FACT(s) (Environment):
A query ran without the ORDER BY clause returns the expected number of records.
The problem does not occur when adding an extra field in the SELECT clause
OpenEdge 10.1B
All Supported Operating Systems
OpenEdge 10.1B01 Service Pack
CAUSE:
Bug# OE00149071
CAUSE:
This bug has to do with what SQL does when the volume of records to be sorted is so large that it needs to write portions of the data to disk. Then some data are lost.
FIX:
Upgrade to OpenEdge 10.1B02 or later. If upgrading to OpenEdge 10.1B02 or later is not feasible, then use one of the following two workarounds:
1. Add an extra field to the SELECT clause.
or
2. Increase the SQLTempBuff database startup parameter to avoid writing data to disk. For example, this command sets the SQLTempBuff 50 MB:
proserve -SQLTempBuff 50000 -S 6760 testdb