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

KB221614: "Database error <5>: Catalog Get Tables failed.Error type: Odbc error. Odbc operation attempted: SQLTables..Driver not capable" error occurs when retrieving tables from a BigSQL database in MicroStrategy Web 9.4.1


Community Admin

• Strategy


This article outline an issue when retrieving tables from a database connection to BigSQL through IBM BigInsights during data import in MicroStrategy Web 9.4.1, the error returned is "Database error <5>: Catalog Get Tables failed"

SUMMARY:
This technical note describes an issue when retrieving tables from a database connection to BigSQL through IBM BigInsights during data import in Strategy Web 9.4.1.
 
SYMPTOM:
In Strategy Web 9.4.1, users receive the following error message when attempting to retrieve tables from a database connection to BigSQL through IBM BigInsights during data import:
 

ka04W000000OhDgQAK_0EM440000002JBI.jpeg

 


Database error <5>: Catalog Get Tables failed. Error type: Odbc error. Odbc operation attempted: SQLTables. [HYC00:-99999: on SQLHANDLE] [IBM] [CLI Driver] CLI0150E Driver not capable 

 
 
CAUSE:
This issue is due to the query sent from the BigSQL server being incompatible with ODBC version 3.x calls. This occurs because the older version of the BigSQL driver does not properly handle certain ODBC version 3.x calls.  
 
ACTION:
Upgrade to the latest version of the BigSQL driver that is supported with the corresponding version of Strategy.
 
WORKAROUND:
Switch the ODBC Version for the database instance to ODBC 2.0 calls, like shown below:
 

ka04W000000OhDgQAK_0EM440000002JBG.jpeg

 
NOTE: This workaround does have implications in terms of performance. The use of ODBC 2.0 fetch calls (sqlfetch and sqlextendedfetch) may have slower performance for larger reports than the OCBC 3.0 call (sqlfetchscroll).


Comment

0 comments

Details

Knowledge Article

Published:

May 30, 2017

Last Updated:

May 30, 2017