Set the create limit for the specified area.

Syntax

proutil db-name -C setareacreatelimit area-name create-limit
        [ tenant tenant-name| group group-name| shared ]

Parameters

db-name
Specifies the database where you are setting the create limit.
area-number
Specifies the area where you are setting the create limit. You can specify an area by its name or its area number.
create-limit
Specifies the new create limit. The create limit is the amount of free space that must remain in a block when you are adding a record to the block.
tenant tenant-name
Specifies that the area create limit is to be set on tables and LOB objects in the area that are associated with tenant-name. If tenant-name is not valid, is part of a group, or is not associated with a partition in the area, SETAREACREATELIMIT exits with an error. Specifying tenant is only allowed on databases enabled for multi-tenancy and Type II areas.
group group-name
Specifies that the area create limit is to be set on tables and LOB objects in the area that are associated with group-name. If group-name is not valid or is not associated with partition in the area, SETAREACREATELIMIT exits with an error. Specifying group is only allowed on databases enabled for multi-tenancy and Type II areas.
shared
Specifies that the area create limit is to be set on shared tables and LOB objects in the area. Specifying shared is only allowed on databases enabled for multi-tenancy and Type II areas.

Notes

  • SETAREACREATELIMIT will set the limit for all tables and LOBs in the specified area.
  • The create limit value must be equal to or greater than 32, and less than the block size minus 128 bytes.
  • For databases with a 1K block size, the default create limit is 75. For all other database block sizes, the default create limit is 150.
  • For databases enabled for multi-tenancy, if tenant, group, or shared, is not specified, and the area has multi-tenant objects, the create limit is set for all objects in the area.
  • For more information on setting create limits, see Database fragmentation .