Schemas are Stale when Creating a Dataset on a Google BigQuery Connection in Oracle Analytics Cloud (Doc ID 2830048.1)

Last updated on NOVEMBER 03, 2023

Applies to:

Symptoms

In OAC, a Google BigQuery connection (For example: Connection-1) is created using the Private Key for a Service Account (For example: Account-1) that has access to certain BigQuery datasets/tables/views (For example: Table-A and Table-B). On creating a Dataset on this connection, these tables/views are visible in the Connections Pane, and columns can be selected to add to the Data Set.

In BigQuery, some changes have occurred over time. For example:

1. New tables, Table-D and Table-E, are created.
2. Account-1 is granted access / permissions to Table-D (in addition to Table-A and Table-B).
3. Another Service Account (Account-2) is created, and has access to Table-E (only).

The following scenarios may be encountered in OAC:

1. If a new Dataset is created on Connection-1, only Table-A and Table-B will be visible in the Connections Pane; that is, Table-D is not listed. However, if a Manual Query is constructed that references Table-D, it will execute successfully and return results.

2. A Google BigQuery connection (For example: Connection-2) is created, using the Private Key of Account-2. On creating a Dataset on this connection, only Table-A and Table-B will be visible in the Connections Pane; that is, Table-E is not listed.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.