BWA 7.00: Incorrect data for attribute types DATE and TIME

June 30, 2009 at 10:37 am

[] [] [] [] [] [] [] [] [] [] [] [] []

  1. 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...
  2. 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...
  3. 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:...
  4. 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...
  5. ICF: Incorrect requests – data from virtual host ignoredSymptom If an invalid request is processed in the Internet Communication Framework, the data stored in the virtual host is ignored. As a result, the incorrect requests lead to the default SAP...
  6. Changing the default sorting attributeSymptom After a search, the default method of sorting is “Relevance” even though sorting by relevance is not possible here. Therefore, only a blank entry is permitted as the default value. Reason...
  7. Added support wof @WebServiceRef without ‘name’ attributeSymptom @WebServiceRef is used without ‘name’ Other terms WebServiceRef, web service client Reason and Prerequisites According to JAX-WS specification, @WebServiceRef doesn’t require ‘name’ attribute. The fix provides support for @WebServiceRef used without...
  8. Error in displaying multiple valued attribute in SearchSymptom Perform Search on documents/Records and provide the value to any of the multiple-valued attributes. The Search result is displayed with the wrong value [ the value of the previous attribute in...

Symptom

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 (index attribute flags ) getAggregateMeasures”
Other terms

BWA, BIA, Accelerator, wrong result, date, time, not implemented
Reason and Prerequisites

Prerequisite: SAP NetWeaver BW Accelerator Revision 50 or previous
Reason: Due to a programming error, a part of the implementation can give rise to incorrect results for a query if at least one attribute of type DATE or TIME is involved in the query.
Solution

Update to BWA Revision 51 and rebuild the BWA indexes for which the error occurs.
As aworkaroundyou can delete sparse compression for attributes of type DATE or TIME. Therefore download the attached zip file “unsparsifyDateTime.zip” and extract the files into a temporary directory on BWA filer. Afterwards in that directory execute command “python unsparsifyDateTime.py” to start deletion of sparse of all indexes of all cubes. Dependend on the number of indexes this script may run some minutes.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Leave a Comment