Kbase 91406: Settings verification
| Autor |
Tatiane Koslinsky - CAT |
| Acesso |
Público |
| Publicação |
26/09/2017 |
|
Settings verification consists of whether the source database that will be updated has updated settings up to the expected package. This is possible using the file from directory '... \ package-update \ cax \' corresponding to the database.
The console can identify one of the following four potential errors:
- Absent: when the client database does not have an expected table in any database.
- Different: when a table has different CRC from the table CRC in the product release.
- Index: when the difference is at some table index.
- Synchronism: when a Schema Holder is not synchronized with the Oracle database. This verification is for Oracle database only.
Click 'View log' in the left side menu to know more.
The console shows only rows with errors. If there are no errors, the list of tables will be empty at the end of the process.
If an application server is available, you can select the option to run the check in Appserver. Otherwise, the option will be disabled. Only the first application server registered is 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 checks 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.