KFAA31727-E

No new table or index can be defined in the data DB area because the maximum number of chunks that can be managed in one data DB area has been exceeded. Another possibility is that the value set for the maximum number of chunks in a table defined in the data DB area cannot be increased. <SQLSTATE: 40801>

aa....aa: Operation attempted

• defined: Defining tables or indexes

• changed: Changing table definitions

bb....bb:

DB area name

cc....cc:

Number of chunks that exceeded the maximum

S:

Invalidates this transaction.

Action:

Reduce the value set for the maximum number of chunks based on the number of chunks that exceeded this maximum (value of cc....cc), and then re-execute the SQL statement.

However, if all the following conditions are satisfied, this message might be output again after the maximum number of chunks is reduced. In such a case, further reduce the maximum number of chunks.

• changed is displayed for aa....aa.

• The table to be changed and the index defined for that table are stored in the same DB area.

If the value set for the maximum number of chunks cannot be reduced, take the action that is appropriate to the operation to be performed, as described below.

Operation attempted (information displayed as aa....aa)	Corrective action
defined	Define the table or index in another DB area. Delete any unneeded tables and indexes from this DB area. Reduce the value set for the maximum number of chunks in another table in the same DB area.#
changed	Delete any unneeded tables and indexes from this DB area. Reduce the value set for the maximum number of chunks in another table in the same DB area.#

#

For details about how to change the maximum number of chunks, see Changing the maximum number of chunks in Performing operations on multi-chunk tables in Unscheduled Operations in the HADB Setup and Operation Guide.