1. Oracle Enterprise Data Quality Online Help
  2. Oracle Enterprise Data Quality Applications Help Topics
  3. Data Stores

Data Stores

A Data Store is a connection to a store of data, whether the data is stored in a database or in one or more files. The data store may be used as the source of data for a process, or you may export the written Staged Data results of a process to a data store, or both.

It is normally recommended to connect to the data store via the server. When connecting to files, this means that the files must exist in the server landing area to ensure that the server will be able to access them. However, it is also possible to pull the data onto the server using a client connection. See Client-side data stores for more details.

EDQ supports native connections to the following types of data store:

Databases

  • Oracle

  • Oracle TimesTen In Memory Database

  • Sybase Adaptive Server Enterprise

  • Sybase IQ

  • Sybase SQL Anywhere

  • Teradata Database

  • PostgreSQL

  • DB2

  • DB2 for i5/OS (see below for further details)

  • MySQL

  • Microsoft SQL Server

  • Sybase

  • Microsoft Access

  • JNDI Datasources

  • Cassandra

Notes:

  • EDQ can also support connections to Teradata systems, if the Teradata JDBC driver is purchased.

  • The JNDI Datasource option is used to connect to a preconfigured connection on an application server, such as Weblogic.

  • EDQ cannot support create table option in Cassandra.

Connecting EDQ to Oracle Databases

By default, EDQ connects to an Oracle database using a direct JDBC connection. It is also possible to connect to Oracle via a JNDI connection configured on the application server, or to configure the EDQ server to use connections via connection strings specified in tnsnames.ora files or on an LDAP server.

These alternative methods may be useful if connecting to a logical schema on a RAC-enabled database, such as Oracle Exadata. For details of how to enable configure EDQ to enable connections to Oracle via tnsnames or LDAP, see Administering Oracle Enterprise Data Quality in the EDQ Release 12.2.1 document library.

Connecting EDQ to DB2 for i5/OS

To connect EDQ to a DB2 for i5/OS database, you must download the DB2 for iSeries driver.

Use the following procedure:

  1. Download Toolbox for Java/JTOpen from http://jt400.sourceforge.net/

  2. Extract the downloaded file. The filename will be in the format (jtopen_N_n.zip), where N and n represent the first and second digits of the version number.

  3. Create a folder called db2i5 in the oedq_local_home/dbconnectors directory.

  4. Copy in the jt400.jar file from the zip file extracted in step 2, and copy it to the db2i5 folder.

  5. Restart the EDQ (Datanomic) application server.

Connecting to an Access Database

Consider the following points if you want to connect to an Access Database:

  • Connecting to Access Databases in EDQ using server-side data store connections is only possible on Windows EDQ servers.

  • To enable server-side connections to Access Database on a Windows EDQ server, the Access drivers must be installed on that server. These are installed as part of Access 2010. If Access 2010 is not installed, the necessary drivers can be installed separately:

    Install Microsoft Access Database Engine 2010 Redistributable (Microsoft.ACE.OLEDB.12.0) from the Microsoft website at

    http://www.microsoft.com/en-gb/download/details.aspx?id=13255

  • Client-side connections to Access databases can be made using Windows clients with Access or with the preceding driver installed even if the EDQ server is running on Linux or UNIX. Additionally, you should review the limitations of client-side data store connections, see Client-side data stores.

Note:

If you are using a 64-bit Java Virtual Machine (JVM) to connect to MDB files, you must install the 64-bit Microsoft Jet Database Engine.

Text Files

  • Text Files (that is, CSV files, or other delimited text files);

  • A directory of delimited text files;

  • Fixed width Text Files.

XML Files

  • XML with Stylesheet (that is, XML files with an XSLT stylesheet file which defines how to translate the XML file into a format understood by EDQ)

  • Simple XML Files (that is, XML files with a simple 2-level structure where the top level tag represents the entity, and the lower level tags represent the attributes of the entity. XML files exported from Microsoft Access are an example.)

MS Office Files

  • Microsoft Access Files

  • Microsoft Excel Files

Other

EDQ supports connectivity to other data stores using standards such as JDBC and ODBC. ODBC connections can only be made via the Client.

See Oracle's JDBC FAQ for information to help you connect to a data store using a JDBC URL.

The connection details to a Data Store are saved on the EDQ server. Any user with access to that server, and the relevant project, can then use that data store.