We are proud to share our inclusion in the 2024 Gartner Magic Quadrant for Data Integration Tools. We believe this recognition reflects the differentiated business outcomes CData delivers to our customers.
Get the Report →Access Neo4J Data as a Remote Oracle Database
Use the Oracle ODBC Gateway and Heterogeneous Services technology to access Neo4J 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 Neo4J to create a database link from Neo4J to Oracle and to query Neo4J data through the SQL*Plus tool. You can also create the database link and execute queries from SQL Developer.
Connect to Neo4J as an ODBC Data Source
Information for connecting to Neo4J follows, along with different instructions for configuring a DSN in Windows and Linux environments.
To connect to Neo4j, set the following connection properties:
- Server: The server hosting the Neo4j instance.
- Port: The port on which the Neo4j service is running. The provider connects to port 7474 by default.
- User: The username of the user using the Neo4j instance.
- Password: The password of the user using the Neo4j instance.
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 Neo4J 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 Neo4J 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 Neo4j Source]
Driver = CData ODBC Driver for Neo4J
Description = My Description
Server = localhost
Port = 7474
User = my_user
Password = my_password
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 Neo4J data just as you would an Oracle database. Set the following properties when working with Neo4J 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-neo4j/lib/cdata.odbc.neo4j.ini in a text editor and set the encoding.
cdata.odbc.neo4j.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 Neo4J data that enables you to query live Neo4J data as an Oracle database.
-
Create the file initmyneo4jdb.ora in the folder oracle-home-directory/hs/admin and add the following setting:
initmyneo4jdb.ora
HS_FDS_CONNECT_INFO = "CData Neo4j Sys"
-
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 = myneo4jdb) (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 = myneo4jdb) (ORACLE_HOME = your-oracle-home) (PROGRAM = hsodbc) ) )
-
Add the connect descriptor below in tnsnames.ora, located in oracle-home-directory/NETWORK/admin:
tnsnames.ora
myneo4jdb = (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=localhost)(PORT=1521)) (CONNECT_DATA=(SID=myneo4jdb)) (HS=OK) )
- Restart the listener.
Test the configuration with the following command:
tnsping myneo4jdb
-
Open SQL*Plus and create the database link with the command below:
CREATE DATABASE LINK myneo4jdb CONNECT TO "user" IDENTIFIED BY "password" USING 'myneo4jdb';
You can now execute queries in SQL*Plus like the one below (note the double quotation marks around the table name):
SELECT * from "ProductCategory"@myneo4jdb WHERE CategoryOwner = 'CData Software';