Access Google Data Catalog Data as a Remote Oracle Database

Ready to get started?

Download for a free trial:

Download Now

Learn more:

Google Data Catalog ODBC Driver

The Google Data Catalog ODBC Driver is a powerful tool that allows you to connect with live data from Google Data Catalog, directly from any applications that support ODBC connectivity.

Access Google Data Catalog data like you would a database - read, write, and update Google Data Catalog Schemas, Tables, etc. through a standard ODBC Driver interface.



Use the Oracle ODBC Gateway and Heterogeneous Services technology to access Google Data Catalog data from your Oracle system.

The Oracle Database Gateway for ODBC and Heterogeneous Services technology enable you to connect to ODBC data sources as remote Oracle databases. This article shows how to use the CData ODBC Driver for Google Data Catalog to create a database link from Google Data Catalog to Oracle and to query Google Data Catalog data through the SQL*Plus tool. You can also create the database link and execute queries from SQL Developer.

Connect to Google Data Catalog as an ODBC Data Source

Information for connecting to Google Data Catalog follows, along with different instructions for configuring a DSN in Windows and Linux environments.

Google Data Catalog uses the OAuth authentication standard. Authorize access to Google APIs on behalf on individual users or on behalf of users in a domain.

Before connecting, specify the following to identify the organization and project you would like to connect to:

  • OrganizationId: The ID associated with the Google Cloud Platform organization resource you would like to connect to. Find this by navigating to the cloud console.

    Click the project selection drop-down, and select your organization from the list. Then, click More -> Settings. The organization ID is displayed on this page.

  • ProjectId: The ID associated with the Google Cloud Platform project resource you would like to connect to.

    Find this by navigating to the cloud console dashboard and selecting your project from the Select from drop-down. The project ID will be present in the Project info card.

When you connect, the OAuth endpoint opens in your default browser. Log in and grant permissions to the application to completes the OAuth process. For more information, refer to the OAuth section in the Help documentation.

Windows

If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.

Note: If you need to modify the DSN or create other Google Data Catalog DSNs, you must use a system DSN and the bitness of the DSN must match your Oracle system. You can access and create 32-bit DSNs on a 64-bit system by opening the 32-bit ODBC Data Source Administrator from C:\Windows\SysWOW64\odbcad32.exe.

Linux

If you are installing the CData ODBC Driver for Google Data Catalog in a Linux environment, the driver installation predefines a system DSN. You can modify the DSN by editing the system data sources file (/etc/odbc.ini) and defining the required connection properties.

/etc/odbc.ini

[CData GoogleDataCatalog Source] Driver = CData ODBC Driver for Google Data Catalog Description = My Description ProjectId = YourProjectId

For specific information on using these configuration files, please refer to the help documentation (installed and found online).

Set Connection Properties for Compatibility with Oracle

The driver provides several connection properties that streamline accessing Google Data Catalog data just as you would an Oracle database. Set the following properties when working with Google Data Catalog data in SQL*Plus and SQL Developer. For compatibility with Oracle, you will need to set the following connection properties, in addition to authentication and other required connection properties.

  • MapToWVarchar=False

    Set this property to map string data types to SQL_VARCHAR instead of SQL_WVARCHAR. By default, the driver uses SQL_WVARCHAR to accommodate various international character sets. You can use this property to avoid the ORA-28528 Heterogeneous Services data type conversion error when the Unicode type is returned.

  • MaximumColumnSize=4000

    Set this property to restrict the maximum column size to 4000 characters.

  • IncludeDualTable=True

    Set this property to mock the Oracle DUAL table. SQL Developer uses this table to test the connection.

Linux Configuration

In Linux environments, Oracle uses UTF-8 to communicate with the unixODBC Driver manager, whereas the default driver encoding is UTF-16. To resolve this, open the file /opt/cdata/cdata-driver-for-googledatacatalog/lib/cdata.odbc.googledatacatalog.ini in a text editor and set the encoding.

cdata.odbc.googledatacatalog.ini

[Driver] DriverManagerEncoding = UTF-8

Configure the ODBC Gateway, Oracle Net, and Oracle Database

Follow the procedure below to set up an ODBC gateway to Google Data Catalog data that enables you to query live Google Data Catalog data as an Oracle database.

  1. Create the file initmygoogledatacatalogdb.ora in the folder oracle-home-directory/hs/admin and add the following setting:

    initmygoogledatacatalogdb.ora

    HS_FDS_CONNECT_INFO = "CData GoogleDataCatalog Sys"
  2. Add an entry to the listener.ora file. This file is located in oracle-home-directory/NETWORK/admin.

    If you are using the Database Gateway for ODBC, your listener.ora needs to have a SID_LIST_LISTENER entry that resembles the following:

    listener.ora

    SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (SID_NAME = mygoogledatacatalogdb) (ORACLE_HOME = your-oracle-home) (PROGRAM = dg4odbc) ) )

    If you are using Heterogeneous Services, your listener.ora needs to have a SID_LIST_LISTENER entry that resembles the following:

    listener.ora

    SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (SID_NAME = mygoogledatacatalogdb) (ORACLE_HOME = your-oracle-home) (PROGRAM = hsodbc) ) )
  3. Add the connect descriptor below in tnsnames.ora, located in oracle-home-directory/NETWORK/admin:

    tnsnames.ora

    mygoogledatacatalogdb = (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=localhost)(PORT=1521)) (CONNECT_DATA=(SID=mygoogledatacatalogdb)) (HS=OK) )
  4. Restart the listener.
  5. Test the configuration with the following command:

    tnsping mygoogledatacatalogdb
  6. Open SQL*Plus and create the database link with the command below:

    CREATE DATABASE LINK mygoogledatacatalogdb CONNECT TO "user" IDENTIFIED BY "password" USING 'mygoogledatacatalogdb';

You can now execute queries in SQL*Plus like the one below (note the double quotation marks around the table name):

SELECT * from "Schemas"@mygoogledatacatalogdb WHERE ProjectId = 'bigquery-public-data';