Why is the copy table not created with the NOLOGGING attribute when the UNRECOVERABLE option for the table and the indexes has been selected in the "Choose Scripting Options" in Reorg Manager?
Product defect.
WORKAROUND
As a workaround, if you really need to use NOLOGGING during the reorganization, they can do one of two things:
1) Do a T-lock switch with Unrecoverable on the “Choose Scripting Options” screen
2) Create the table NOLOGGING on the “Customize Object Allocations” screen, and then manually change it back to logging with an alter table statement once the reorganization is complete.
STATUS
Waiting for a fix in a future release of Space Manager with LiveReorg.
