Feedback
 
Did this article resolve your question/issue?

   

Your feedback is appreciated.

Please tell us how we can make this article more useful. Please provide us a way to contact you, should we need clarification on the feedback provided or if you need further assistance.

Characters Remaining: 1025

 


Article

How to migrate a database from Progress version 9 to OpenEdge 11 on the same machine?

« Go Back

Information

 
Article Number000029914
EnvironmentProduct: Progress
Version: 9.x
Product: OpenEdge
Version: 10.x, 11.x
OS: All Supported Operating System
Question/Problem Description
How to migrate a database from Progress version 9 to OpenEdge 11 on the same machine?
How to upgrade a database from Progress version 9 to OpenEdge 11 on the same machine?
How to migrate a database from Progress version 9.1E to OpenEdge 11 on the same machine?
Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement Number
Cause
Resolution
1) Open a Progress 9 PROENV window by first bringing up a terminal or command prompt for your Operating System.
On windows:  Start -> All Programs -> Progress -> Progress 9 and select: proenv.
UNIX command line:  Go to where <Progress 9 is installed>/bin and execute the proenv command.
Windows command line:  Go to where < Progress 9 is installed>\bin and execute the proenv command

2)  Always have a verified offline backup prior to conversion. Backup the Progress 9 database using the version 9 executables:
$   probkup <dbname> <dbname>.bkp
$   prorest <dbname> <dbname>.bkp -vf

Starting with OpenEdge 11.2 the <DLC directory>/bin/91dbutils/conv911 script / batch is provided for converting a database from Progress 9 to OpenEdge 11 instead of the Steps outlined below.
$   DLC/bin/91dbutils/conv911 <dbname>

3) Truncate the Progress 9 database using the current version 9 executables:
$   proutil <dbname> -C truncate bi

4) Open a new OpenEdge 11 PROENV window by first bringing up a terminal or command prompt for your Operating System.
 
On windows:  Start -> All Programs -> Progress -> OpenEdge 11.x and select: proenv.
UNIX command line:  Go to where <OpenEdge 11.x is installed>/bin and execute the proenv command.
Windows command line:  Go to where <OpenEdge 11.x is installed>\bin and execute the proenv command.
 
5)  Once PROENV has executed it will display the directory where OpenEdge 11 was installed and set the DLC environment variable. 
Another environment variable needs to be set to reference this value as the default value of DLC will be changed throughout this exercise and finally reverted.  
 
On UNIX:  
ORIGDLC=$DLC;export ORIGDLC
 
On Windows:
set ORIGDLC=%DLC%

6)  Convert the Progress 9 database to OpenEdge 10. 
 
a) Set the DLC and PROCONV environment variables to point to DLC/bin/102dbutils. 
 
On UNIX: 
DLC=$ORIGDLC/bin/102dbutils;export DLC 
PROCONV=$DLC/convmap.cp; export PROCONV
 
On Windows: 
set DLC=%ORIGDLC%\bin\102dbutils 
set PROCONV=%DLC%\convmap.cp
 
b) Convert the database from 9 to 10 using 102dbutils. 
 
On UNIX: 
$DLC/102b05_dbutil <dbname> -C conv910 
 
On Windows:
%DLC%\102b05_dbutil <dbname> -C conv910
 
c) Truncate BI file using 102dbutils: 
 
On UNIX: 
$DLC/102b05_dbutil <dbname> -C truncate bi
 
On Windows: 
%DLC%\102b05_dbutil <dbname> -C truncate bi 
 
d) Optionally backup the database using 102dbutils: 
 
On UNIX: 
$DLC/102b05_dbutil -C probkup <dbname> <dbname>10.bkp 
 
On Windows:
%DLC%\102b05_dbutil -C probkup <dbname> <dbname>10.bkp 
 
7) Convert the now OpenEdge 10 database to OpenEdge 11
 
a) Set the DLC and PROCONV environment variables to the OpenEdge 11 installation. 
 
On UNIX:  
DLC=$ORIGDLC;export DLC
PROCONV=$DLC/convmap.cp; export PROCONV
 
On Windows:
set DLC=%ORIGDLC%
set PROCONV=%DLC%\convmap.cp
 
Alternatively open a new OpenEdge 11 PROENV window to set the environment to OpenEdge 11. 
 
b) Convert the database from 10 to 11 using conv1011:
proutil <dbname> -C conv1011

c)  Backup the database using OpenEdge 11:
probkup <dbname> <dbname>-11.bkp
Workaround
Notes
1) If the location of the database extent changes use $DLC/102b05_dbutil prostrct repair <dbname> <filename>.st to apply changes to the database before running the steps on this article.

2) If after-image is enabled for database make sure to disable after-image before starting the conversion. Fail to do so may result in a partial conversion and backup will need to be reverted to as the database will not be usable.
Attachment 
Last Modified Date12/23/2015 12:32 PM