The conv1112 utility lets you convert replication-enabled databases from OpenEdge release 11.x to OpenEdge release 12.3 without requiring a rebase of the target database(s).

CAUTION: Before you begin, make sure that you complete the steps in Prepare to convert replication-enabled databases.

By avoiding a time-consuming rebase, a database schema conversion is potentially faster than a full database conversion. You can convert without rebase when the only database changes from OpenEdge Release 11 are in the schema area. OpenEdge Release 12.3 is the earliest release that supports conversion without rebase. For example, you can run a schema conversion to convert a replication-enabled database from Release 11.x to Release 12.3 or later, as long as the changes are limited to the schema area.

To convert the schema of a replication target database:

  1. Run the conv1112 utility offline with replsource on the OpenEdge Release 11.x source database. For example, to create a backup file named sports2020schemabk for the replication-enabled sports2020 database:: 
    proutil sports2020 -C conv1112 replsource schema.bk
    For details, see PROUTIL CONV1112 REPLSOURCE qualifier in Manage the OpenEdge Database.
  2. Next, run the conv1112 utility offline with repltarget on the OpenEdge Release 11.x target database with the same schema backup file created from the replsource. 
    proutil sports2020 -C conv1112 repltarget schema.bk
    For details, see PROUTIL CONV1112 REPLTARGET qualifier in Manage the OpenEdge Database.
    Note: The conversion requires the same backup file for both the conv1112 replsource and conv1112 repltarget commands.
    During the conversion:
    • If After-imaging was enabled on the target database prior to the conversion, it is enabled after the conversion. Otherwise, it remains disabled.
    • AI extents existing on disk prior to conversion are converted and usable with the OpenEdge replication source after conversion.
    • If your encryption is enabled on your database, it is temporarily disabled, preventing access to the encryption cache and any encrypted data in the database. Conversion completion re-enables encryption and restores access to the encryption cache and any encrypted data.
    • 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.
    • Auditing for your database, if previously enabled, is temporarily deactivated. After the conversion completes, auditing is enabled again.
    • All schemas in your database are 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 virtual system tables (VSTs) in your database are recreated and updated to the latest version, and any new VSTs are added.
    • New auditing events are populated.

    After conversion and restarting the replication in OpenEdge Release 12.3 or later, the source and target databases can connect and synchronize.