| |
Original OpenEdge Database
| The source database name. Accept the default value.
|
Connect parameters for OpenEdge
| The parameters for the connection to the source OpenEdge database, which is the current working database. Accept the default value.
|
Name of Schema holder Database
| Enter the name for the schema holder. The utility creates the schema holder if it does not exist.
|
Logical name for Oracle Database
| Enter the Oracle database logical name. The logical database name is the name of the schema image and the name you will use to refer to the Oracle database in applications. The database’s logical name must be different than the name you enter for the schema holder and different than the name of any other schema image existing in that schema holder.
|
What version of Oracle
| Enter the version of Oracle you are using. The default is 8. To enable Unicode, this value must be set to 9 or higher, which represents Version 9i or later.
|
Oracle Owner’s Username
| Enter the Oracle database owner’s name.
|
Oracle User’s password
| Enter the owner’s password.
|
Oracle connect parameters
| Enter additional connection parameters as needed.
|
Code page for Schema Image
| Enter the OpenEdge name for the code page that the Oracle Call Interface (OCI) uses. For Unicode support, set the value to UTF-8 when migrating from an OpenEdge database to an Oracle database.
Note: For a UTF-8 schema image code page, the corresponding OCI code page (that is, the NLS_LANG setting) setting must be AL32UTF8 to ensure full Unicode compatibility. |
Collation Name
| Enter the collation table you wish to use. By default, the collation table is Basic. The collation table you specify must be defined in the convmap .dat file or you will receive an error message.
|
Maximum char length
| Enter a positive value up to and including 4000. This value is defaulted based on the values of other Unicode-specific settings in your migration. See the "Handling character length during database migration" section for details.
|
Tablespace tables
| Enter the name of the Oracle tablespace where you want to store schema information. The default is the Oracle user’s default tablespace.
|
Tablespace index
| Enter the name of the Oracle tablespace where you want to store index information. The default is the Oracle user’s default tablespace.
|
Create RECID field
| Check this toggle box to create an Oracle database that supports arrays, case-insensitive indexes, backward and forward scrolling, and the OpenEdge record identifier. These objects result in additional columns added to Oracle tables.
|
Load SQL
| Check this toggle box to load the .sql file that contains the data definitions for your OpenEdge database into the Oracle database. By default, this option is checked.
|
Move Data
| Check this toggle box to dump and load data from your OpenEdge database to the Oracle database. Copying data from a large database can take a long time. For example, you might not check this box if you want to dump and load data at a more convenient time.
|
Create Shadow Columns
| Check this toggle box to support case-sensitive columns with shadow columns. By default, this option is not checked, allowing the utility to automatically support ABL case insensitivity via Oracle function-based indexes.
Note: Function-based indexes and shadow columns can coexist in a schema holder to support case insensitive indexes. |
Include Default
| Check this toggle box to include initial values in column definitions.
|
Char semantics
| Check this toggle box to set the unit of measure for length to character semantics when migrating OpenEdge file fields to Oracle table columns. Length values for the migration are derived from the For field widths use setting. The Char semantics option is only enabled for Unicode migrations. To enable it, the schema image code page must be set to utf-8 and you must specify an Oracle Version of 9 or later. The default setting is YES if ORACODEPAGE is UTF-8.
|
Use Unicode Types
| Maps character fields to Unicode data types. You must specify 9 or higher (corresponding to an Oracle version of 9i or later) to enable this option.
|
For field widths use
| When pushing fields to a foreign data source, you can select one of two primary field format options:
- Width — Uses the value of the _width field in the _field record. Recommended especially for Unicode implementations. For more information on field widths, see the "Adjusting field widths during migration" section.
- ABL Format — Compiles with the current default width specified. (default)
If you select the ABL Format option, you have an additional setting to define:
- Expand x(8) to 30 — This setting is on by default to indicate that the format for the character fields defined as x(8) will be created as 30 characters.
Note: You cannot use the Expand x(8) to 30 setting with the Width option. |
