When reorganizing with CREATE TABLE AS SELECT or in Deferred mode the objects are reorganized one after the other. During reorganization sufficient memory space must be available both for the old and the new object. Each time SAPBDA checks whether there is enough space in the relevant tablespace in order to regenerate the largest object to be reorganized. The largest object is always reorganized first.
In exceptional cases, for example when the objects to be reorganized are very fragmented or free space is relatively short, errors can arise during the reorganization of a list of objects or a whole tablespace when generating the new objects. Such ORACLE errors, which SAPDBA registers as a warning, tell you that the object that caused the termination will be left out. The object is unchanged, however. You can reorganize it later as a single object or carry out a restart (if necessary after a tablespace enhancement).