For conversion without a replication rebase, source and target databases must meet certain requirements. The conversion utility CONV1213 performs a pre-scan to validate conversion readiness. If it detects any blocking conditions, the utility exits without modifying the database. You must resolve all reported issues before proceeding. You must correct all reported issues before CONV1213 can successfully complete. Conditions that cause the pre-scan to exit include:

  • Ensure the database is a valid OpenEdge Release 12 database. Databases from earlier releases are not supported.
  • Perform a full backup of the source database using OpenEdge 12 tools. If the user declines to confirm a backup, the utility will verify that the database remains unaltered.

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

  1. Back up your OpenEdge Release 12 source database using a Release 12 backup utility.
  2. Verify that the source database is not in use, and that all transactions have committed or rolled back.
  3. Ensure that replication is enabled on both source and target and remains enabled on both source and target during conversion.
  4. Verify that the source and target databases are synchronized. Synchronization between source and target databases is critical. You can achieve this using either of the following methods:

    Option 1: Double shutdown

    To synchronize the source and target databases before conversion, follow these steps:
    1. Shut down both source and target(s) before the conversion.
    2. Restart source and target.
    3. Wait for synchronization to be completed. Check the log files for the message that synchronization has completed.
      1. 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.
      2. 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 targets immediately after synchronization completes. Ensure 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 or shutdown and conversion do not replicate to the target database. The conversion of the target database will fail due to validation checks performed during conversion.
    Option 2: Use the -replSync parameter

    To synchronize the replication source and target databases using the -replSync parameter, follow these steps:

    1. Ensure the replication source and server are running, and all targets are connected.
    2. On the replication source database, run the PROSHUT command with the following syntax:
      proshut -shutdownTimeout sourcedb-name -replSync

      The system default timeout is ten minutes. Use the optional -shutdownTimeout parameter to specify a timeout value that allows active users to finish. Adjust the timeout as needed. If synchronization fails within the timeout, the system prompts you to extend or force shutdown, which may cause inconsistent data or synchronization failure.

      For example, this command shuts down sourcedb in 40 minutes:
      proshut -shutdownTimeout 40m sourcedb -replSync

      For information, see PROSHUT command.

      Successful synchronization is confirmed with messages like:
      BROKER  0: (20258) Database broker has verified that all written AI locations were sent to replication target databases. 
RPLS    1: (10436) The source database and the target database are synchronized. 
RPLS    1: (20257) Replication server has verified that all connected replication target databases are synchronized.
      Note: Do not allow any new transactions after synchronization. Any changes made between synchronization and conversion will not be replicated and may cause the conversion to fail.
    3. To ensure the replication target database is offline before conversion, run the PROSHUT:
      proshut targetdb-name -by
  5. Truncate the BI file of the replication source with OpenEdge Release 12.
    Note: If you forgot to truncate the OpenEdge Release 12 database after installing OpenEdge Release 13 in the new installation and need to convert your OpenEdge Release 12 databases to OpenEdge Release 13, you should:
    1. Copy the 128_dbutil utility from <install-dir>/bin/128dbutils/ to <install-dir>/bin.
    2. Use this utility to truncate the BI areas on the databases before starting the conversion process.
    This step is required because the External Security Administration Manager (ESAM) does not support running utilities from subdirectories under <install-dir>/bin.
    For example, if you attempt to run:
    $DLC/bin/128dbutils/128_dbutil sports -C truncate

    Where, $DLC is an environment variable that points to the OpenEdge installation directory and in this case, it resolves to <install-dir>.

    You may encounter the following error:
    ESAM action error (00000009): {00000045} The client's DLC path does not appear to be an OpenEdge installation
ESAM validation of DLC failed.
    Workaround: Copy 128_dbutil to <install-dir>/bin and run it from there.

    For instructions, see PROUTIL TRUNCATE BI qualifier.