KB12340: Attribute IDs mapped to column with a datatype of raw result in inconsistent behavior in Microstrategy Developer 9.x

SYMPTOM:
Attributes with ID forms mapped to columns which are stored in an Oracle warehouse as datatype raw will manifest errors in varying ways. Some known effects are listed here.

• If the attribute is put on a grid report with only the ID form showing, the form mapped to the raw column will not display data even though the correct number of rows is returned, as shown below:
  

• If another form is displayed, that form will show data but the ID form will not, as shown below:
  

• Attempting to qualify on the attribute will result in the first element being replaced by a duplicate of the last item on the list, as shown below:
  

CAUSE:
The raw datatype is not intended for columns that require joins. This datatype should not be used for an attribute ID column. The raw datatype is intended to be used to store binary data or other kinds of raw data, such as a digitized picture or image. The difference between RAW and VARCHAR2 is that Oracle will not try to interpret raw data. Oracle will not perform character set conversions on raw data when it is moved from one system to another system.
 
ACTION:
The datatype should be changed to a numeric data type.