Queries Using Simba ODBC Driver With Google Big Query Fail With nQSError 16011 ' Unable to read from file buffer.' And Creates Huge Temporary Files
(Doc ID 2030248.1)
Last updated on NOVEMBER 07, 2021
Applies to:
Business Intelligence Server Enterprise Edition - Version 11.1.1.7.181016 to 12.2.1.4.0 [Release 11g to 12g]Business Intelligence Suite Enterprise Edition - Version 11.1.1.7.181016 to 12.2.1.4.0 [Release 11g to 12g]
Information in this document applies to any platform.
Symptoms
Note: This is not a supported datasource for OBIEE which means there is no specific option in the metadata for it. Therefore, it must be configured as an ODBC Advanced datasource, with database feature settings customized. The connection pool has to use an ODBC driver, which is not supplied by Oracle
Per the Certification Matrix: ERP-Apps and Other Datasources tab > Generic ODBC
5. For 3rd party drivers not explicitly certified by Oracle, it is the customer’s responsibility to work with the 3rd party vendor to insure compatible and functional installation of the driver on the Oracle Business Intelligence Server.
You are using the following in your environment:
- Google Biq Query datasource - https://cloud.google.com/bigquery/third-party-tools
- Simba Big Query ODBC driver (note: this is a 3rd party driver) - https://www.simba.com/connectors/google-bigquery-odbc
Creating queries with small amounts of data creates huge temporary files.
In the OBI Server(nqsserver.log) log you may see:
You, potentially, may encounter an OBI Server (nqsserver) crash(es).
An excerpt from a session log shows an extremely large row size:
Execution Node: <<27278>> Projection, Close Row Count = 4000, Row Width = 524384 bytes [[
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |