Causes and solutions for temporary suspension of DB2 tables (1)

When using the DB2 database, query the data of a table. The SQL statement is select * from db2admin. AlarmTarget. An error is reported. The error code is SQL0668N. SQL0668N. The table is not allowed" <Table Name> "Perform operations to restrict tables" <Table Name> . This article will analyze the causes for temporary suspension and solutions for you.

The reasons are as follows:

1. The table is in the "set integrity temporarily unavailable" status. The table integrity is not enforced and the table content may be invalid. This error may also be received if the operation is performed from the base table.

2. The table is in the "no data movement" status. In this status, data movement is prohibited. Data movement operations include REDISTRIBUTE, database partition Key Update, multi-dimensional cluster Key Update, range cluster Key Update, Data Partition Key Update, and reorg table.

3. The table is in the "load temporarily suspended" status. Previous LOAD attempts to this table failed. You are not allowed to access the table before restarting or terminating the LOAD operation.

4. The table is in the Read access status. This status can occur during online loading of LOAD) processing load insert with read access options, or after online loading of LOAD) operations, except when using SET INTEGRITY

5. The table is in the "loading" status. The LOAD utility is currently operating on this table and cannot be accessed until LOAD is complete.

6. You cannot refresh the specific query table that references the nickname in ESE.

7. The table is in the "REORG temporarily suspended" status. This situation may occur when you execute the alter table statement containing the REORG suggested operations.

8. The table is in the "change pending" status. This situation may occur when the alter table statement containing the REORG suggested operation is used in the work unit of the statement.