Tablespaces are put into backup pending after a load

DB2 sets tablespace as Backup Pending state after loading data into a table in linear logging database(that is, logretain or userexit is on), whatever the load is successful or failed. the reason is that the load process will not write log file. from the begin time of loading to the end time of loading, there will be a blank segment in log file, and the rollforward recovery can Not jump over the blank segment to apply the later log file.

so database needs a backup after loading to make sure db2 have recovery capicibility.

it's able to use ~~[COPY YES|NO] or~~ [NONRECOVERABLE] to prevent tablespace go into Backup Pending state. ~~COPY YES will do the backup automatically after loading, and COPY NO and~~ NONRECOVERABLE will give up this backup that means db2 will be not able to recover the database once an serious error occured.

Thinking more

how if specified NONRECOVERABLE at load insert but not specified it at load terminate or load restart?

how if give an increamental backup instead of a full backup after tablespace goes into Backup Pending state by a loading?

it is not allowed, you must give a full backup after going into Backup Pending state by a loading. but a full online backup works as well as a full offline backup.

a full tablespace backup doesn't works for above.

Commands reference

$ db2 load client from "loadfile.del" of del insert into table_name [nonrecoverable | copy yes]

$ db2 load query table table_name to msgfile.txt

$ db2 load client from "loadfile.del" of del terminate into table_name [nonrecoverable | copy yes]

$ db2 load client from "loadfile.del" of del restart into table_name [nonrecoverable | copy yes]

[nonrecoverable ~~| copy yes~~] to prevent the tablespace go into backup pending status after successful of failed load.