Basis Errors and Solutions

BWA 7.00: Incorrect result for some FEMS queries

July 3, 2009 at 7:27 am

[Accelerator] [BIA] [BWA] [Data] [different] [incorrect] [incorrect string] [incorrect xml] [login incorrect] [result] [wrong]

BWA 7.00: Incorrect result for some FEMS queriesSymptom You encounter incorrect results for a BW query using FEMS logic Other terms BIA, BWA, Accelerator, wrong data, different result Reason and Prerequisites Prerequisites: SAP NetWeaver BW Accelerator Revision 51 or...
BWA 7.00: Incorrect result if query runs during commitSymptom You obtain incorrect query results but if you execute the query again the result is correct. Other terms BIA, BWA, Accelerator, wrong result, different, rollup, commit, changerun Reason and Prerequisites Prerequisites:...
BWA 7.00: Incorrect query result due to internal compressionSymptom You experience incorrect query results. Other terms BIA, BWA, Accelerator, different, wrong result, kidsel, inconsistent Reason and Prerequisites Prerequisites: SAP NetWeaver BW Accelerator Revision 51 or previousThe fact table index used...
BWA 7.00: Incorrect data for attribute types DATE and TIMESymptom You receive incorrect data for queries where the F-table has attributes of type DATE or TIME. You find the following entry in the trace of TREXIndexServer: “Attribute engine function not implemented...
BWA – Short dump when executing RSRV Consistency CheckSymptom When executing RSRV- or rsddbiamon2- Consistency Check program occurs short dump – COMPUTE_BCD_OVERFLOW . Other terms BWA index, BW Accelerator, Consistency Check, RSRV, AGGREGATE_ROW, COMPUTE_BCD_OVERFLOW Reason and Prerequisites The summation of...
Incorrect matches when using find_next( )Symptom If you use anchor characters, the methods find_next( ) and replace_next( ) of class cl_abap_matcher find additional, incorrect matches. Other terms Regular expressions, beginning of line, cl_abap_regex, match, regex, regexp Reason...
Where-used list incorrect for includesSymptom The where-used list for includes does not find all usage locations. Other terms WBCROSSI, SE38, where-used list Reason and Prerequisites This problem is caused by a program error. Solution Implement the...
NR: Number from incorrect year is usedSymptom You create an interval in a year-dependent number range, and an interval for a later year already existed before. For the interval that already existed before, a buffer was created in...

Symptom

You encounter incorrect results for a BW query using FEMS logic
Other terms

BIA, BWA, Accelerator, wrong data, different result
Reason and Prerequisites

Prerequisites:
SAP NetWeaver BW Accelerator Revision 51 or previousThe index for the F-table is not splitThe BWA OLAP index is located on a different TREX index server than the F-table indexYou are running a query that uses FEMS logic
Reason:Due to a programming error in an internal compression method, all the results are put into FEMS 0. This leads to an incorrect result set for the query.

Solution

Apply BW Accelerator Revision 52.
Workaroundfor BWA Revision 51 or previous:
In file TREXIndexServer.ini set the following parameter:
[olap]
min_merge_compress_results = 2000000000

To activate the change, you need to restart the TREX index servers.