Software Knowledge

  1. Home
  2. Docs
  3. Software Knowledge
  4. Database
  5. DB2: “Backup Pending” appeared after issue “LOAD” command
Generic selectors
Exact matches only
Search in title
Search in content

DB2: “Backup Pending” appeared after issue “LOAD” command

Because Load inserts data by pages, the tablespace need to be recovered for data consistency.
if the load fails, you have to do load terminate.

Example of a table space state

If you load an input file (staffdata.del) into a table NEWSTAFF, as follows:
update db cfg for sample using logarchmeth1 logretain;
backup db sample;
connect to sample;
create table newstaff like staff;
load from staffdata.del of del insert into newstaff copy no;
connect reset;
and you open another session and issue the following commands,
connect to sample;
list tablespaces;
connect reset;
USERSPACE1 (the default table space for the sample database) is in the Load in Progress state and, after the first commit, the Backup Pending state as well. After the load operation finishes, the LIST TABLESPACES command reveals that USERSPACE1 is now in the Backup Pending state:
Tablespace ID = 2
Type = Database managed space
Contents = All permanent data. Large table space.
State = 0x0020
Detailed explanation:
Backup pending

Backup the database to clear “Backup pending” state
db2 “backup db nongdb tablespace (USERSPACE1) online to /dev/null without prompting”