Preparing a database for the utility
- Last Updated: March 30, 2020
- 1 minute read
- OpenEdge
- Version 12.2
- Documentation
The OpenEdge DB-to-Oracle utility does not literally translate definitions for Progress fields into Oracle columns. It makes some adjustments in order to provide the functionality of the OpenEdge and Oracle systems. The following table describes the changes to a database that result from making an OpenEdge database compatible with Oracle when using the OpenEdge-to-Oracle utility.
| OpenEdge database | Oracle database |
|---|---|
| Record ID | An additional NUMBER column
named PROGRESS_RECID |
| Case-insensitive index | The UPPER(column-name) syntax
is used by the index SQL |
| Array | A column for each array element named field##1, field##2,
etc. |
| Sequence | A sequence with the same characteristics (incrementation, beginning value, etc.) |
| OpenEdge BLOB type | This is set to NOT NULL in Oracle |
Note: OpenEdge BLOB must be set to NOT NULL in Oracle, that is, any Oracle application that
inserts records into a table also initializes the record with EMPTY_BLOB() function as
OpenEdge DataServer cannot access a NULL BLOB column.
The utility makes these changes in the target Oracle database automatically. The following sections explain how to account for these changes when you plan your migration.