For conversion without a replication rebase, source and target databases must meet certain requirements.

The conversion utility 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.
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.

To ensure that your source and target databases meet requirements for replication, follow these steps:

  1. Back up your OpenEdge Release 11 source database using a Release 11 backup utility.
  2. Verify that the source database is not in use, and that all transactions have committed or rolled back.
  3. Make sure that replication is enabled on both source and target, and remains enabled on both source and target during conversion.
  4. Make sure that after-imaging is enabled on the source, and remains enabled during conversion.
  5. If after-imaging is enabled on the target(s), leave it enabled during conversion. If after-imaging is disabled on the target(s), leave it disabled during conversion.
  6. Verify that the source and target databases are synchronized:
    1. Shut down both source and target(s) before the conversion.
    2. Restart source and target(s).
    3. Wait for synchronization to complete. Check the log files for the message that synchronization has completed.
      Restart the replication source database and look for the following message in the sourcedb.lg or the sourcedb.repl.server.lg file
      (10436) The source database [source] and the target database [target] on host [hostname] are synchronized.
      Restart the replication target database and look for the following message in the targetdb.lg or the targetdb.repl.agent.lg file
      (10668) The Source and Target databases are synchronized.
    4. Shut down both source and target(s) immediately after synchronization completes. Make sure that no new transactions start on the source, or the target can lose synchronization with the source again.
      CAUTION: Do not allow new transactions after synchronization. Changes to the source database between synchronization/shutdown and conversion do not replicate to the target databases. The conversion of the target database will fail due to validation checks performed during conversion.
  7. Truncate the BI file of the replication source with OpenEdge Release 11.
    For instructions, see PROUTIL TRUNCATE BI qualifier in Manage the OpenEdge Database.
Now you are ready to convert your replication-enabled source and target databases, as described in Convert replication-enabled databases without target rebase.