Changing Pooled Tables/Cluster Tables 

Procedure

To change a pooled or cluster table, proceed as described for transparent tables (see Changing Tables).

Effect of Changes

However, there are certain differences between pooled/cluster tables and transparent tables with regard to the effect of such changes.

If new fields are appended to a pooled or cluster table, it is not necessary to convert the table. The new fields are defined automatically as NOT NULL (see Initial Values). Therefore, when the modified table is activated, the complete table is scanned and the new field is filled with the initial value. This can take a considerable time in the case of pooled or cluster tables containing a large number of records.

Unlike for transparent tables, inserting new fields in a pooled or cluster table and making changes to the field sequence always causes the table to be converted.

If a pooled or cluster table is assigned to another physical table pool or table cluster, this results in the table being converted.

Pooled and cluster tables with more than 250 fields cannot be converted. You may not make changes to such tables that would require a table conversion (for example, inserting fields, changing the field sequence, deleting fields). New fields must always be appended at the end of the table.