Problem Note 67739: The message "panic: runtime error" occurs if you do not include the SCHEMA= option in a LIBNAME statement when accessing a Google BigQuery database
When you try to access a Google BigQuery database via a LIBNAME statement, an error similar to the following might occur:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x7f7132d86441]
goroutine 17 [running, locked to thread]:
cloud.google.com/go/storage.(*Client).Close(...)
/go/pkg/mod/cloud.google.com/go/storage@v1.8.0/storage.go:154
main.gbqgoFreeHandle(0x4, 0x7f7157dc3be0, 0xc8, 0x80)
/home/sdsci/access-bigquery/bigquery/connect.go:277 +0x71
main._cgoexpwrap_c6e24a2f0a30_gbqgoFreeHandle(0x4, 0x7f7157dc3be0, 0xc8, 0x0)
_cgo_gotypes.go:390 +0x41
/usr/local/bin/runcmdfile[43]: .: line 68: 29318: Abort
The issue occurs when you do not include the SCHEMA= option in the LIBNAME statement.
Click the Hot Fix tab in this note to access the hot fix for this issue.
After you apply the hot fix, the error changes to the following because SCHEMA is a required option:
ERROR: CLI error trying to establish connection: Invalid connection string attribute : SCHEMA is required for this datasource
ERROR: Error in the LIBNAME statement.
Operating System and Release Information
SAS System | SAS/ACCESS Interface to Google BigQuery | Linux for x64 | 9.41 | | 9.4 TS1M6 | |
SAS System | SAS/ACCESS Interface to Google BigQuery (on SAS Viya) | Linux for x64 | V.03.05 | 2020.0.6 | Viya | Viya |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2021-06-29 16:46:17 |
Date Created: | 2021-04-07 17:11:40 |