SAP Basis Tech Supports

Symptom

The index calls take a rather long time, and a lot of entries in the trace file TREXIndexServerAlert.trc are written.
Example for the error messages:
[2708] 2005-10-21 16:19:26.993 e attributes DateAttributeValue.cpp(00160) : DateAttributeValue::set() failed: 6931 attribute value is not a date or wrong syntax
[2708] 2005-10-21 16:19:27.013 e attributes SingleUpdate2.h(00593) : Additional info for previous 6931: index “1fs:q5c_tbut000en”, attribute “birthdt”, docid 1, value “00000000″

Reason and Prerequisites

Dates in the form “00000000″ or “” are not valid in TREX. Therefore an error message is written for each invalid entry. The writing of error messages is rather slow, and the trace file can get huge.
Solution
As of TREX 7.10:
By default, the parameter accept_long_all_zero_dates in TREXAttributes.ini, section [global] is set to “on”.
So TREX can accept dates in the form “00000000″. Internally they are stored as “0000″ (year 0000).
Dates in the form “” are not accepted by TREX.For older releases and for dates in the form “”:
Suppress the tracing of error messages of the TREX attribute engine.
In the configuration file TREXIndexServer. ini, section [trace], change “attributes = none”.
Note: The suppressing of error tracing is dangerous because important error messages might not appear in the trace, and error tracking is impossible then.