Running the OpenEdge DB-to-Oracle utility in batch mode
Print
- Last Updated: January 17, 2024
- 1 minute read
- OpenEdge
- Version 12.8
- Documentation
To run the OpenEdge DB-to-Oracle utility in batch mode on a UNIX client machine:
- Create a target Oracle database. You should connect as a user with no pre-existing object.
- Start an instance of your target Oracle database.
-
If using Oracle Networking, make sure that the
ORACLE_SIDenvironment variable is set to the Oracle database name. -
Make sure that the
ORACLE_HOMEenvironment variable is set to the directory where you installed Oracle. -
On your client machine, pass parameters to the utility
by setting the environment variables as listed in the following table.
Table 1. Environment Variables Environment Variable Description PRODBNAMESpecify the source OpenEdge database name. PROCONPARMSSpecify parameters for the connection to the source OpenEdge database. SHDBNAMESpecify the new schema-holder name. ORADBNAMESpecify 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. ORAVERSIONSpecify the version of Oracle you are using. Possible values are 8,9, or10. The default is8.ORAUSERNAMESpecify the Oracle user's name. ORAPASSWORDSpecify the user's password. ORACONPARMSSpecify additional connection parameters for the schema holder. ORACODEPAGESpecify the OpenEdge name for the code page that the Oracle Database uses. TABLEAREAEnter the name of the Oracle tablespace where you want to store schema information. The default is the SYSTEMtablespace.INDEXAREAEnter the name of the Oracle tablespace where you want to store index information. The default is the SYSTEMtablespace.COMPATIBLESpecify YESto create an Oracle database that supportsFIND PREV/LASTand the OpenEdgeROWIDfunction. The default isYES.SQLWIDTHSpecify YESto use the_widthfield to calculate column size instead of using the format field.ORACOLLNAMEEnter the collation name. CRTDEFAULTSpecify YESto include initial values in column definitions.LOADSQLSpecify YESto load the.sqlfile that contains the data definitions for your OpenEdge database into the Oracle database. SpecifyNOif you do not want the utility to load the.sqlfile, for example if you want to edit the file before loading it. The default isYES.MOVEDATASpecify YESto dump and load data. Otherwise, if you do not want to populate the Oracle database, specifyNO. For example, you might specifyNOif your database is large, and you want to dump and load data at a more convenient time. The default isNO.EXPANDX8This setting is on by default to indicate that the format for the character fields defined as x(8) will be created as 30 characters. UNICODETYPESMaps character fields to Unicode data types. The default is NO.CHARSEMANTICSSets the unit of measure for length to character semantics when migrating OpenEdge file fields to Oracle data columns. The default setting is YESifORACODEPAGEis 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.
VARLENGTHDependent on other selections. Maximum value is 4000. -
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