WOS Overload

Explanation and Workaround

The WOS can expand to hold up to 1GB of data at any time. If you try to load more data than the WOS can hold before the automatic tuple mover can advance the epoch and perform a moveout, the COPY statement fails and the current transaction rolls back. WOS overload is most likely to occur when loading a very large fact table. If you encounter this problem, consider one or more of the following:

• Load the data to disk (ROS) instead of memory (WOS).
• Split the fact table load file into multiple pieces and do multiple loads in sequence.

Refer to Advanced Storage Control in the Database Administrator's Guide (Advanced).