The server ends a database update transaction for the specified
session because the size estimate provided by the client is too small.
The server has attempted to obtain additional space in the indicated
storage pool, but was unable to do so.
The specified session is ended and server operation continues.
If pool name is a random access storage pool with caching enabled,
it is also possible that additional space can be made available in this
storage pool by eliminating cached files. When the server allocates
space based on the size estimate provided by the client, it frees
space occupied by cached files if this space is needed to obtain the
estimated space. However, if the server later determines that the
file size estimate was too low, it attempts to obtain additional space
that is not utilized, but does not delete cached files to do so.
If the client sending the data has the option COMPRESSALWAYS YES set,
it is possible that a file grew during the compression operation and
when the client sent it to the server it exceeded the space available
in storage pool pool name.
This message may indicate that there is no additional space in pool
name. The following are possible circumventions:
An authorized administrator can issue the DEFINE VOLUME command
to add storage to this pool.
If the suspected cause of the failure is that pool name is
a DISK storage pool and that space in use by cached files was not
freed, turn off caching for the storage pool and issue the MOVE DATA
command for the volumes in pool pool name.
If the suspected cause of the failure is that a file grew in size
during compression on the client, another possible circumvention is
to set the COMPRESSALWAYS option in the client options file to NO
and retry the operation. This may allow the client to accurately
report the file size and possibly avoid the out of space condition
in the storage pool.