KB486745: Google BigQuery JDBC driver fails to connect when turning on the trace log

Symptom

The Google BigQuery JDBC driver may fail to connect if trace logs are enabled. This occurs when two applications/processes are running simultaneously and using the same log location. To resolve this issue, the applications/processes should use separate log locations. Otherwise, the driver will encounter problems with file renaming, file creation, and file opening, resulting in connection errors.
 

• Connect to Strategy Library or Workstation.
   
  
• Add a Google BigQuery JDBC connection to the data source with a

  loglevel=6.

  
   
  
• Add multiple tables and save. An "Unable to publish the cube" error occurs.
   
  

•  
  Sample Error Message:
   
  CITY_MNTH_SLS: We could not obtain the data because the database connection or the warehouse table has changed. Encountered error: JdbcResultWrapper::Fetch failed. Disconnected. Error type: Unknown exception. Jdbc operation attempted: FetchTable. Error Message:java.lang.NullPointerException: Cannot invoke "java.io.File.length()" because "this.m_currentLogFile" is null.
  

Solution

The driver vendor is considering adding a process ID to log filenames to differentiate the logs. However, this change would have a significant impact and cannot be implemented in the near future. To optimize driver performance, we recommend disabling trace logging. Generating logs can negatively affect performance and should only be used for testing or debugging purposes.