Kbase P3397: Why select 'Create Extended 4GL Objects' option when migrating Progress-to-ORACLE?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/16/2008 |
|
Status: Verified
GOAL:
Why select 'Create Extended 4GL Objects' option when migrating Progress-to-ORACLE?
FIX:
The Progress-to-ORACLE utility does not literally translate definitions for Progress fields into Oracle columns. It is important to know what adjustments are made in order to provide the functionality of the Progress and ORACLE systems.
Table 5-5 lists the changes to a database that result from making a Progress database compatible with ORACLE by selecting "Create Extended 4GL Objects" option during the migration.
1. PROGRESS_RECID NUMBER column created within the Oracle table
2. Sequence, named <table_name>_SEQ, for providing a value to PROGRESS_RECID
3. VARCHAR2 column, u##column_name, created when field is part of a
case-insensitive index
4. Columns field##1, field##2,... for a field of Progress datatype ARRAY