Don't know whether this can help or not... but you can keep this in
mind.

1) if you do "list tablespaces show detail", you should see a "status"
field. If the tablespace is in the "rebalancing" state, you need to
wait until the tablespace is in the "normal" state.

2) in UNIX, there is a 2gb file size limitation (I think this can be
controlled by ulimit command). to get around this limitation, I think
you can add container. This should not happen in windows.

3) if your index is created in a different DMS tablespace, you can
check whether the index tablespace is running out of space or not.

4) if your index is create in the same DMS tablespace, (caution) you
can consider dropping the index first, hopefully, to get around the
existing 289 problem. Then you can increase the size of the
tablespace. Then you can recreate the index.

5) all of the containers' size should be the same. If your containers
have different size, as soon as one container runs out of space, you
will see SQL0289.

6) if you can read db2 traces, you should be able to pinpoint the
origin of SQL0289.