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

KB426499: “We could not obtain the data because the database connection or warehouse table is changed. Encountered error: IVEProcessHeadInfo failed.” Error Message is Returned When Publishing an In-memory Data Import Cube from Splunk Database


Community Admin

• Strategy


This knowledge base article describes an issue when publishing an In-memory data import cube from Splunk database that contains "_time" column/search. This issue has been classified as a defect by MicroStrategy. The impact is limited to using "Pick Tables" select import option in MicroStrategy Web 10.x. This article discusses workaround available in the current releases.

SYMPTOM:
When publishing an In-memory data import cube from Splunk database that contains "_time" column/search, the following error message might occur:

ka04W000000OallQAC_0EM440000002T0N.png


We could not obtain the data because the database connection or warehouse table is changed. Encountered error: IVEProcessHeadInfo failed. Error type: Data Import Error. Error occurs when processing the head info...”

CAUSE:
The issue is related to the underscore character in the column name. By default, Splunk adds this underscore before its time search index, but the Strategy engine cannot handle the underscore character in some scenarios. This is limited to the “Pick Tables” and "Build a Query" Data Import options which use the underscore in the column alias.
WORKAROUNDS:
​1. Use "Type a Query" in the select import option instead. By using "type a query", the generated SQL in the above data import cube is:
select b,
h,
host,
idx,
pool,
s,
st,
_time
from   [DMC License Usage Data Cube]; 
Note: No column aliases are used. This will get all columns including "_time".
 
2. Use "Build a Query" in the select import option and manually alter the column alias.
 
By using "Build a query", the generated SQL is:
select DMC_License_Usage_Data_Cube.b b,
DMC_License_Usage_Data_Cube.h h,
DMC_License_Usage_Data_Cube.host host,
DMC_License_Usage_Data_Cube.idx idx,
DMC_License_Usage_Data_Cube.pool pool,
DMC_License_Usage_Data_Cube.s s,
DMC_License_Usage_Data_Cube.st st,
DMC_License_Usage_Data_Cube.[_time] [_time] 
from [DMC License Usage Data Cube] DMC_License_Usage_Data_Cube;
Alter this statement to: 
select DMC_License_Usage_Data_Cube.b b,
DMC_License_Usage_Data_Cube.h h,
DMC_License_Usage_Data_Cube.host host,
DMC_License_Usage_Data_Cube.idx idx,
DMC_License_Usage_Data_Cube.pool pool,
DMC_License_Usage_Data_Cube.s s,
DMC_License_Usage_Data_Cube.st st,
DMC_License_Usage_Data_Cube.[_time] time
from [DMC License Usage Data Cube] DMC_License_Usage_Data_Cube;
Renaming the "_time" alias as "time" will resolve the issue.
3. Use Connect Live

ka04W000000OallQAC_0EM440000002Ubc.png

4. Rename or remove the underscore character in the “_time” column from Splunk before importing into Strategy.  
ACTION:
Currently this issue is being reviewed for feasibility by our Technology team and it is not scoped for any upcoming scheduled Strategy release.
  KB426499


Comment

0 comments

Details

Knowledge Article

Published:

June 27, 2017

Last Updated:

January 1, 2019