ETL SAS xpt in Oracle Data Integrator

Ready to get started?

Download for a free trial:

Download Now

Learn more:

SASxpt JDBC Driver

Rapidly create and deploy powerful Java applications that integrate with SAS xpt (XPORT) files data.



This article shows how to transfer SAS xpt data into a data warehouse using Oracle Data Integrator.

Leverage existing skills by using the JDBC standard to connect to SAS xpt: Through drop-in integration into ETL tools like Oracle Data Integrator (ODI), the CData JDBC Driver for SAS xpt connects real-time SAS xpt data to your data warehouse, business intelligence, and Big Data technologies.

JDBC connectivity enables you to work with SAS xpt just as you would any other database in ODI. As with an RDBMS, you can use the driver to connect directly to the SAS xpt APIs in real time instead of working with flat files.

This article walks through a JDBC-based ETL -- SAS xpt to Oracle. After reverse engineering a data model of SAS xpt entities, you will create a mapping and select a data loading strategy -- since the driver supports SQL-92, this last step can easily be accomplished by selecting the built-in SQL to SQL Loading Knowledge Module.

Install the Driver

To install the driver, copy the driver JAR and .lic file, located in the installation folder, into the ODI userlib directory:

On Unix: ~/.odi/oracledi/userlib On Windows: %APPDATA%\Roaming\odi\oracledi\userlib

Restart ODI to complete the installation.

Reverse Engineer a Model

Reverse engineering the model retrieves metadata about the driver's relational view of SAS xpt data. After reverse engineering, you can query real-time SAS xpt data and create mappings based on SAS xpt tables.

  1. In ODI, connect to your repository and click New -> Model and Topology Objects.
  2. On the Model screen of the resulting dialog, enter the following information:
    • Name: Enter SASXpt.
    • Technology: Select Generic SQL (for ODI Version 12.2+, select Microsoft SQL Server).
    • Logical Schema: Enter SASXpt.
    • Context: Select Global.
  3. On the Data Server screen of the resulting dialog, enter the following information:
    • Name: Enter SASXpt.
    • Driver List: Select Oracle JDBC Driver.
    • Driver: Enter cdata.jdbc.sasxpt.SASXptDriver
    • URL: Enter the JDBC URL containing the connection string.

      Connecting to Local SASXpt Files

      You can connect to local SASXpt file by setting the URI to a folder containing SASXpt files.

      Connecting to S3 data source

      You can connect to Amazon S3 source to read SASXpt files. Set the following properties to connect:

      • URI: Set this to the folder within your bucket that you would like to connect to.
      • AWSAccessKey: Set this to your AWS account access key.
      • AWSSecretKey: Set this to your AWS account secret key.
      • TemporaryLocalFolder: Set this to the path, or URI, to the folder that is used to temporarily download SASXpt file(s).

      Connecting to Azure Data Lake Storage Gen2

      You can connect to ADLS Gen2 to read SASXpt files. Set the following properties to connect:

      • URI: Set this to the name of the file system and the name of the folder which contacts your SASXpt files.
      • AzureAccount: Set this to the name of the Azure Data Lake storage account.
      • AzureAccessKey: Set this to our Azure DataLakeStore Gen 2 storage account access key.
      • TemporaryLocalFolder: Set this to the path, or URI, to the folder that is used to temporarily download SASXpt file(s).

      Built-in Connection String Designer

      For assistance in constructing the JDBC URL, use the connection string designer built into the SAS xpt JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

      java -jar cdata.jdbc.sasxpt.jar

      Fill in the connection properties and copy the connection string to the clipboard.

      Below is a typical connection string:

      jdbc:sasxpt:URI=C:/folder;
  4. On the Physical Schema screen, enter the following information:
    • Schema (Schema): Enter SASXpt.
    • Schema (Work Schema): Enter SASXpt.
  5. In the opened model click Reverse Engineer to retrieve the metadata for SAS xpt tables.

Edit and Save SAS xpt Data

After reverse engineering you can now work with SAS xpt data in ODI. To view SAS xpt data, expand the Models accordion in the Designer navigator, right-click a table, and click View data.

Create an ETL Project

Follow the steps below to create an ETL from SAS xpt. You will load SampleTable_1 entities into the sample data warehouse included in the ODI Getting Started VM.

  1. Open SQL Developer and connect to your Oracle database. Right-click the node for your database in the Connections pane and click new SQL Worksheet.

    Alternatively you can use SQLPlus. From a command prompt enter the following:

    sqlplus / as sysdba
  2. Enter the following query to create a new target table in the sample data warehouse, which is in the ODI_DEMO schema. The following query defines a few columns that match the SampleTable_1 table in SAS xpt: CREATE TABLE ODI_DEMO.TRG_SAMPLETABLE_1 (COLUMN1 NUMBER(20,0),Id VARCHAR2(255));
  3. In ODI expand the Models accordion in the Designer navigator and double-click the Sales Administration node in the ODI_DEMO folder. The model is opened in the Model Editor.
  4. Click Reverse Engineer. The TRG_SAMPLETABLE_1 table is added to the model.
  5. Right-click the Mappings node in your project and click New Mapping. Enter a name for the mapping and clear the Create Empty Dataset option. The Mapping Editor is displayed.
  6. Drag the TRG_SAMPLETABLE_1 table from the Sales Administration model onto the mapping.
  7. Drag the SampleTable_1 table from the SAS xpt model onto the mapping.
  8. Click the source connector point and drag to the target connector point. The Attribute Matching dialog is displayed. For this example, use the default options. The target expressions are then displayed in the properties for the target columns.
  9. Open the Physical tab of the Mapping Editor and click SAMPLETABLE_1_AP in TARGET_GROUP.
  10. In the SAMPLETABLE_1_AP properties, select LKM SQL to SQL (Built-In) on the Loading Knowledge Module tab.

You can then run the mapping to load SAS xpt data into Oracle.