Converts an OpenEdge Release 11 replication source database to an OpenEdge Release 12 database.

Syntax

proutil db-name -C conv1112  replsource conversion-file

Parameters

db-name
Specifies the OpenEdge Release 11 source database name.
replsource
Creates a schema backup file with the name specified by conversion-file from a replication-enabled OpenEdge Release 11 source database. After-imaging and replication are enabled for the generated replication source. The backup file is used later by the repltarget operation. This option applies only to replication source databases.
conversion-file
Specifies the name of the schema backup file.

You may save time by converting only the database schema area instead of the entire database. Upgrading from OpenEdge Release 11 to OpenEdge Release 12 allows this type of conversion.

CAUTION: Before you convert the database schema area, make sure that your databases meet requirements. Complete the steps in Prepare to convert replication-enabled databases in Upgrade to OpenEdge 12 before you run CONV1112.
Note: Users who defined SQL views in an OpenEdge Release 11 database may see messages like the following after running CONV1112. 
You must have your database backed up before running the conversion. (1024)
Have you done this (y/n) ?
Updated view LOPEZ.MYVIEW's file number to 32820 (20551)
VST Table Deletion has begun. Please stand by. (6876)
VST Table Deletion has completed successfully. (6885)
Conversion completed, database is now in Progress OpenEdge Release 12 format. (19121)
PLEASE IMMEDIATELY BACK UP YOUR NEWLY CONVERTED Progress OpenEdge Release 12 DATABASE !!! (11115)
Follow the instructions in the messages immediately after you run CONV1112. CONV1112 installs a new system view with file number 32819. If you defined a SQL view with file number 32819 in your Release 11.7 database, CONV1112 updates the file number of your SQL view to the next available file number, as shown in message 20551.

CONV1112 performs a pre-scan to check for conditions that prevent a complete conversion. If any conditions exist that would prevent a complete conversion are found, they are reported, and CONV1112 exits normally with no change to the database. You must correct all reported issues before CONV1112 can successfully complete. Conditions that cause the pre-scan to exit include:

  • The database is not an OpenEdge Release 11 database.
  • The database has Transparent Data Encryption (TDE) enabled, and an encryption policy using the current or previous RC4 cipher (Cipher ID 7) exists on any table, index, or LOB.

For conversion steps and results, see Convert replication-enabled databases without target rebase in Upgrade to OpenEdge 12.