Hi David,
An alter table statement which modifies the location of sblob columns (put in <sdbspace>)
affects only new records, not existing records.
If the goal from this operation is the full replacement of an sblob space instead of a new sblobspace
to be added in order to overcome a very full sdbspace and to spread the data over several sblob spaces
for any reason, the update operation using locopy needs to be done in order to really move
the sblob contents to the new sdbspace.
That kind of operation might be necessary if you want to replace a set of hard disks with a new one
without having to restore a full backup, but doing it in-place while keeping the database up.
This might take a while depending on the amount of data to be moved.
In case you are using replication of any kind, make sure the target sblob dbspace
is logged. (onspaces -S ... -Df LOGGING=ON, or for an pre-existing sblob space onspaces -ch -Df)
So this article is still valid (also with newer releases 14.x).
The original sblob should have no references at the end, resulting in an empty sblob space,
which can be dropped after this operation (unless there are other tables with referencing content).
There is an additional operation which might be necessary to mark the sblob objects as freed,
when there is no reference any more (onspaces -cl).
Best, Marcus