Ready to get started?

Download a free trial of the BigCommerce ODBC Driver to get started:

 Download Now

Learn more:

BigCommerce Icon BigCommerce ODBC Driver

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

Access BigCommerce data like you would a database - read, write, and update BigCommerce Customers, Products, Orders, Transactions, etc. through a standard ODBC Driver interface.

Access BigCommerce Data as a Remote Oracle Database



Use the Oracle ODBC Gateway and Heterogeneous Services technology to access BigCommerce 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 BigCommerce to create a database link from BigCommerce to Oracle and to query BigCommerce data through the SQL*Plus tool. You can also create the database link and execute queries from SQL Developer.

Connect to BigCommerce as an ODBC Data Source

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

BigCommerce authentication is based on the standard OAuth flow. To authenticate, you must initially create an app via the Big Commerce developer platform where you can obtain an OAuthClientId, OAuthClientSecret, and CallbackURL. These three parameters will be set as connection properties to your driver.

Additionally, in order to connect to your BigCommerce Store, you will need your StoreId. To find your Store Id please follow these steps:

  1. Log in to your BigCommerce account.
  2. From the Home Page, select Advanced Settings > API Accounts.
  3. Click Create API Account.
  4. A text box named API Path will appear on your screen.
  5. Inside you can see a URL of the following structure: https://api.bigcommerce.com/stores/{Store Id}/v3.
  6. As demonstrated above, your Store Id will be between the 'stores/' and '/v3' path paramters.
  7. Once you have retrieved your Store Id you can either click Cancel or proceed in creating an API Account in case you do not have one already.

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 BigCommerce 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 BigCommerce 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 BigCommerce Source] Driver = CData ODBC Driver for BigCommerce Description = My Description OAuthClientId = YourClientId OAuthClientSecret = YourClientSecret StoreId = 'YourStoreID' CallbackURL = 'http://localhost:33333'

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 BigCommerce data just as you would an Oracle database. Set the following properties when working with BigCommerce 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-bigcommerce/lib/cdata.odbc.bigcommerce.ini in a text editor and set the encoding.

cdata.odbc.bigcommerce.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 BigCommerce data that enables you to query live BigCommerce data as an Oracle database.

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

    initmybigcommercedb.ora

    HS_FDS_CONNECT_INFO = "CData BigCommerce 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 = mybigcommercedb) (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 = mybigcommercedb) (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

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

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

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

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

SELECT * from "Customers"@mybigcommercedb WHERE FirstName = 'Bob';