![]() |
VOOZH | about |
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 Vercel to create a database link from Vercel to Oracle and to query Vercel data through the SQL*Plus tool. You can also create the database link and execute queries from SQL Developer.
Information for connecting to Vercel follows, along with different instructions for configuring a DSN in Windows and Linux environments.
Vercel uses Bearer token authentication. You can use either a personal access token or an OAuth access token as the API key.
To obtain a personal access token:
After obtaining your token, set the following connection properties:
Profile=C:\profiles\Vercel.apip;AuthScheme=APIKey;APIKey=your_access_token;
Many Vercel resources are scoped to a team. To scope all requests to a specific team, set the TeamId connection property to your team's ID. You can find your team ID by querying the Teams table or from the Vercel dashboard. Alternatively, you can specify TeamId in your SQL queries using the WHERE clause where supported.
Once the authentication is configured, you can connect to Vercel and query data from any of the available tables such as Projects, Deployments, Teams, and Domains.
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 Vercel 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.
If you are installing the CData ODBC Driver for Vercel 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.
[CData API Source] Driver = CData ODBC Driver for Vercel Description = My Description Profile = C:\profiles\Vercel.apip AuthScheme = APIKey APIKey = your_access_token
For specific information on using these configuration files, please refer to the help documentation (installed and found online).
The driver provides several connection properties that streamline accessing Vercel data just as you would an Oracle database. Set the following properties when working with Vercel 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.
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-api/lib/cdata.odbc.api.ini in a text editor and set the encoding.
[Driver] DriverManagerEncoding = UTF-8
Follow the procedure below to set up an ODBC gateway to Vercel data that enables you to query live Vercel data as an Oracle database.
Create the file initmyverceldb.ora in the folder oracle-home-directory/hs/admin and add the following setting:
HS_FDS_CONNECT_INFO = "CData API Sys"
If you are using the Database Gateway for ODBC, your listener.ora needs to have a SID_LIST_LISTENER entry that resembles the following:
SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (SID_NAME = myverceldb) (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:
SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (SID_NAME = myverceldb) (ORACLE_HOME = your-oracle-home) (PROGRAM = hsodbc) ) )
Add the connect descriptor below in tnsnames.ora, located in oracle-home-directory/NETWORK/admin:
myverceldb = (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=localhost)(PORT=1521)) (CONNECT_DATA=(SID=myverceldb)) (HS=OK) )
Test the configuration with the following command:
tnsping myverceldb
Open SQL*Plus and create the database link with the command below:
CREATE DATABASE LINK myverceldb CONNECT TO "user" IDENTIFIED BY "password" USING 'myverceldb';
You can now execute queries in SQL*Plus like the one below (note the double quotation marks around the table name):
SELECT * from "User"@myverceldb WHERE = '';
Connect to live data from Vercel with the API Driver
Connect to Vercel