EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB485440: “String data, right truncated” error is seen when the Platform Analytics Cube is published against a PostgreSQL warehouse with 'America/Buenos Aires' TimeZone setting in MicroStrategy 2021


Frederick Kellerman

Cloud Support Expert I • MicroStrategy


Symptom


When the Platform Analytics cube publishes against a PostgreSQL warehouse where the TimeZone parameter on the database is set to 'America/Buenos_Aires' an error like the following may be observed in the DSSErrors.log.
String data, right truncated. Error in column 6. Connection String: DSN=PLATFORM_ANALYTICS_WH;UID=mstr_pa;. SQL Statement: select    "fact_latest_cube_cache"."cache_id" AS "cache_id",
    "fact_latest_cube_cache"."cache_status_id" AS "cache_status_id",
    "fact_latest_cube_cache"."cache_size" AS "cache_size",
    "fact_latest_cube_cache"."historical_hit_count" AS "historical_hit_count",
    "fact_latest_cube_cache"."hit_count" AS "hit_count",
    "fact_latest_cube_cache"."last_update_timestamp" AS "last_update_timestamp",
    "fact_latest_cube_cache"."expiration_timestamp" AS "expiration_timestamp",
    "fact_latest_cube_cache"."iserver_instance_id" AS "iserver_instance_id"

Cause


PostgreSQL supports a column datatype of Timestamp With Time Zone or TSWTZ that stores a timestamp along with its respective time zone. The issue occurs when the following conditions are met:

  1. The timestamp data is fetched as the ODBC type SQL_VARCHAR 
  2. The timestamp data being fetched isn’t supported by this format. Such as having a value of 1899-12-29 22:43:12-04:16:48
  3. The warehouse session is Non-UTF8


The issue can be resolved by enabling the Fetch TSWTZ as timestamp setting the PLATFORM_ANALYTICS DSN or whatever DSN is used by the Platform Analytics Project on the I-server:

ka0PW0000000t7lYAA_0EM4W000004Z1Bc.jpeg

After enabling the setting restart the Intelligence Server for the change to take effect. 
 


Comment

0 comments

Details

Knowledge Article

Published:

April 1, 2022

Last Updated:

February 26, 2024