Originally Posted by tataforums
Could you please advise why there is a need for load resume NO.
There are three possible LOAD scenarios for a tablespace:
(1) tablespace is empty and you have all new data in an external file
(2) tablespace is not empty; you want to empty it first, then do (1)
(3) tablespace is not empty; you have additional data to be added to it (like a set of INSERTs)
RESUME NO is the default; it makes sure that you're in situation (1) so that you won't accidentially do (2) or (3) which are either nonrecoverable (2) or difficult to recover (3) unless you fall back to an image copy.
Otherwise said: the default makes sure you don't do stupid things.
Combined with REPLACE, you explicitly tell DB2 you want scenario (2), which is of course also not a RESUME. So REPLACE goes together with RESUME NO.
RESUME YES tells DB2 you want to resume, i.e., continue with, the data already present in the table, i.e. you go for appending (scenario 3).
This is of course incompatible with RESUME YES.