postconv fails on very large strings in 1.1.x conversion
The postconv step of conversion may fail for originating 1.1.x
repositories with extremely large strings, with an error "VM temp
obj memory is full". The large object coversion rebuilds objects in
memory, with the risk of running out of memory for sufficiently
The repository is safe to use even though the large object/s were
not converted; the old large object node layout will still work.
You can increase the amount of temporary object cache from the
default of 200000 by for the conversion process using the
postconv -t option. See the installation instructions for more information.
If this is not sufficient to allow postconv to complete, contact
GemStone Technical Support.