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

KB440206: "[Teradata Database] Object 'TH5FF8R15SP003' does not exist" error occurs when executing a partitioned cube with “Parallel Query Execution" enabled


Community Admin

• Strategy


This issue has been classified as a non-defect by MicroStrategy. The impact is limited to MicroStrategy product only with partitioned cube which has “Parallel Query Execution" enabled and Table Qualifier VLDB enabled. A solution for this issue is available in current release.

SYMPTOM:
 
 
In Strategy 10.x, "[Teradata Database] Object 'TH5FF8R15SP003' does not exist" error occurs when executing a partitioned cube which has “Parallel Query Execution" enabled as shown below:
 
(QueryEngine encountered error: Execute Query failed. Error type: Odbc error. Odbc operation attempted: SQLExecDirect. [42S02:-3807: on SQLHANDLE] [Teradata][ODBC Teradata Driver][Teradata Database] Object 'TH5FF8R15SP003' does not exist. Connection String: DSN=xxx;UID=MSTR;. SQL Statement: ;insert into TH5FF8R15SP003 select …. Error in Process method of Component: QueryEngineServer, Project Retail Prod A, Job 21319, Error Code= -2147212544.)
 
 
Refer to Technical Document below on how to enable "Parallel Query Execution":
KB44052 Feature in the Strategy SQL engine: "Parallel Query Execution".
 
 
 
CAUSE:
 
It is notice the create temp table and insert temp is different. 
The cube has 2 cube level VLDB settings:

  • set the "Create Post String" to “on commit preserve rows;"
  • set the "Table Qualifier" to "volatile multiset”.


 
Then the SQL will be:
                  create volatile multiset table T5K1CIHXYSP00G {
                  xxx
                  on commit preserve rows;
 
With the settings, it will create volatile multiset table T5K1CIHXYSP00G.
 
By design, the Parallel SQL Execution (PSE) feature can only use permanent tables. With the partition cube ("Parallel Query Execution" is enabled), the Query Engine changes the table type from temp table to permanent table, thus throws the error.
 
 
 
 
ACTION:
 
 
Remove the VLDB setting or make the cube as non-partition cube.
 
 
 
Article Reference Number: KB440206
 
  KB440206


Comment

0 comments

Details

Knowledge Article

Published:

March 21, 2018

Last Updated:

December 29, 2018