Try OpenEdge Now
skip to main content
DataServer for Oracle
The DataServer Tutorial : OpenEdge DB-to-Oracle utility : Running the OpenEdge DB-to-Oracle utility : Running the OpenEdge DB-to-Oracle utility in batch mode
 
Running the OpenEdge DB-to-Oracle utility in batch mode
To run the OpenEdge DB-to-Oracle utility in batch mode on a UNIX client machine:
1. Create a target Oracle database. You should connect as a user with no pre-existing object.
2. Start an instance of your target Oracle database.
3. If using Oracle Networking, make sure that the ORACLE_SID environment variable is set to the Oracle database name.
4. Make sure that the ORACLE_HOME environment variable is set to the directory where you installed Oracle.
5. On your client machine, pass parameters to the utility by setting the environment variables as listed in the following table.
Table 66. Environment Variables
Environment Variable
Description
PRODBNAME
Specify the source OpenEdge database name.
PROCONPARMS
Specify parameters for the connection to the source OpenEdge database.
SHDBNAME
Specify the new schema-holder name.
ORADBNAME
Specify the Oracle database logical name. The database's logical name can be the same as its physical name, but it must be different from the name you enter for the schema holder.
ORAVERSION
Specify the version of Oracle you are using. Possible values are 8, 9, or 10. The default is 8.
ORAUSERNAME
Specify the Oracle user's name.
ORAPASSWORD
Specify the user's password.
ORACONPARMS
Specify additional connection parameters for the schema holder.
ORACODEPAGE
Specify the OpenEdge name for the code page that the Oracle Database uses.
TABLEAREA
Enter the name of the Oracle tablespace where you want to store schema information. The default is the SYSTEM tablespace.
INDEXAREA
Enter the name of the Oracle tablespace where you want to store index information. The default is the SYSTEM tablespace.
COMPATIBLE
Specify YES to create an Oracle database that supports FIND PREV/LAST and the OpenEdge ROWID function. The default is YES.
SQLWIDTH
Specify YES to use the _width field to calculate column size instead of using the format field.
ORACOLLNAME
Enter the collation name.
CRTDEFAULT
Specify YES to include initial values in column definitions.
LOADSQL
Specify YES to load the .sql file that contains the data definitions for your OpenEdge database into the Oracle database. Specify NO if you do not want the utility to load the .sql file, for example if you want to edit the file before loading it. The default is YES.
MOVEDATA
Specify YES to dump and load data. Otherwise, if you do not want to populate the Oracle database, specify NO. For example, you might specify NO if your database is large, and you want to dump and load data at a more convenient time. The default is NO.
EXPANDX8
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.
UNICODETYPES
Maps character fields to Unicode data types. The default is NO.
CHARSEMANTICS
Sets the unit of measure for length to character semantics when migrating OpenEdge file fields to Oracle data columns. The default setting is YES if ORACODEPAGE is UTF-8.
SHADOWCOL
Determines if shadow columns must be added to the record layout to represent data in upper case form for OpenEdge fields marked case-insensitive.
VARLENGTH
Dependent on other selections. Maximum value is 4000.
6. Enter these commands to set and export environment variables at the system prompt before running the compiled ABL program, protoora.r:
PRODBNAME=db-name; export PRODBNAME
PROCONPARMS="-1 -i"
SHDBNAME=schema-holder-name; export SHDBNAME
...pro -b -p prodict/ora/protoora.r