Set the toss limit for the specified area.

Syntax

proutil db-name -C setareatosslimit area-name toss-limit 
     [ tenant tenant-name| group group-name | shared ]

Parameters

db-name
Specifies the database where you are setting the toss limit.
area-name
Specifies the area where you are setting the toss limit. You can specify an area by its name or its area number.
toss-limit
Specifies the new toss limit. The toss limit is the minimum amount of free space that must exist in a block for the block to remain on the free chain as a candidate for holding additional records.
tenant tenant-name
Specifies that the area toss 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, SETAREATOSSLIMIT 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 toss 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, SETAREATOSSLIMIT exits with an error. Specifying group is only allowed on databases enabled for multi-tenancy and Type II areas.
shared
Specifies that the area toss 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

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