we installed the ODBC Dremio Driver on SAP Business Intelligence 4.2 SP5 on Linux RH 7.3 server.
Is this configuration supported by Dremio?
When we try to run a query on Dremio from SAPBI, we note the following error on the logs:
(…)v7QDIeFFUPKrJXRy9eyjQkf5ce|||||Administrator||||||google:: protobuf said: This program requires version 2.5.0 of the Protocol Buffer runtime library, but the installed version is 2.2.0. Please update your library. If you compiled the program yourself, make sure that your headers are from the same version of Protocol Buffers as your link-time library. (Version verification failed in “/home/employee/Desktop/Rob/drill/drill-1.10.0.4/contrib/native/client/src/protobuf/ExecutionProtos.pb.cc”.) (…)
Making some investigation, we found that SAP BI probably use a different libprotobuf version library, while Dremio seems to require 2.5
Has anyone ever experienced this? Is it possible to circumvent this problem?
Hi superbstreak,
there’s no proto package installed with yum on the servers, but I note there’s a library copied by Sap Business Intelligence installation at the path
Regarding Dremio driver installation, we did the following steps:
–>rpm -i dremio-odbc-1.3.14.1043-1.x86_64
–>we copied the content of /opt/dremio-odbc/lib64
into
/opt/sapbi/sap_bobj/enterprise_xi40/linux_x64/odbc/lib/dremio
–> to make dremio driver shared libs available to SAP BI runtime, this path is then added to the LD_LIBRARY_PATH variable of the user which runs SAP BI services
–> then we did a Sap BI service Restart
I was able to find the protobuf library files you mentioned on both Windows and RHEL installation of IPS. And verified both to be of version 2.2.0. I wonder if this is reproducible on Windows as well.
I’m going to do an switch from IPS (a subset of BI) to BI, since it looks like IPS does not have the capability to utilize an external ODBC connector as of 4.2.
have you found any bypass? We still can’t connect to Dremio
Do you think that using jdbc connection ma be an easier way to connect ?
We could give it another try if jdbc connection is supported or known to work with SAP BI on linux
Hi Sergio, Apologies for the delay, we’re looking into a possible workaround of shading protobuf libraries to resolve this issue while the team completes the switch from IPS to BIP.
You mentioned that you’ve tried the JDBC driver before but encountered a connection issue. Could you provide more detail regarding that?
Today we re-tried to configure a working JDBC connection using SAP BI but we didn’t succeed in making progress. We noted the following exception on Sap BI log:
ERRORCODE=“10901” ERRORTYPE=“USER” MESSAGE=“Si verificato il seguente errore di database: (CS) “Java Exception : java.lang.NullPointerException: while trying to invoke the method cdjd.com.typesafe.config.impl.MergeableValue.toFallbackValue() of a null object loaded from local variable ‘mergeable’” Per informazioni sull’errore, fare riferimento all’articolo della SAP Knowledge Base 2054721 nel SAP Support Portal. (IES 10901)” PREFIX=“ERR”
We used dremio-jdbc-driver-2.0.1rc-201804132205050000-10b1de0.jar
Is there any way to configure a higher debug level for the jdbc driver?
Regards,
Sergio
Hi @seraus, after some investigation regarding the protobuf 2.2 and 2.5 conflict issue, it looks like shading the protobuf library would be quite complex and would not the recommended solution. I’m recompiling the protobuf library again and ensuring the enable shared flag is properly picked up and turned off. I believe this should be able to help with the version conflict.
Regarding the JDBC Driver error, would it be possible to acquire the stacktrace of the NPE. Could you provide the setup process you’ve attempted? The SAP support portal KB 2054721 doesnt provide much information, only mentioned that these are the frequent causes:
Reporting database drivers not loaded or found
An error returned by the reporting database indicating a connection or other system issue
Network connectivity between the BI server and the reporting database
we configure Dremio driver as a “Generic JDBC Driver” following the instructions in the paragraphs 5.3.1 & 5.3.4 of the Data Access Guide.
We use the attached jdbc.sbo file; jdbcClass and jdbcURL are provided when creating the server connection (that is from the connection wizard of BI).
I’m recompiling the protobuf library again and ensuring the enable shared flag is properly picked up and turned >>off. I believe this should be able to help with the version conflict.
Let me know when you have a new build of the driver, I can make another attempt with ODBC
Hi @seraus, I would like to provide a quick update on this. We’ve successfully recompiled the protobuf library with the shared flag disabled as well as the rest of the related components. We should be able to verify the workaround shortly.
have you got a chanche to recompile the ODBC driver e verify the workaround?
I saw that there’s a new minor build of the ODBC driver…
Let me me know if there is any news
We have just heard back from SAP and setup a BI P for testing on Windows and RHEL. However, we are seeing an issue where exporting additional LD_LIBRARY_PATH would cause the core services to be shutdown due to a critical error in CMC. I was wondering if you’ve experience something similar before in your setup?
Would you mind verify the following steps:
Install the SAP BOBJ BI Platform server on RHEL
Install Dremio Connector
move the dremio connector to /opt/sapbi/sap_bobj/enterprise_xi40/linux_x64/odbc/lib/dremio
Modify the odbc.ini within the /opt/sapbi/sap_bobj/enterprise_xi40/…/odbc.ini file
yes, these are the steps we made when we installed Dremio ODBC driver. We never experienced a critical error on reboot (and we restarted SAP BI several times)
