Journal - Task History - Database backup success is expired

[cmitchell]

Hi,

I have daily backups set up for a database, however today i noticed in
the Journal under task history i see under the success column that the
status is expired. Normally the success column says successful or not
successful. Any ideas?

Cheryl

[Pierre Saint-Jacques]

I believe this refers to an association with an another parm. of your db
cfg:
Number of database backups to retain (NUM_DB_BACKUPS ) = 3
As you see mine is set to 3, yours by default would be set to 12 and your
expired indicator means that that backup is probably the 13th and therefore
DB2 considers it "expired".
You can check this by doing a get db cfg for the value of the parm. and a
list history backup all for <dbname> and count the number of backups your
history file has.

Now associate that parm. with this one:
Recovery history retention (days) (REC_HIS_RETENT N) = 90 That's mine.
Yours probably says 366.
If you were to issue:
PRUNE HISTORY timestamp
Then DB2 would delete all entries referring to backups, restores and
rollforward that are prior to the timestamp AND are not within the timestamp
of the 12th backup image.
If you add the options [WITH FORCE OPTION] [AND DELETE] then DB2 deletes
everything irregardless.

HTH, Pierre.
--
Pierre Saint-Jacques
SES Consultants Inc.
514-737-4515
"cmitchell" <ch************ *@eds.com> a écrit dans le message de news:
11************* ********@g43g20 00...legro ups.com...

Hi,

I have daily backups set up for a database, however today i noticed in
the Journal under task history i see under the success column that the
status is expired. Normally the success column says successful or not
successful. Any ideas?

Cheryl