12.15.2 Restrictions
(1) Definition SQL
Some definition SQL statements cannot be executed on falsification prevented tables. The following table lists restricted definition SQL statements and the restrictions that apply to them.
Table 12-6 Restricted definition SQL statements and the restrictions that apply to them
SQL statement | Restrictions |
---|
CREATE TABLE | If all columns have the updatable column attribute, the falsification prevention option cannot be specified. |
ALTER TABLE | - Table names and column names cannot be changed.
- The falsification prevention facility cannot be applied to a table containing data. For details about how to apply the falsification prevention facility to an existing table, see 12.15.3 Changing a falsification-unprevented table to a falsification prevented table.
- The falsification prevention facility cannot be released.
- No existing column can be changed to an updatable column, or no updatable column can be changed to a normal column.
- Updatable columns must be defined before the falsification prevention facility is applied.#
- Setting, releasing, and duration of deletion prevented duration cannot be changed.
- If a deletion prevented duration is specified for a falsification prevented table, the insert history maintenance column that specifies the deletion prevented duration cannot be deleted.
- Partition storage conditions cannot be changed.
|
DROP TABLE | Cannot be executed if there is data in a falsification prevented table. |
- #: To specify an updatable column for an existing table and apply the falsification prevention facility, you must execute ALTER TABLE on the column and the table. To apply the falsification prevention facility:
- Use ALTER TABLE to change the attribute of a desired column to updatable.
- Use ALTER TABLE (CHANGE INSERT ONLY) to apply the falsification prevention facility to the table.
(2) Utilities
The operation of utilities is restricted on falsification prevented tables and the RDAREAs that store them. The following table lists restricted utilities and the restrictions that apply to them. There are no restrictions on utilities not listed in the table.
Table 12-7 Restricted utilities and the restrictions that apply to them
Utility | Restrictions |
---|
Database creation utility (pdload) | - Cannot be used in the creation mode (-d option specified).
- Cannot be executed if the table is in reload-not-completed data status.#
|
Database structure modification utility (pdmod) | - Cannot re-initialize a falsification prevented table's storage RDAREA (initialize rdarea).
|
Database reorganization utility (pdrorg) | Table reorganization (-k rorg)
- Cannot execute if the related table storage RDAREA is not in command shutdown status.
- Cannot perform reorganization using a UOC (unlduoc statement).
- Cannot reorganize the synchronization point specification (option job statement).
- Cannot execute if related tables are in reload-not-completed data status.#
Table unload (-k unld)
- Cannot be executed unless the -W option is specified.
Table reload (-k reld)
- Cannot execute if the related table storage RDAREA is not in command shutdown status.
- Can execute if the related table is in reload-not-completed data status# (can only re-execute if table reloading terminates abnormally during table reorganization)
- Cannot reorganize the synchronization point specification (option job statement).
- Cannot reload to another table (for details, see Figure 12-24).
Batch index creation (-k ixmk), re-creation (-k ixrc), reorganization (-k ixor)
- Cannot execute if related tables are in reload-not-completed data status.#
|
Rebalance utility (pdrbal) | Cannot execute if related tables are in reload-not-completed data status.# |
- #: If reorganization is executed for a falsification prevented table, but because of an error or some other reason the reload is not completed, the table is placed in a status called reload-not-completed data status, which status is also applied to the storage RDAREAs of the falsification prevented table. You can check whether an RDAREA is in reload-not-completed data status with the database condition analysis utility, the RDAREA unit analysis utility (logical analysis), or by means of a table unit status analysis. Reload-not-completed data status can be released when table reorganization (table reloading) completes normally. For details about the reload-not-completed data status, see the manual HiRDB Version 9 Command Reference.
Figure 12-24 Reloading to another table
![[Figure]](figure/zu120200.gif)
- Explanation:
- Falsification prevented table T1 can be reloaded to non-falsification prevented table T3, because falsification prevented table T1 loses its restrictions.
- Non-falsification prevented table T3 cannot be reloaded to falsification prevented table T1, because the data in falsification prevented table T1 is protected.
- Falsification prevented table T1 cannot be reloaded to falsification prevented table T2, because the data in falsification prevented table T2 is protected.
- Falsification prevented table T1 can be reloaded back into itself, because falsification prevented table T1 loses its protection.
- Falsification prevented table T1 on HiRDB system 1 cannot be reloaded into falsification prevented table T1 on HiRDB system 2, because the data in falsification prevented table T1 on HiRDB system 1 loses its protection when it is in falsification prevented table T1 on HiRDB system 2.
(3) Operation commands
There are restrictions on the commands that can be used on falsification prevented tables and the RDAREAs in which falsification prevented tables are stored. The following table lists the restricted operating commands.
Table 12-8 Restricted commands and their restrictions
Operation command | Restrictions |
---|
RDAREA shutdown (pdhold) | If you cannot execute a reload in order to complete the reorganization of a falsification prevented table so that the status of the RDAREA that stores the table can be changed from reload-not-completed data status, the following options cannot be executed:
- Reference-possible shutdown: -i
- Backup shutdown: -b
|
RDAREA shutdown release (pdrels) | If you do not reload an RDAREA that stores a falsification prevented table that is in reload-not-completed data status, you cannot release the shutdown before the table reorganization is completed, because that would leave 0 records of data. |
(4) Restrictions on related products
Restrictions on related products include the following:
- Replication facility
For falsification prevented tables, do not use the replication facilities (HiRDB Dataextractor and HiRDB Datareplicator) to copy data and reflect the result. An attempt to do so could result in a mismatch in the data in the reflection source and the reflection result, causing an error.