Title	Considerations when upgrading from OpenEdge 11 to a later OpenEdge 11 version.

URL Name	Considerations-when-upgrading-from-OpenEdge-11-to-a-later-OpenEdge-11-version

Article Number	000136575

Environment	Product: OpenEdge Version: 11.x OS: All supported platforms Other: Upgrade

Question/Problem Description

Considerations when upgrading between versions 11.0, 11.1, 11.2, 11.3, 11.4, 11.5, 11.6, 11.7.
Upgrade considerations for OpenEdge 11.x to a later minor version
Migrating between minor released in OpenEdge 11.

Steps to Reproduce

Clarifying Information

Error Message

Defect Number

Enhancement Number

Cause

Resolution

The following are a few considerations when upgrading from one 11.x release to another on the same machine.
This Article is not designed to identify all upgrade steps that need to be performed. Instead the purpose of this Article is to make the reader aware of areas for consideration when upgrading from one release to another release in the same major version ie. OpenEdge 11.x.

Databases:

Shutdown the databases being used prior to migration: proshut dbname -by or dbman -i -stop

This can be done by simply:

proshut <dbname> [-by]

Unless the database was started using the AdminService (i.e. dbman or thru OEE/OEM)

dbman <config> -stop

Relevant Knowledgebase Articles:

Truncate the bi file: proutil dbname -C truncate bi

Relevant Knowledgebase Articles:

Ensure a valid backup prior to migration.

Relevant Knowledgebase Articles:

Ubrokers:

Stop all Ubrokers (NameServer, AppServers, Webspeed etc.) using the appropriate *man command for the Broker. Example: wtbman -stop, asbman -stop, nsman -stop

AdminServer:

Stop the AdminServer. Example: proadsv -stop

Property files:

Backup properties files in $DLC/properties or %DLC%\properties as this information may be needed when migrating to the later release. Example: ubroker.properties, AdminServerPlugins.properties, conmgr.properties etc.

OpenEdge Management:

Backup the fathom.db if historical trending information will be needed. It is an OpenEdge database so the steps identified above apply.
Backup the OpenEdge (Fathom) Management configuration information. See Article: How to upgrade OpenEdge Management?

General Info:

Remove or archive the older version of OpenEdge.

(NOTE: While removal is not required it can simplify many aspects of management if scripts exist for the existing location of a Progress installation.)

Relevant Knowledgebase Articles:

Install the newer version of OpenEdge in either the same or new directory.
Review the Release Notes for the new commercial release and their service pack versions via the OpenEdge Documentation site.

Property files:

For property files like ubroker.properties and conmgr.properties it is not recommended to use the mergeprop utility to migrate changes from one parameter file into another. This utility is not recommended as newer parameters could have been added to later releases for example. See Article Migrating Progress versions, is it possible to use conmgr.properties and ubroker.properties from the previous version with the new version of Progress?
Other parameter files are tailored to the install. However customized changes may have been made for the environment in the earlier version. If there were, then modify as needed to accommodate the earlier customizations that were required for your environment. The mergeprop utility can be used in this case to merge the customized lines with the later OpenEdge versions property file. For example, typically the AdminServerPlugins.properties file sets the minimum, maximum and related heap parameters for java in the jvmargs that are higher than the default values set by the install. Or IPV4 is explicitly preferred for TCP communications, a particular Network Card is hardcoded, or specific port and adminports are used which have been opened on the firewall. For an example of using mergeprop for the plugin, see Article How to maintain ubroker.properties, conmgr.properties and other property files with the mergeprop utility
If the site is going to maintain multiple versions of OpenEdge AdminServer on this machine, see Article: How To Configure Multiple Versions of AdminServer To Be Run Concurrently since OpenEdge 10.1B for information on ports that will need to be changed prior to starting the AdminServer.

OpenEdge Management:

Reload the OpenEdge (Fathom) Management configurations that were dumped earlier. This can be done with the fathom -load command.

Databases (including the fathom trend database):

There isn't a convert utility to use when upgrading between major releases, ie from one OpenEdge 11 release to another OpenEdge 11 release.
Starting the database will update the version information in the database.
Typically there is a need to update VST (Virtual System Tables) for these databases that may have been added to the newer release. The offline utility is: proutil dbname -C updatevst

Workaround

Notes