Feedback
Did this article resolve your question/issue?

   

Article

How to perform a schema upgrade with a runtime license

« Go Back

Information

 
TitleHow to perform a schema upgrade with a runtime license
URL NameP4760
Article Number000141955
EnvironmentProduct: OpenEdge
Version: 10.x, 11.x
OS: All supported platforms
Question/Problem Description
How to perform an Application Schema upgrade with a runtime license
How to use -rx to modify the database Schema with a runtime license
How to update a Windows 64-bit OpenEdge database schema using the Windows 32-bit GUI client installed with the database license.
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
Starting a progress session with -rx parameter allows getting access to Progress Procedure Editor.
  • Using -rx -p _dict.p allows access directly to the Dictionary UI
  • Using -rx -p _admin.p allows access directly to the Administration UI where a .df can be loaded.
  • Note - neither of these options allows access to "Table Contents (.d file)..." to load Dump/Load data.  This can only be used to Dump/Load schema changes .df files.  A full development license such as OpenEdge Development Studio or ABL Development license is necessary to dump data using The Data Dictionary or Data Administration tools.

If you need to only load schema changes from a .df do the following:

1. In your Development environment,create a program (<yourProgram>) containing the following:

RUN prodict\load_df.r (SESSION:PARAMETER).

2. Compile and save the r-code.

3. Deploy the r-code to the runtime environment.  As an alternative, the source code .p file can be deployed if it is encrypted with XCODE.

4. From the command line, start a session using -rx and run the following:

On Unix: pro <dbname> -rx -p <yourProgram> -param <yourdf.df>
On Windows from proenv: prowin32 <dbname> -1 -rx -p <yourProgram> -param <yourdf.df>
Workaround
Notes
Last Modified Date11/20/2020 7:17 AM
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.