2.85 pdorcheck (Check the application conditions for online reorganization)

Organization of this section
(1) Function
(2) Executor
(3) Format
(4) Options
(5) Rules
(6) Notes

(1) Function

The pdorcheck command checks whether or not all base tables in specified RDAREAs satisfy the following application conditions:

  1. At least one index has been defined that satisfies one of the following conditions:
    • Primary key index whose index component columns do not include a VARCHAR or MVARCHAR column with a definition length of 256 bytes or greater or a NVARCHAR column with a definition length of 128 characters or greater
    • Cluster key index with PRIMARY specified whose index component columns do not include a VARCHAR or MVARCHAR column with a definition length of 256 bytes or greater or a NVARCHAR column with a definition length of 128 characters or greater
    • Cluster key index with UNIQUE specified whose index component columns do not include a VARCHAR or MVARCHAR column with a definition length of 256 bytes or greater or a NVARCHAR column with a definition length of 128 characters or greater
    • Index for which UNIQUE is specified whose index component columns are all subject to the NOT NULL constraint and do not include a VARCHAR or MVARCHAR column with a definition length of 256 bytes or greater or a NVARCHAR column with a definition length of 128 characters or greater
  2. The table columns consist of only the following data types:
    INTEGER, SMALLINT, [LARGE]DECIMAL, FLOAT, SMALLFLT, CHAR, VARCHAR, NCHAR, NVARCHAR, MCHAR, MVARCHAR, DATE, INTERVAL YEAR TO DAY, TIME, INTERVAL HOUR TO SECOND, TIMESTAMP, BINARY, BLOB, SGMLTEXT, XML, FREEWORD
  3. If a LOB column has been defined for the table, the update log acquisition mode defined for the database in the LOB column storage RDAREA is the log acquisition mode (RECOVERY ALL).
  4. The table is not an audit trail table.

The command issues a message identifying a table that does not satisfy the application conditions.

You can execute the pdorcheck command only when HiRDB Staticizer Option has been installed and the pd_max_reflect_process_count and pd_inner_replica_control operands have both been specified in the system definition.

(2) Executor

HiRDB administrator

(3) Format

 pdorcheck {-r original-RDAREA-name[,original-RDAREA-name]...| -r ALL}

(4) Options

(a) -r original-RDAREA-name[,original-RDAREA-name]... ~<identifier> ((1-30))

Specifies the names of original RDAREAs that are to be checked for the application conditions.

Rules
  1. For the rules for specifying RDAREAs, see 1.5.2 Specification of RDAREAs in operation commands and utilities.
  2. Specify user RDAREAs and user LOB RDAREAs. If a temporary table RDAREA is specified, an error results.
  3. Specify only RDAREAs for which replica RDAREAs have been defined.
(b) -r ALL

Specifies that the application conditions are to be checked for all original RDAREAs.

(5) Rules

  1. The pdorcheck command can be executed only while HiRDB is active.
  2. The pdorcheck command must be executed at the server machine that contains the single server or where the system manager is located.

(6) Notes

  1. The following shows the pdorcheck command's return codes:
    0: The application conditions are satisfied.
    4: Some of the resources do not satisfy the application conditions.
    8: The command terminated abnormally.
  2. Do not add to, delete, or change definition of a table or index of a specified RDAREA while the pdorcheck command is executing. If an addition, deletion, or definition change occurs, the result may be invalid or the command may terminate abnormally.