KB204738: An error message "ORA-01704: string literal too long" occurs in the DSSErrors.log when logging information into statistics tables on an Oracle database in MicroStrategy Intelligence Server 9.x and 10.x

SUMMARY
This issue has been classified as a defect by Strategy. The impact of this issue is limited to Statistics tables on an Oracle database and when the data exceeds the 4000 character limit on some columns in the statistics tables. A solution/code fix for this issue is not available in current releases but will be made available for the upcoming Strategy release.
 
SYMPTOM
In Strategy Intelligence Server 9.x and 10.x statistics are not logged to certain database tables and an error message similar to the following is seen in the DSSErrors.log:

[Database Classes][Error] Execute Query failed.

Error type: Odbc error. Odbc operation attempted: SQLExecDirect. [HY000:1704: on SQLHANDLE] [Strategy][ODBC Oracle Wire Protocol driver][Oracle]ORA-01704: string literal too long Connection String: DSN=XXXXX;UID=XXXXX;HOST=XXXXX;PORT=XXXXX;SID=XXXXX;. SQL Statement: insert into IS_PR_ANS_STATS ...

  
Columns like PROMPTANSWER in IS_PR_ANS_STATS and ERRORMESSAGE in IS_REPORT_STATS have a 4000 byte limit. When the data being inserted exceeds this limit, an error message is received.
 
Note: For Oracle, the Intelligence Server truncates data in the IS_PR_ANS_STATS > PROMPTANSWER column to 4000 characters while generating the INSERT statement. However, some unicode characters can take more than 1 byte and thus result in the 4000 byte limit on the column getting exceeded.
 
CAUSE
This is a know issue in Strategy Intelligence Server 9.x Statistics logging.
Strategy will continue to investigate and post updates as soon as they are available.
ACTION
Currently this issue is being reviewed by Strategy for a potential code fix on an upcoming Strategy release.
 
 
 
The Strategy Internal Reference Number for the issue discussed in this technical note is 814124.