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

KB19646: 'Authorization Error Bind' error occurs when attempting to connect to a DB2 UDB database using the MicroStrategy ODBC driver for DB2 Wire Protocol


Community Admin

• Strategy


This KB addresses an error seen when attempting to connect to a DB2 UDB database using the MicroStrategy ODBC driver for DB2 Wire Protocol.

SYMPTOM:
Administrator has created a DSN via ODBC Data Source Administrator using Strategy ODBC Driver for DB2 Wire Protocol. When attempting to log in to database using Test ODBC tool, the following error is displayed:

ka04W00000148mVQAQ_0EM440000002JHz.gif


Error connecting to DSN:
Connect failed. Error type: Odbc error. Odbc operation attempted:
SQLDriverConnect. Optional feature not implemented.

Authorization Error Bind 
[Driver`s SQLSetConnectAttr failed.

 

CAUSE:
Required packages do not exist on the DB2 server and the User ID that connects to the DB2 Server does not have the appropriate privileges for the driver to create and bind these packages. These privileges are BINDADD for binding packages and GRANT for executing the packages.
Refer to the following Knowledge Base articles for details regarding package creation and binding for the Strategy ODBC Driver for DB2 Wire Protocol:

  • KB19382: Information regarding package creation and binding for the MicroStrategy ODBC Driver for DB2 Wire Protocol
  • KB19385: How to perform package creation and binding manually for the MicroStrategy ODBC Driver for DB2 Wire Protocol ​

 
ACTION:
Contact the Database Administrator (DBA) to give the above User ID. If the above User ID does not have these privileges, then a User ID with DBA privileges needs to create these packages by connecting with the driver. This connectivity with the latter User ID needs to be done just once, the very first time the driver attempts to connect to the DB2 server.
 
Refer to the above mentioned Knowledge Base articles (KB1100-000-0659 and KB1100-000-0660) for more details.
 
Third Party Software Installation:
WARNING:
The third-party product(s) discussed in this technical note is manufactured by vendors independent of Strategy. Strategy makes no warranty, express, implied or otherwise, regarding this product, including its performance or reliability.


Comment

0 comments

Details

Knowledge Article

Published:

May 16, 2017

Last Updated:

May 16, 2017