Kbase 91409: Dictionary correction
| Autor |
Tatiane Koslinsky - CAT |
| Acesso |
Público |
| Publicação |
26/09/2017 |
|
Dictionary correction imports settings from databases that could not be created in the preparation stage: indexes, for example, that demanded to have new fields populated by the upgrade stage, will be created only in the correction stage.
With the console you can import these settings to a new Progress session. This option is required if the Progress license installed is not Full.
If the database is not Progress, you can set the console to open multiple concurrent sessions to the database to import settings. This option is not allowed with Progress OpenEdge because it does not support simultaneous DDL commands.
If an application server is available, you can select the option to import settings to the Appserver. Otherwise, the option will be disabled. If the database used is not Progress OpenEdge, the option is disabled as well. Only the first application server registered will be used.
You can run a script before executing the stage. The script is a command or a set of statements in an file executable by the operating system. The console does not address error or return of this script. The script will run through the same Appserver that runs the process if it has been flagged to be executed on an application server.
In multi-company environments with duplicate databases, all settings referring to single-company databases are doubled according to the companies entered at the beginning of the process.
The console enables the option to not execute this stage. Do not use this option unless explicitly recommended by the TOTVS technical support. Use the button if you want to execute the stage to start the process immediately, or the button to schedule stage execution to configure all processes of the console and leave the execution to the end.
Once you fix the data dictionaries, if an error occurs, the system creates a log file with the problem found.
Important: if you have already executed this stage at some point, you cannot execute it again, except when the database backup returns to repeat the conversion/update process.