Release 10.1A: OpenEdge Data Management:
DataServer for ORACLE

> ## OpenEdge DataServer for ORACLE logic

> The DataServer places OpenEdge equivalents for the data definitions from an ORACLE database into a schema holder. A schema holder contains only data definitions for one or more non-OpenEdge databases. When you issue 4GL statements, they are compiled into calls to the ORACLE database. When the OpenEdge client executes 4GL statements and retrieves information from the ORACLE database, it relies on data definitions maintained by the Data Dictionary in the OpenEdge schema holder. Figure 1–2 shows the internal logic of the OpenEdge DataServer for ORACLE.

> Figure 1–2: The OpenEdge DataServer for ORACLE logic

> The DataServer uses the ORACLE Call Interface (OCI) to access an ORACLE instance. An ORACLE instance provides the software mechanisms for accessing and controlling a database. When you start up the ORACLE Database Manager (DBMS) against a database, you create an ORACLE instance. See your ORACLE documentation for more information on instances.

> When you execute an OpenEdge application that accesses an ORACLE database, the Compiler translates the 4GL statements in the OpenEdge application into their SQL equivalents. The DataServer then issues the SQL statements to the ORACLE instance through the OCI. The ORACLE instance processes the SQL statements and returns the results to the application through the OCI.

> You can also send SQL statements directly to ORACLE. The DataServer passes `SELECT` SQL statements that you reference in a 4GL application directly to ORACLE without translating them. The DataServer also allows you to issue PL/SQL statements from an OpenEdge application.

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095