Consistency Verification
Warning, this tool returns results whose interpretation can be difficult, in particular for certain standard tables. It is therefore advised that, when the log file lines are returned, to contact the support in order to verify if the anomalies identified are real and require maintenance, of if these are normal within the context.
The ADONIX X3 data dictionary describes the links between tables. These links are tested by the update programs, but they are not, for reasons of portability between databases, described in the database itself as referential integrity constraints. In order to be able to verify that these constraints are satisfactory, it is possible to use this utility, which is used to exhaustively to test the line links to other tables for each line in each table.
Taking into account the number of tables, the potential number of lines in a table and the number of lines to be tested, the execution of this utility in an exhaustive fashion can be extremely long. It is often advisable to limit the tests to be carried out.
The result of the test is a log file, in which are found any anomalies. It is advisable to examine in a detailed fashion the anomalies in order to take the appropriate maintenance measures if required.
Warning, if anomalies exist in the data dictionary description (for example following specific/custom developments), it is possible that "false errors" exist. It is necessary to be very prudent in the interpretation of the results of this test.
Screen management
The start of this function is made in a single window.
Entry screen
Presentation
The following parameters are found :
Folder
This is the folder in which the control must be carried out. By default, the current folder is proposed, however it is possible to give the name of another accessible folder, using the following syntax :
FOLDER (the name of the folder directly : in this case, the folder is supposed to be directly accessible on the same server and the same service).
server@FOLDER (the network name for the server where the folder is located should be given : An adxd service must work on the current service number to allow the connection).
server:service@FOLDER (same principle as above, but the service number can be different. This gives, for example, the syntax server_01:1802@DEMO).
Warning: the last two syntaxes assume that there exists on the remote server a folder having the same name as the folder from where the function is run (even if it is not in this folder that the operation will be launched). This condition is always fulfilled on leaving the supervisor folder, since any installation assumes that as a minimum the supervisor folder is installed. (this folder can take various names according to the installed product, for example X3, PAYE, GX ). Therefore it is advised that this syntax is used only in this case. In addition, according to the network configurations, entering an incorrect network name can trigger a long wait time after entry of the field (since the check on server existence is made on the network, a delay in the order of one minute, sometimes several minutes occurs before an error message is received).
Start/End table
This the range used to limit the control to a group of tables. If coherence of only a single table is to be checked, the code for this table is used for both the start and end. If the start range is not assigned, the check starts at the first table, and if the end range is not assigned, the checks will be made up to the last table.
Module
It is possible place a filter on the tables concerning one or more modules (the filter is made by responding Yes or No for each module. The test will be made on each table as a function of the module field present in the table dictionary.
Close
Fields
The following fields are present on this tab :
Block number 1
| This field is used to define the folder in which the utility is launched. The possible syntaxes are described in the dedicated appendix. |
Block number 2
| Used to give a range between two values for the code to be controlled by the utility. |
|
|
| List of modules in the software. |
| This grid is used to define (by responding Yes for the lines concerned) the tables to be analyzed by filtering by functional module. |
Close
Functions accessed by right click on the grid
Yes to all the rest
No to all the rest
Error logs
No error message is displayed on the screen, rather error messages are presented in the following form:
Anomalies in the XXXXXX table
Key : KEY_RECORD Incorrect link INCORRECT_FIELDto LINKED_TABLE_NAME (LINK_KEY_VALUE)
This signifies that in the XXXXXX table, in the key record KEY_RECORD, the INCORRECT_FIELD field points to a non-existent key (LINK_KEY of table, LINKED_TABLE_NAME. For example if in the customer table (BPCUSTOMER), the customer JOHNDOE has as sales representative (REP field) with the code UNKNOWN that does not exist. The log file will display the following message:
Anomalies in the BPCUSTOMER table
Key : JOHNDOE Incorrect link REP to SALESREP (UNKNOWN)
Tables used
Potentially, all the tables can be used by this function.
Fermer