The pdorcheck command checks whether or not all base tables in specified RDAREAs satisfy the following application conditions:
- 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 with UNIQUE specified whose index component columns are all NOT NULL 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
- 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
- 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).
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.