PROUTIL CONV1112 qualifier

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

To convert replication source and target databases from OpenEdge Release 11 to OpenEdge Release 12, see PROUTIL CONV1112 REPLSOURCE qualifier and PROUTIL CONV1112 REPLTARGET qualifier.

Syntax

proutil db-name -C conv1112

Parameters

db-name
Specifies the OpenEdge Release 11 source database name.

To convert from OpenEdge 11 to a major version release (OpenEdge 12.0), you must perform a full database conversion with CONV1112. Conversion must be performed when the database is offline, and cannot be interrupted. If there is an abnormal exit from CONV1112, you must revert to a backup of your OpenEdge Release 11 database.

Before performing the conversion, you must:

  • Back up your OpenEdge Release 11 database using a Release 11 backup utility.
  • Verify that the database is not in use.
  • Truncate the BI file with Release 11.
  • Disable after-imaging with Release 11.
  • Disable two-phase commit with Release 11.
Note: If you have OpenEdge Replication enabled, you must disable it before you can disable after-imaging. For information on Replication, see OpenEdge Replication: User Guide.

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 BI file is not truncated.
  • The database is online.
  • 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.
Note: If existing encryption uses the RC4 cipher (Cipher ID 7), conversion is cancelled and you will receive a message that the cipher is no longer supported. You must then either:

  • Use the PROUTIL EPOLICY utility to remove the RC4 cipher (Cipher ID 7) encryption from the encrypted objects, and PROUTIL EPOLICY UPDATE to retire the cipher; or

  • Use the PROUTIL EPOLICY utility to change the RC4 cipher (Cipher ID 7) to a stronger encryption cipher, and use the PROUTIL EPOLICY UPDATE and PROUTIL EPOLICY SCAN operations to re-encrypt the objects with the new policy and cipher.

These operations may be performed on either the existing OpenEdge Release 11 database or on a backup created at the time of conversion.

During the conversion:
  • If your database has after-imaging enabled, the conversion process disables it, and issues a message.
  • If your database has auditing enabled, it is temporarily disabled during the conversion, but re-enabled before the conversion completes.
  • If your database has encryption enabled, it is temporarily disabled, preventing access to the encryption cache and any encrypted data in the database. Encryption is re-enabled when the conversion completes, and access to the encryption cache and any encrypted data restored.
  • If your database has Change Data Capture (CDC) enabled, it is temporarily disabled, preventing CDC cache allocation and loading. CDC is re-enabled when the conversion completes.
  • All schemas in your database is updated to the latest version, and any new schema tables are added.
  • All existing 32-bit sequences are upgraded to 64-bit.

    Existing 32-bit sequences set to cycle at the limit, with the Unknown value (?) as the limit, are changed to cycle at the maximum or minimum value of a 32-bit integer (+/-2147483647), keeping the behavior of a cycling sequence consistent.

    Existing 32-bit sequences that do not have a cycle and the limit is the Unknown value (?), are changed to have an implied maximum or minimum of a 64-bit integer (+/-9223372036854775807).

    CAUTION: Verify any impact the sequence conversion may have on your application. Review your database sequence schema after the conversion completes, to verify initial and cycle settings, or take advantage of the 64-bit values.
  • All VSTs in your database are recreated and updated to the latest version, and any new VSTs are added.
  • New auditing events are populated.

Notes

  • CONV1112 must be run offline for a full conversion.
  • Large file support is enabled by default for databases created, copied, or opened using OpenEdge Release 12 and later.
  • If db-name is a UTF-8 database, you must specify -cpinternal UTF-8 on the command line. If not specified, an error message is generated and CONV1112 exits.
  • As database conversion is a single-user operation, the caches for multi-tenancy and OE Authentication Gateway are not allocated or loaded. Conversion does not involve these features.
  • After completing the conversion, back up your OpenEdge Release 12 database as soon as possible.
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.