KB440315: Statistics is not getting logged into STG_IS_MESSAGE_STATS for bursting Subscription in MicroStrategy 10.3 Hotfix 2 and above

SYMPTOM
In Strategy 10.3 Hotfix 2, Statistics is not getting logged into STG_IS_MESSAGE_STATS for Bursting Subscriptions. Statistic is getting logged into STG_IS_REPORT_STATS.
 
Follow below steps to reproduce this issue:

1. Create a Bursting Subscription for Email
2. Run the newly created subscription
3. Check STG_IS_MESSAGE_STATS from DBQuery tool  

CAUSE
This is a known issue with Strategy 10.3 Hotfix2 and above.
The column CONTACTTYPE in table IS_MESSAGE_STATS/STG_IS_MESSAGE_STATS is TINYINT or NUMBER(3), depending on the database type. Normally the value list for CONTACTTYPE is from 1~31 so type TINYINT or NUMBER(3) is sufficient.
From manual Supplemental Reference for System Administrator:
IS_CONTACT_TYPE_ID Type of contact delivered to:
• 1: Contact
• 2: Contact group
• 4: Strategy user
• 5: Count
• 8: Strategy user group
• 10: LDAP user
• 31: (Strategy use only)
However when Bursting Subscriptions function is used, the value is 0x01000000(16777216) which exceeds the precision of TINYINT or NUMBER(3). Therefore, this data cannot be saved in the database. 
 
ACTION 
This issue has been fixed in Strategy 10.9 GA and 10.4 Hotfix 5. Upgrade to this version to take advantage of the fix.
Data type for CONTACTTYPE has been changed to INT or NUMBER(10).
WORKAROUND
Depending the database, users could manually extend the precision for CONTACTTYPE.
E.g.
for SQL server DB:
ALTER TABLE STG_IS_MESSAGE_STATS ALTER COLUMN CONTACTTYPE INTEGER;
ALTER TABLE IS_MESSAGE_STATS ALTER COLUMN CONTACTTYPE INTEGER;
for Oracle DB:
ALTER TABLE STG_IS_MESSAGE_STATS MODIFY CONTACTTYPE NUMBER(10);
ALTER TABLE IS_MESSAGE_STATS MODIFY CONTACTTYPE NUMBER(10);
 Article Reference Number: KB440315