When partitioning data, the server uses file systems that are specified in the DATAPATH=
option to distribute partitions in a cyclic, round-robin pattern. Instead of creating
partitions until the first file system is full, the server randomly chooses a file
system from the DATAPATH= list for the first
partition. Then, it sequentially assigns partitions to successive file systems in the DATAPATH=
list. The software continues to cycle through the file system set as many times as
needed until all data partitions for the table are stored.
If you set PARTSIZE=0, the server uses the DATAPATH= file systems strictly for overflow.
It creates partitions in the first file system, up to the file size limit of your
operating system. When the first file system is full, it proceeds to the second file
system, and so on. When the primary file system is full, specifying additional data
paths will enable users to append to an existing table. However, users will not be
able to create new tables in the
domain. In order for a new table to be created, the primary file system must be able to
store the first metadata file partition for the table. You will need to either free
space in the primary file system or create
a new server domain to enable new tables to be created.