Try OpenEdge Now
skip to main content
DataServer for Oracle
The DataServer Tutorial : OpenEdge DB-to-Oracle utility : Naming conventions

Naming conventions

The OpenEdge-to-Oracle utility generates names for the columns it adds to an Oracle table. These names follow the conventions described in the following table.
Table 63. OpenEdge-to-Oracle naming conventions
OpenEdge field
Oracle column name
Record ID
Array with three elements(for example, MONTH)
field ##1, field##2, field##3(MONTH##1, MONTH##2, MONTH##3)
For example, if your source OpenEdge table includes a field extent named MONTH with 12 elements, the OpenEdge-to-Oracle utility creates 12 columns of the same data type named MONTH##1, MONTH##2, MONTH##3, etc. ABL reference to MONTH[3] translates into a reference to the Oracle column MONTH##3.
In addition, the OpenEdge-to-Oracle utility modifies the names of OpenEdge objects to non-Oracle keywords in the Oracle schema. For example, ORDER is a reserved word in Oracle, so the utility changes the order field of the OpenEdge demo database to the order_ column in an Oracle database. It also modifies names that might conflict with unrolled field extents and that contain characters unacceptable to Oracle. The OpenEdge field name order-line changes to order_line to account for the fact that the hyphen (-) is an unacceptable character in Oracle object names. Be aware that if you have objects in your OpenEdge database with names that are very similar, and conflict with Oracle reserved words and restricted characters, they can be modified multiple times to produce a valid name.