How to remove backup pending state of a tablespace/database without actually taking a backup?
A LOAD operation without the nonrecoverable or copy yes option puts the tablespace in backup pending state. If you change your database logging from circular to archive, the database state will change to backup pending state.
While it is strongly recommended to take an actual backup in such cases any stay out of any possible trouble, there is a workaround to bring your database out of backup pending state using DB2DART utility. This would save a lot of time (if you database is huge) but in the case of a corruption your database may become unrecoverable. You must backup your database/tablespace on the first available opportunity if you use DB2DART to change database/tablespace state.
To change the state of the database using DB2DART your database must be offline.
The DB2DART command is:
db2dart <DB NAME> /CHST /WHAT DBBP OFF
If you have time to take the backup but don't have enough space to store it, you can consider running a normal backup and redirecting it to a null device (on UNIX and Linux only)
db2 backup db <db name> to /dev/null
This will take approximately the normal time it takes to backup your db but will not store it anywhere.
