The conv1213 utility lets you convert replication-enabled databases from OpenEdge Release 12 to OpenEdge Release 13 without requiring a rebase of the target databases.
CAUTION: Before you begin, make sure that you complete the steps in Prepare to convert replication-enabled databases from OpenEdge 12 to OpenEdge 13.

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 12 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 12.3 or later to Release 13, as long as the changes are limited to the schema area.

To convert the schema of a replication target database:
  1. Run the conv1213 utility offline with replsource on the OpenEdge Release 12 source database. For example, to create a backup file named schema.bk for the replication-enabled sports2020 database:
    proutil sports2020 -C conv1213 replsource schema.bk

    For information, see PROUTIL CONV1213 REPLSOURCE qualifier.

  2. Next, run the conv1213 utility offline with repltarget on the OpenEdge Release 12 target database with the same schema backup file created from the replsource:
    proutil sports2020 -C conv1213 repltarget schema.bk

    For information, see PROUTIL CONV1213 REPLTARGET qualifier.

    Note: The conversion requires the same backup file for both the conv1213 replsource and conv1213 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.
  • If AI archiver was enabled on source or target 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 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.