cancel
Showing results for 
Search instead for 
Did you mean: 

SAP BO 4.2 SP8 - Impala Connectivity issue

mr1925
Explorer
0 Kudos

Hi All, Getting the below mentioned error when trying to run webi report based on universe (unx) which is using the Cloudera Impala database connection.

Application Landscape : SAP BO 4.2 SP8

RHEL OS version : 7.8

Cloudera Impala odbc middleware version : 2.5.39

The following database error occurred: [unixODBC][Cloudera][ImpalaODBC] (100) Error from the Impala Thrift API: SASL(-1): generic failure: GSSAPI Error: A supplied name was of an unsupported type (OK). For information about this error, please refer to SAP Knowledge Base Article 2054721 on the SAP Support Portal. (IES 10901) (Error: INF WIS 10901)

The ODBC configurations:

Description=Cloudera Impala ODBC Driver (64-bit)

[Impala-DSN]

Host=bigdata

Port=21051

Driver=/opt/cloudera/impalaodbc/lib/64/libclouderaimpalaodbc64.so

SSL=1

AllowSelfSignedServerCert=1

AuthMech=1

KrbRealm=<REALM>

KrbFQDN=<_HOST>

KrbServiceName=impala

UseKeytab=1

UID=<bigdata>

UPNKeytabMappingFile=<Install_DIR>/enterprise_xi40/bigdata.json

Tried the below things.

1.Establish the connection from Local IDT Middleware - Successful.

2.Establish the Impala DSN connection from isql in Business Objects Linux Server - Successful.

3.Checked Connection metrics whether Simba impala ODBC is loaded or not - Loaded.

But it is not working from Business Objects Linux server.

Can you please help us to fix the issue.

Thanks,

Chinnu

Accepted Solutions (0)

Answers (1)

Answers (1)

denis_konovalov
Active Contributor
0 Kudos

the error comes from the DB, the DB DBA should review and advice on why

mr1925
Explorer
0 Kudos

Its working in BO 4.2 Sp2 environment.Not working in BO 4.2 SP8 after the upgrade.

This is the error log

Oct 05 04:08:42.950 INFO 4294178560 Simba::KerberosSupport::KSKinitSupport::Kinit: User principal is: <bigdata>. Oct 05 04:08:42.950 INFO 4294178560 Simba::KerberosSupport::KSKinitSupport::Kinit: Obtaining TGT. Oct 05 04:08:43.483 DEBUG 4294178560 Simba::ThriftExtension::TETSaslClientTransport::TETSaslClientTransport: sasl auth mech: 0 Oct 05 04:08:43.483 DEBUG 4294178560 Simba::ThriftExtension::TETSaslClientTransport::TETSaslClientTransport: The SASL layer had already been initialized by a previous connection attempt. Oct 05 04:08:43.483 DEBUG 4294178560 Simba::ThriftExtension::TETSaslClientTransport::TETSaslClientTransport: Using SSPI: false Oct 05 04:08:43.483 DEBUG 4294178560 Simba::ThriftExtension::TETSaslClientTransport::TETSaslClientTransport: SASL_CB_LOG added Oct 05 04:08:43.483 DEBUG 4294178560 Simba::ThriftExtension::TETSaslClientTransport::TETSaslClientTransport: SASL_CB_AUTHNAME added Oct 05 04:08:43.483 DEBUG 4294178560 Simba::ThriftExtension::TETSaslClientTransport::TETSaslClientTransport: SASL_CB_GETREALM added Oct 05 04:08:43.483 DEBUG 4294178560 Simba::ThriftExtension::TETSaslClientTransport::TETSaslClientTransport: SASL_CB_GETOPT added Oct 05 04:08:43.483 DEBUG 4294178560 Simba::ThriftExtension::TETSaslClientTransport::TETSaslClientTransport: SASL_CB_LIST_END added Oct 05 04:08:43.483 DEBUG 4294178560 Simba::ThriftExtension::TETSaslClientTransport::TETSaslClientTransport: +++++ exit +++++ Oct 05 04:08:43.557 INFO 4294178560 Simba::ThriftExtension::TETSaslClientTransport::SaslLoggingCallback: Realm callback found. The realm returned was: <Domain> Oct 05 04:08:43.595 INFO 4294178560 Simba::ThriftExtension::TETSaslClientTransport::SaslLoggingCallback: Kerberos principal: <Service Name>/<FQDN>@<Domain> Oct 05 04:08:43.595 DEBUG 4294178560 Simba::ThriftExtension::TETSaslClientTransport::SaslLoggingCallback: GSSAPI Error: A supplied name was of an unsupported type (OK)

denis_konovalov
Active Contributor
0 Kudos

and yet, it is still a DB error.

denis_konovalov
Active Contributor
0 Kudos

and points to authentication problem.