Feedback
Did this article resolve your question/issue?

   

Article

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

Information

 
TitleConsiderations when upgrading from OpenEdge 11 to a later OpenEdge 11 version.
URL NameConsiderations-when-upgrading-from-OpenEdge-11-to-a-later-OpenEdge-11-version
Article Number000136575
EnvironmentProduct: 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:
  1. 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:
  1. Truncate the bi file:  proutil dbname -C truncate bi
​Relevant Knowledgebase Articles:
  1. 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.
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: 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

References to Other Documentation:

Progress Article(s):

 How to shut down a database remotely
 How to disallow a database from being shutdown remotely?
How to disconnect any database user from a remote machine using an AppServer
How to disconnect all self and remote users from a database?
 "What happens during PROSHUT -by and PROSHUT -F?"
How to disconnect a database user with PROSHUT or PROMON
 Is it possible to terminate broker without shutting down DB?
 Can I shut down a secondary login broker without shutting down the entire database?
 How to terminate a remote server process?
 How to shut down the remote Fathom dbagent without stopping the database.
 How to shut down the Database and Adminserver on Windows 2008 when the system is restarted
 Is it possible to terminate broker without shutting down DB?
 Does shutting down OpenEdge Management affect running databases?  How the primary recovery (.bi) file works
 What is the limit on file size for PROBKUP on disk ?
  How to upgrade OpenEdge Management? Migrating Progress versions, is it possible to use conmgr.properties and ubroker.properties from the previous version with the new version of Progress?
How to maintain ubroker.properties, conmgr.properties and other property files with the mergeprop utility
How To Configure Multiple Versions of AdminServer To Be Run Concurrently since OpenEdge 10.1B
 
Last Modified Date2/17/2021 7:13 PM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.