Salesforce

How to disable site replication before migration when the prior version is not installed

« Go Back

Information

 
TitleHow to disable site replication before migration when the prior version is not installed
URL NameHow-to-disable-site-replication-before-migration-when-the-prior-version-is-not-installed
Article Number000136558
EnvironmentProduct: OpenEdge
Version: All supported versions
OS: All supported platforms
Question/Problem Description
How to disable site replication before migration to the next major version when the prior version is not installed
How to disable replication when the prior major version is not installed on the server where the migration is taking place

Why does using 102b05_dbutil or 102b08_dbutil to disablesitereplication fail with error 10354
Why does using 117_dbutil to disablesitereplication fail with error 10354

Can't disable site replication with the dbutil executable provided in the DLC\bin\102dbutils directory.
Can't disable site replication with 117_dbutil from DLC\bin\117dbutils directory.
Steps to Reproduce
Clarifying Information
Error MessageReplication (<type>) cannot be disabled for database <db-name> because it is not already enabled. (10354)
Defect Number
Enhancement Number
Cause
Resolution
To disable site replication before migration to the next major version when the prior version is not installed

Performing a migration from an older version to a newer version requires replication and after-imaging to be disabled before performing the migration.

OpenEdge provides earlier Major version executables in the install-dir\bin\*dbutils folders. The purpose of the *dbutils directory is to allow DBA's the capability to use the new installation to perform necessary steps to migrate older databases, when the prior version is not installed on the server where the migration is taking place, by being able to run basic _dbutil instruction from the command line. 

It is important to note these executables will fail when the database to be converted is enabled for any features that require a specific OpenEdge license (TDE, OER, MT, TP) or is enabled for features only an Enterprise Database license provides. For example the license information in this directory does not provide rights to perform operations against a large file enabled database which requires an Enterprise Database License or a Replication Enabled database which requires an OpenEdge Replication License:
  • In Progress 9 and earlier, the progress.cfg included in the 91dbutils is a Query Results license
  • Since OpenEdge 10 the NameServer license is provided in the *dbutils progress.cfg
  • Since OpenEdge 12 a license file (progress.cfg) is not provided with in the DLC/bin/*dbutil directory and use the current licenses.  


Option 1: To disable replication, use an installation which has the full OpenEdge Replication license installed.

These utilities will use the current OpenEdge licenses where an OpenEdge Replication license is required. By default the from dlc/progress.cfg is used otherwise set the PROCFG environment variable. This can be confirmed by running 'showcfg'.

for example:
cd /db
$DLC/bin/117_dbutil.exe <dbname> -C truncate bi
echo y | $DLC/bin/dbutils/117_dbutil.exe <dbname> -C disablesitereplication source
rm <dbname>.recovery
echo y | $DLC/bin/dbutils/117_dbutil.exe <dbname> -C aimage end
$DLC/bin/dbutils/117_dbutil.exe probkup <dbname> 1112.back
echo y | proutil <dbname> -C conv112
 

Once the database has been migrated, re-enable replication:

Option 2: To disable replication, use the PROCFG environment variable to use the earlier version's executables in DLC/bin/*dbutils

If the purpose of the migration is to no longer have the database enabled for replication. Use the License Configuration file from the previous version which contains the OpenEdge Replication (and Enterprise RDBMS license if required) and use *it* instead of the progress.cfg that is provided with the DLC/bin/*dbutil utilities. As described above, similar failures will occur when the database to be converted is enabled for any features that require a specific OpenEdge license (TDE, OER, MT, TP) or is enabled for features only an Enterprise Database license provides.

1. Copy the progress.cfg from the production environment which has the full OpenEdge Replication license installed, to the dlc/*dbutils directory of the next major version OpenEdge installation:
  • 102dbutils/progress.cfg
  • 117dbutils/progress.cfg
2. Use the PROCFG environment variable to use the earlier version's executables in DLC/bin/*dbutils

For example:
cd $DLC/bin/dbutils
DLC=`pwd`;export DLC
PROCFG=$DLC/progress.cfg;export PROCFG
PATH=$DLC:$PATH;export PATH
cd /db
117_dbutil <dbname> -C truncate bi
117_dbutil <dbname> -C disablesitereplication source
rm <dbname>.recovery

117_dbutil <dbname> -C aimage end
117_dbutil.exe probkup <dbname> 1112.back
cd $DLC/bin
DLC=`pwd`;export DLC
PROCFG=$DLC/progress.cfg;export PROCFG
PATH=$DLC:$PATH;export PATH
echo y | proutil <dbname> -C conv112

When the prior version is available replication can simply be disabled with the current executable:
Workaround
Notes
Keyword Phrase
Last Modified Date11/20/2020 6:52 AM

Powered by