Trying to access a Google BigQuery external table might result in an error if you are running SAS^® 9.4M6 (TS1M6) with Hot Fix H5A005 or H5A006 or with SAS^® Viya^® 2020.1.4. Here are some situations that might cause this issue to occur:

• Trying to open the table using SAS^® Studio Library Explorer.
• Trying to run code against the table using one of the following:
  • SET statement in a DATA step
  • running the CONTENTS procedure when using the SCANSTRINGCOLUMNS LIBNAME or data set option
  • running the SQL procedure with a SELECT * statement

The error that occurs might vary depending on exactly what you are doing and whether you are using SCANSTRINGCOLUMNS=YES LIBNAME or data set option. Some of the errors that have been seen are the following:

Trying to open the external table in SAS Studio Library Explorer generates a pop-up window with the following error:

Trying to run code against the external table might result in an error similar to the following:

The workaround, in some cases for code, is to use the FEDSQL procedure instead.

Operating System and Release Information

Viya on Linux: An update for this issue is available for SAS Viya 3.5. For instructions on how to access and apply software updates, see the Updating Your SAS Viya software section in the SAS Viya 3.5 for Linux Deployment Guide at

A fix for this issue for SAS/ACCESS Interface to Google BigQuery 9.42 is available at: