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

KB10417: "Invalid Catalog SQL. Required column 'TAB_NAME' is missing. Please refer to online help for more information" error message appears when accessing the Warehouse Catalog against a Teradata warehouse in MicroStrategy Developer 9.4.1 and 10.x.


Stefan Zepeda

Salesforce Solutions Architect • Strategy


When accessing Warehouse Catalog in MicroStrategy Developer 9.4.1 and 10.x for a Teradata database, the following error is seen: "An error was detected while trying to read the warehouse catalog: Invalid Catalog SQL. Required column 'TAB_NAME' is missing."

SYMPTOM:
When accessing Warehouse Catalog in Strategy Developer 9.4.1 and 10.x for a Teradata database, the following error is seen:

ka02R000000kbwFQAQ_0EM440000002Ft5.gif

 


 


An error was detected while trying to read the warehouse catalog:
Invalid Catalog SQL. Required column 'TAB_NAME' is missing. Please refer to online help for more information

Do you want to modify the Warehouse Catalog Browser options to try solve this problem?
Please re-run the Warehouse Catalog Browser after you make your changes.
Entries similar to the following can be found in the DSSErrors.log:

1440:Invalid Catalog SQL. Required column 'TAB_NAME' is missing. Please refer to online help for more information

1484: Unexpected Error (Line no. 0, Number: 80041E00, Description: Invalid Catalog SQL. Required column 'TAB_NAME' is missing. Please refer to online help for more information , Source: DSSCatalogServer.DSSCatalogServer.1)

 
 
CAUSE:
This error occurs because the Teradata ODBC driver option "Disable Parsing" is selected for the Warehouse DSN.
 
ACTION:
To resolve this issue, uncheck the setting "Disable Parsing." This setting can be accessed as follows:

  • Open the ODBC Data Source Administrator.
  • Select the Warehouse DSN and click 'Configure.'
  • Click on the 'Options >>,' button, as shown below:
ka02R000000kbwFQAQ_0EM440000002FtB.gif
  • Under the Teradata ODBC Driver Options, uncheck the setting "Disable Parsing":
ka02R000000kbwFQAQ_0EM440000002Ft9.gif

NOTE: The option "Disable Parsing" is provided to users in order to enable/disable parsing of SQL statements by the ODBC driver. If the user is using Teradata specific SQL, then the SQL statements need not be parsed by the driver. If this option is checked, the driver does not parse the SQL statements. By default, this option is unchecked.
For use with Strategy, this option does not need to be checked. However, before changing the ODBC configuration, check with the DBA regarding whether unchecking this setting is a valid option.
 


Comment

0 comments

Details

Knowledge Article

Published:

June 5, 2017

Last Updated:

June 5, 2017