Messages relating to execution during the analysis phase
CHECK OF INDICES IS IMPOSSIBLE WITHOUT TOTAL CHECK OF THE DATABASE: THE INDEX CLAUSE IS IGNORED.
Meaning
During incremental checking, consistency criterion 6 cannot be checked (correct chaining of table pages between levels with respect to their index values).
FOR INDEX CHECKS A SORTING MUST BE PERFORMED EVEN FOR THE SUMMING PROCEDURE.
Meaning
In an index check the check records must be sorted, even for a summing check. During input analysis it is determined that consistency criterion 6 is to be checked (correct chaining of table pages between levels with respect to their index values).
***** THE INPUT IS CORRECT, THE CHECK RUN IS STARTING NOW.
Meaning
Input analysis did not generate any error messages. Actual consistency checking is beginning.
Messages relating to the realm currently being processed
***** ANALYSING NEW STATE OF REALM realm-name FROM FILE file-name. number NON EMPTY BLOCKS HAVE BEEN ANALYSED.
Meaning
Total checking, with statistical information. If no DBTT anchor pages, no DBTT pages, no CALC pages and only empty data pages exist, only administration data must be checked in the realm. In this case only this check is performed, but no message is issued for the realm.
***** ANALYSING NEW STATE OF REALM realm-name FROM FILE file-name AGAINST OLD STATE FROM FILE file-name. number CHANGED BLOCKS HAVE BEEN ANALYSED.
Meaning
Incremental check ORIG/COPY <-> COPY, with statistical note
Messages for the sort phase
***** SORTING STARTED DATE AND TIME YYYY-MM-DD HH:MM:SS
***** SORTING COMPLETED DATE AND TIME YYYY-MM-DD HH:MM:SS
Meaning
These messages are output to SYSOUT and SYSLST immediately before and after all check records have been sorted. The following actions are performed between the two messages:
DB access with the local consistency checks and generation of the check records
Sorting of the check records
Evaluation of the check records and, if required, generation of the consistency error messages
Messages relating to consistency checking in summing checks
| ||
|
type-no
Designates the consistency criteria for which BCHECK has detected consistency errors (see "Selecting criteria for the global consistency check (TYPE)")
ref-no
Designates the record types that are faulty with respect to consistency criteria 1-8
type-no =1 Record type for the faulty DBTT
type-no =2-8 Owner record type for the corresponding set
0000-rsq
Output in conjunction with ref-no =0; designates the DB key of an anchor record.
key-length
Output with consistency criteria 9 and 10; designates the length of the CALC key.
dbtt-column-no
Output with consistency criterion 11; designates the column number in the DBTT
area-ref
Output with consistency criteria 9-11
type-no = 9,10 Realm in which the indirect CALC table is located.
type-no = 11 Realm in which the duplicates table is located.
SUMMARY report
| |
| refers to the warnings refers to the error messages refers to the system error messages |
If a consistency check was possible, additional statistical messages are issued:
number RECORD/TABLE ...
Number of references checked from the actual key in a DBTT column to the record or to the highest table page or first table page (consistency criterion 1; see "Selecting criteria for the global consistency check (TYPE)")
number CHAIN-SET-...
Number of records checked
- in a set MODE IS CHAIN including the owner record (consistency criterion 2)
- in a set MODE IS CHAIN LINKED TO PRIOR including the owner record (consistency criterion 3)
number REFERENCES BETWEEN ...
Number of references checked between
- the first table page and the last table page at level 0 (consistency criterion 4)
- the table pages between levels (consistency criterion 5)
- the table pages between levels with respect to their index values (consistency criterion 6)
- the table pages within one level (consistency criterion 7)
- a CALC table overflow chain (consistency criterion 10)
- a duplicates table overflow chain (consistency criterion 11)
number REFERENCES FROM ...
Number of references checked from
- table entries at level 0 to the records (consistency criterion 8)
- the indirect table entries to the records (consistency criterion 9)
number LOCAL CHECKS HAVE BEEN DONE ...
Total number of local checks performed in all the realms to be checked.
number USERKEYS BETWEEN TABLES AND MEMBER-RECORDS HAVE BEEN CHECKED
Number of checks output under REFERENCES FROM TABLES ... which were executed with key value check.
Local check:
{ NO | number } { EASY (MINOR) | FATAL (SERIOUS, STRUCTURAL)} LOCAL CONSISTENCY ERRORS.Number of consistency errors which BCHECK has discovered in the database during the check run:
EASY (MINOR) LOCAL CONSISTENCY ERRORS
Less important consistency errors, i.e. local errors that do not impede database operation.FATAL (SERIOUS, STRUCTURAL) LOCAL CONSISTENCY ERRORS
Severe consistency errors, i.e. local errors that must be rectified since they impair or prevent correct database operation.SERIOUS identifies an error which generally only affects a single object contained on a page.
STRUCTURAL indicates that several objects on a page are affected, or the page as a whole; as a result a large number of global consistency errors can be reported just for this one page.
Summing check:
{ NO GLOBAL CHECK HAS BEEN DONE | NO GLOBAL CONSISTENCY ERRORS | GLOBAL CONSISTENCY ERRORS. DO A SORTING CHECK }These messages refer to consistency criteria 1-5 and 7-11; see "Selecting criteria for the global consistency check (TYPE)".
{ NO GLOBAL INDEX CHECK HAS BEEN DONE | { NO | number } GLOBAL CONSISTENCY ERRORS IN INDEX CHECK }These messages refer only to consistency criterion 6 (Correct chaining of table occurrences between levels in terms of index values (Selecting criteria for the global consistency check (TYPE))).
Sort check:
{ NO GLOBAL CHECK HAS BEEN DONE | { NO | number } GLOBAL CONSISTENCY ERRORS }Number of global consistency errors with respect to consistency criteria 1-11; see also "Selecting criteria for the global consistency check (TYPE)".
*****END OF DIAGNOSTIC SUMMARY
Meaning
End of the SUMMARY report