The pdconstck processing results include the processing results of integrity checking and information about the check pending status. The following is an example of the pdconstck processing results:

 
            [1]                                  [2]       [3]
 pdconstck VV-RR *** DB VALIDATION CHECK *** yyyy-mm-dd hh:mm:ss
 processing-results-of-integrity-checking [4]
 information-about-check-pending-status [5]
 pdconstck TERMINATED, RETURN CODE=0[6]
 

Explanation

1. HiRDB version number
2. pdconstck execution start date
3. pdconstck execution start time
4. Processing results of integrity checking
5. Information about check pending status
6. pdconstck's return code

The execution results of the integrity check facility are output by pdconstck as the integrity checking processing results. This information is output when -k check is specified.

The following shows an output example of the processing results of integrity checking:

 
 ** DB VALIDATION CHECK INFORMATION **
 processing-results-of-integrity-checking-on-referential-constraints [1]
 processing-results-of-integrity-checking-on-check-constraints [2]
 

Explanation

1. Processing results of integrity checking on referential constraints
2. Processing results of integrity checking on check constraints
   These are the processing results of executing integrity checking on check constraints. This information is output when the -t option is specified and check constraints have been defined for the table, or when the name of a check constraint is specified in the -c option.
   

(a) Processing results of integrity checking on referential constraints

The processing results of integrity checking on referential constraints are output in alphanumeric order of the constraint names when the -t option is specified and referential constraints have been defined for the table, or when the name of a referential constraint is specified in the -c option.

The following shows an output example of the processing results of integrity checking on a referential constraint:

 
      ** REFERENTIAL CONSTRAINT INFORMATION **
      CONSTRAINT    = SCHEMA1.CONST1 [1]
      REFERENCED  TABLE = SCHEMA1.P1 [2]
      REFERENCING TABLE = SCHEMA1.F1 [3]
      [5]              [6]
[4] - NO.  FOREIGN KEY COLUMN NAME
   | ---- ------------------------------
   |  1   COL1
    - 2   COL2
 
      execution-results  [7]
 

Explanation

1. Name of a constraint (authorization-identifier.constraint-name)
2. Name of the referenced table (authorization-identifier.table-identifier)
3. Name of the referencing table (authorization-identifier.table-identifier)
4. Column information for foreign keys
5. Definition order
6. Column names (in the order that the foreign key component columns are defined)
7. Execution results
   These are the results of integrity checking on the constraint. This information is not output for a constraint whose integrity was not checked.
   When the inner replica facility is not used, only one set of the information items is output; when the inner replica facility is used, as many sets of the information items are output as there are generations on which integrity checking was executed, in ascending order of the original RDAREA generations (from 1 to 10). The following shows an output example of the results of integrity checking on referential constraints, both when there are no violation key values and when there are violation key values.
   

Execution results when there are no violation key values

 
 GENERATION    = 0 [1]
 NO ERROR FOREIGN KEY [2]
 

Explanation

1. Number of the generation on which integrity checking was performed
   When the inner replica facility is not used, this information is not output. When pdconstck was executed by current RDAREA, CUR is output.
   
2. Indicator that there were no violations foreign key values.

Execution results when there are violation key values

 
      GENERATION    = 0 [1]
      [3]          [4]
[2] - NO.   ERROR FOREIGN KEY
    |----- -----------------
    |   1   1234567890
    |       Taylor
    |   2   777
     -      Young
      PROCESSING DISCONTINUED [5]
      EXIST ERROR FOREIGN KEY [6]
 

Explanation

1. Number of the generation on which integrity was checked
   When the inner replica facility is not used, this information is not output. When pdconstck was executed by current RDAREA, CUR is output.
   
2. Information about the violation key values (in the order of the primary key values referenced by the foreign key).
3. Sequence numbers of the violation keys (in ascending order starting with 1)
   The violation key values are output in the order of the column names of the foreign key. If there are multiple columns composing the foreign key, only the first key value is output.
   
4. Violation key values
   A violation key value is displayed in character format in the default character set (in the case of a character string data type for which a character set is specified, a violation key value is converted to the default character set and then is displayed).
   In the case of a character data type, only the first 70 bytes are output as a violation key value. A national character that ends in byte 71 is not output.
   
5. Indicator that integrity checking was cancelled.
6. Indicator that violation foreign key values were found.

(b) Processing results of integrity checking on check constraints

The processing results of integrity checking on check constraints is output when the -t option is specified and check constraints have been defined for the table, or when the name of a check constraint is specified in the -c option.

The following shows an output example of the processing results of integrity checking on a check constraint:

 
      ** CHECK CONSTRAINT INFORMATION **
      CONSTRAINT = SCHEMA1.CONST2 [1]
      TABLE      = SCHEMA1.TABLE1 [2]
      [4]            [5]
[3] - NO.    CHECK KEY COLUMN NAME
   | ---- ------------------------------
   |  1   COL1
    - 2   COL2
 
      execution-results [6]
 

Explanation

1. Name of a constraint (authorization-identifier.constraint-name)
2. Name of the table (authorization-identifier.table-identifier)
3. Column information in the search conditions (in the order stored in the SQL_CHECK_COLUMNS data dictionary table)
4. Sequence numbers assigned to the column information
5. Column names
6. Execution results
   These are the results of integrity checking on the constraint. This information is not output for constraints whose integrity was not checked.
   When the inner replica facility is not used, only one set of information items is output; when the inner replica facility is used, as many sets of information items are output as there are generations on which integrity checking was executed, in ascending order of the original RDAREA generations (from 1 to 10).
   The following shows an output example of the results of integrity checking on check constraints, both when there are no violation key values and when there are violation key values.
   

Execution results when there are no violation key values

 
 GENERATION    = 0 [1]
 NO ERROR CHECK KEY [2]
 

Explanation

1. Number of the generation on which integrity was checked
   When the inner replica facility is not used, this information is not output. When pdconstck was executed by current RDAREA, CUR is output.
   
2. Indicator that there were no violation foreign key values.

Execution results when there are violation key values

 
      GENERATION    = 0 [1]
      [3]          [4]
[2] - NO.   ERROR CHECK KEY
    |----- -----------------
    |   1   1234567890
    |       Taylor
    |   2   777
     -      Young
      PROCESSING DISCONTINUED [5]
      EXIST ERROR CHECK KEY [6]
 

Explanation

1. Number of the generation on which integrity was checked
   When the inner replica facility is not used, this information is not output. When pdconstck was executed by current RDAREA, CUR is output.
   
2. Information about the violation key values (in the order of integrity checking on check constraints)
3. Sequence numbers of the violation keys (in ascending order starting with 1)
4. Violation key values
   A violation key value is displayed in character format in the default character set (in the case of a character string data type for which a character set is specified, a violation key value is converted to the default character set and then is displayed).
   If the data type of the column that constitutes the check constraint is BLOB or BINARY, only the first 35 bytes of the violation key value are displayed (in hexadecimal). If the data type of the column that constitutes the check constraint is neither BLOB nor BINARY, the violation key value is displayed in the data format.
   In the case of a character data type, only the first 70 bytes are output as a violation key value. A national character that ends in byte 71 is not output.
   
5. Indicator that integrity checking was cancelled.
6. Indicator that violation foreign key values were found.

Regardless of the -k option's value, the check pending statuses of the table and check constraints are output. An output example of check pending status information is shown below. Note that the check pending status of each RDAREA is not output. For the check pending status of each RDAREA, check pddbst's status analysis by RDAREA (logical analysis) or status analysis by table.

 
 ** CHECK PENDING STATUS INFORMATION **
                                                [2]            [3]
 TABLE                                   CONSTRAINT TYPE PENDING STATUS
 SCHEMA1.T5 [1]
                                         REFERENCE       PENDING
                                         CHECK           RELEASE
                                                [2]            [3]
 CONSTRAINT                              CONSTRAINT TYPE PENDING STATUS
 SCHEMA1.CONST1 [4]                      REFERENCE       PENDING
 SCHEMA2.CONST2 [4]                      CHECK           RELEASE
 

Explanation

1. Table name
2. Type of constraint:
   REFERENCE: Referential constraint (if no referential constraints have been defined, this information is not output)
   CHECK: Check constraint (if no check constraints have been defined, this information is not output)
   
3. Check pending status:
   PENDING: Check pending status
   RELEASE: Non-check pending status
   
4. Constraint name:
   Outputs the names of the referential constraints and then the check constraints that have been defined for this table, in ascending alphanumeric order of the constraint names.