Nonstop Database, HiRDB Version 9 Command Reference

[Contents][Index][Back][Next]

7.5.5 Output of execution results listing

When an RDAREA is re-initialized, an execution results listing is output. The following shows an example of an execution results listing (table and index information):

                              1         2          9
pdmod -information-         yyyy-mm-dd  hh:mm:ss   dbl
 initialize rdarea name = 3 USER_PUBLIC_1
  initialized table
  4 USERA.STOCK
  USERA.EMPLOYEE
  initialized index               rdarea name
  5 USERA.EMPLOYEENO              6 USER_PUBLIC_1
     USERA.PNAME                    USER_PUBLIC_2
  unfinished index                rdarea name
   7 USERA.NAME                   8 USER_PUBLIC_1
 initialize LOB data(table name)  rdarea name
  10 USERA.STOCK                 11 USER_LOB_1
  initialized sequence
  12 USERA.PRODUCT_SEQUENCE_NUMBER
  pending status table            constraint name
  13 USERA.SALARY             14 *NAME1
     USERA.SECTION_CHIEF      15 NAME2
  release pending status table
  16 USERA.EMPLOYEE
  17 *USERA.PNAME
  access prohibited(LOB rdarea name) table name
  18 USER_LOB_2                  19 USERA.ADDRESS
 

Explanation
  1. Date pdmod was executed
    yyyy-mm-dd
    year month date
  2. Time pdmod was executed
    hh:mm:ss
    hour minute second
  3. Name of reinitialized RDAREA
  4. Table identifier in reinitialized RDAREA
    authorization-identifier.table-identifier
  5. Initialized index
    authorization-identifier.index-identifier
  6. Name of RDAREA from which index data was deleted
  7. Index placed in incomplete status (unusable status) after the index data was deleted
  8. RDAREA name of index placed in incomplete status (unusable status)
  9. HiRDB identifier
  10. Table identifier of LOB column structure base table
  11. Name of user LOB RDAREA
  12. Initialized sequence generator
  13. Name of the table placed in check pending status
  14. A constraint name with an asterisk (*) has been in check pending status since before the re-initialization was executed
  15. Name of constraint placed in check pending status
  16. Name of the table that was released from check pending status
  17. A table with an asterisk (*) indicates the name of a partitioned table that was released from check pending status#
  18. Name of user LOB RDAREA storing a column of an abstract data type with the LOB attribute that was placed in access-disabled status
  19. Name of table corresponding to the column of an abstract data type with the LOB attribute that was placed in access-disabled status
#
If a partitioned table has been released from check pending status, only table information for the RDAREA subject to re-initialization is released from check pending status. Other RDAREAs storing the partitioned table might still be in check pending status. Note that the dictionary table is not released from check pending status even when all other RDAREAs storing the partitioned table are in non-check pending status.